On 29.10.2012 02:47, Pranith Kumar Karampuri wrote: > hi, > Could you post output of 'getfattr -d -m . -e hex <fpath>' on both > the bricks. Sure, [root at 2216 ~]# getfattr -d -m . -e hex /brick1/rawfile.img getfattr: Removing leading '/' from absolute path names # file: brick1/rawfile.img security.selinux=0x73797374656d5f753a6f626a6563745f723a66696c655f743a733000 trusted.afr.glusterfs1-client-0=0x000000000000000000000000 trusted.afr.glusterfs1-client-1=0x000000000000000000000000 trusted.gfid=0x0881c9c6837642c0a616d03c2f034138 [root at 1631 ~]# getfattr -d -m . -e hex /brick1/rawfile.img getfattr: Removing leading '/' from absolute path names # file: brick1/rawfile.img security.selinux=0x73797374656d5f753a6f626a6563745f723a66696c655f743a733000 trusted.afr.glusterfs1-client-0=0x000000000000000000000000 trusted.afr.glusterfs1-client-1=0x000000000000000000000000 trusted.gfid=0x0881c9c6837642c0a616d03c2f034138 To answer another question that came off-list: server A /brick1/rawfile.img and server B /brick1/rawfile.img have different md5 sums, however on the mounted glusterfs volume I get the md5sum from server A (which is also the largest file and probably the "correct" file, whatever that means). -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
