[Gluster-users] Inconsistent md5sum of replicated file
Pranith Kumar K
pranithk at gluster.com
Wed Sep 7 08:43:56 UTC 2011
Could you send the output of the getfattr -d -m . -e hex
<filepath> on both the bricks and also the stat output on the both the
backends. Give the outputs for its parent directory also.
On 09/07/2011 04:22 AM, Anthony Delviscio wrote:
> I was wondering if anyone would be able to shed some light on how a
> file could end up with inconsistent md5sums on Gluster backend storage.
> Our configuration is running on Gluster v3.1.5 in a
> distribute-replicate setup consisting of 8 bricks.
> Our OS is Red Hat 5.6 x86_64.Backend storage is an ext3 RAID 5.
> The 8 bricks are in RR DNS and are mounted for reading/writing via NFS
> When comparing md5sums of the file from two different NFS clients,
> they were different.
> The extended attributes of the files on backend storage are
> identical.The file size and permissions are identical.The stat data
> (excluding inode on backend storage file system) is identical.
> However, running md5sum on the two files, results in two different
> Copying both files to another location/server and running the md5sum
> also results in no change – they’re still different.
> Gluster logs do not show anything related to the filename in
> question.Triggering a self-healing operation didn’t seem to do
> anything and it may have to do with the fact that the extended
> attributes are identical.
> If more information is required, let me know and I will try to
> Thank you
> Gluster-users mailing list
> Gluster-users at gluster.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-users