The file in question is a linux ISO. On Server01 I've copied it over to my gluster mount and waited for it to be fully copied. Then on server02 I've waited until about half of the file is replicated over and pulled the network cable. Once the network cable is back in again no matter what I do I cannot get it to sync the file back up. I did notice however that if I reboot both of the servers then the corrupt image on Server02 is then replicated over to Server01. Should Gluster 2.0.6 be able to cope with something like this or is this a 2.1 feature? On Sun, Sep 20, 2009 at 6:26 PM, Anand Avati <avati at gluster.com> wrote: > > I'm starting gluster like this: > > sudo glusterfs -f /etc/glusterfs/glusterfs-client.vol /mnt/glusterfs > > sudo glusterfsd -f /etc/glusterfs/glusterfs-server.vol > > > > And do the following to try and trigger it to replicate > > sudo ls -alRh /mnt/glusterfs/ > > sudo ls -alRh /data/export > > sudo ls -alRh /data/export-ns > > > > Am I missing something? > > You need to access the file in question from the mountpoint (ls -lR > just ends up accessing all the files). Are you accessing it while the > file is still open and being written to? self heal of open files will > be supported only in 2.1 release. > > Avati >
