Martin Schenker
2011-May-15 18:20 UTC
[Gluster-users] Brick pair file mismatch, self-heal problems?
Can someone enlighten me what's going on here? We have a two peers, the file 21313 is shown through the client mountpoint as "1Jan1970", attribs on server pserver3 don't match but NO self-heal or repair can be triggered through "ls -alR"?!? Checking the files through the server mounts show that two versions are on the system. But the wrong one (as with the "1Jan1970") seems to be the preferred one by the client?!? Do I need to use setattr or what in order to get the client to see the RIGHT version?!? This is not the ONLY file displaying this problematic behaviour! Thanks for any feedback. Martin pserver5: 0 root at pserver5:~ # ls -al /mnt/gluster/brick1/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef /hdd-images -rwxrwx--- 1 libvirt-qemu vcb 483183820800 May 13 13:41 21313 0 root at pserver5:~ # getfattr -R -d -e hex -m "trusted.afr." /mnt/gluster/brick1/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef /hdd-images/21313 getfattr: Removing leading '/' from absolute path names # file: mnt/gluster/brick1/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef/ hdd-images/21313 trusted.afr.storage0-client-2=0x000000000000000000000000 trusted.afr.storage0-client-3=0x000000000000000000000000 0 root at pserver5:~ # ls -alR /opt/profitbricks/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef/h dd-images/21313 -rwxrwx--- 1 libvirt-qemu kvm 483183820800 Jan 1 1970 /opt/profitbricks/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef/h dd-images/21313 pserver3: 0 root at pserver3:~ # ls -al /mnt/gluster/brick1/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef /hdd-images -rwxrwx--- 1 libvirt-qemu kvm 483183820800 Jan 1 1970 21313 0 root at pserver3:~ # ls -alR /opt/profitbricks/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef/h dd-images/21313 -rwxrwx--- 1 libvirt-qemu kvm 483183820800 Jan 1 1970 /opt/profitbricks/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef/h dd-images/21313 0 root at pserver3:~ # getfattr -R -d -e hex -m "trusted.afr." /mnt/gluster/brick1/storage/images/2078/ebb83b05-3a83-9d18- ad8f-8542864da6ef/hdd-images/21313 getfattr: Removing leading '/' from absolute path names # file: mnt/gluster/brick1/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef/ hdd-images/21313 trusted.afr.storage0-client-2=0x000000000000000000000000 trusted.afr.storage0-client-3=0x0b0000090900000000000000 <- mismatch, should be targeted for self-heal/repair? Why is there a difference in the views?>From the volfile:volume storage0-client-2 type protocol/client option remote-host de-dc1-c1-pserver3 option remote-subvolume /mnt/gluster/brick1/storage option transport-type rdma option ping-timeout 5 end-volume volume storage0-client-3 type protocol/client option remote-host de-dc1-c1-pserver5 option remote-subvolume /mnt/gluster/brick1/storage option transport-type rdma option ping-timeout 5 end-volume
Mohit Anchlia
2011-May-16 00:23 UTC
[Gluster-users] Brick pair file mismatch, self-heal problems?
Try this to trigger self heal: find <gluster-mount> -noleaf -print0 -name <file name>| xargs --null stat >/dev/null On Sun, May 15, 2011 at 11:20 AM, Martin Schenker <martin.schenker at profitbricks.com> wrote:> Can someone enlighten me what's going on here? We have a two peers, the file > 21313 is shown through the client mountpoint as "1Jan1970", attribs on > server pserver3 don't match but NO self-heal or repair can be triggered > through "ls -alR"?!? > > Checking the files through the server mounts show that two versions are on > the system. But the wrong one (as with the "1Jan1970") seems to be the > preferred one by the client?!? > > Do I need to use setattr or what in order to get the client to see the RIGHT > version?!? This is not the ONLY file displaying this problematic behaviour! > > Thanks for any feedback. > > Martin > > pserver5: > > 0 root at pserver5:~ # ls -al > /mnt/gluster/brick1/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef > /hdd-images > > -rwxrwx--- 1 libvirt-qemu vcb ?483183820800 May 13 13:41 21313 > > 0 root at pserver5:~ # getfattr -R -d -e hex -m "trusted.afr." > /mnt/gluster/brick1/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef > /hdd-images/21313 > getfattr: Removing leading '/' from absolute path names > # file: > mnt/gluster/brick1/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef/ > hdd-images/21313 > trusted.afr.storage0-client-2=0x000000000000000000000000 > trusted.afr.storage0-client-3=0x000000000000000000000000 > > 0 root at pserver5:~ # ls -alR > /opt/profitbricks/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef/h > dd-images/21313 > -rwxrwx--- 1 libvirt-qemu kvm 483183820800 Jan ?1 ?1970 > /opt/profitbricks/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef/h > dd-images/21313 > > pserver3: > > 0 root at pserver3:~ # ls -al > /mnt/gluster/brick1/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef > /hdd-images > > -rwxrwx--- 1 libvirt-qemu kvm ?483183820800 Jan ?1 ?1970 21313 > > 0 root at pserver3:~ # ls -alR > /opt/profitbricks/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef/h > dd-images/21313 > -rwxrwx--- 1 libvirt-qemu kvm 483183820800 Jan ?1 ?1970 > /opt/profitbricks/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef/h > dd-images/21313 > > 0 root at pserver3:~ # getfattr -R -d -e hex -m "trusted.afr." > /mnt/gluster/brick1/storage/images/2078/ebb83b05-3a83-9d18- > ad8f-8542864da6ef/hdd-images/21313 > getfattr: Removing leading '/' from absolute path names > # file: > mnt/gluster/brick1/storage/images/2078/ebb83b05-3a83-9d18-ad8f-8542864da6ef/ > hdd-images/21313 > trusted.afr.storage0-client-2=0x000000000000000000000000 > trusted.afr.storage0-client-3=0x0b0000090900000000000000 ?<- mismatch, > should be targeted for self-heal/repair? Why is there a difference in the > views? > > > From the volfile: > > volume storage0-client-2 > ? ?type protocol/client > ? ?option remote-host de-dc1-c1-pserver3 > ? ?option remote-subvolume /mnt/gluster/brick1/storage > ? ?option transport-type rdma > ? ?option ping-timeout 5 > end-volume > > volume storage0-client-3 > ? ?type protocol/client > ? ?option remote-host de-dc1-c1-pserver5 > ? ?option remote-subvolume /mnt/gluster/brick1/storage > ? ?option transport-type rdma > ? ?option ping-timeout 5 > end-volume > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users >