hi Anthony,
Parent directory is directory that contains the file.
Pranith
On 09/07/2011 08:18 PM, Anthony Delviscio wrote:
Pranith, by parent directory, do you mean the directory that contains
the file or the top level directory of the brick?
My gluster volume info:
http://pastie.org/2493045
The hostnames used in the gluster volume info are DNS hostnames that
resolve to 10GB interfaces on the Gluster nodes.
The hostname used in the mount options is a RR DNS hostname that
resolves to all eight Gluster nodes.
Stat/md5sum/getfattr data of the identical files with different md5sums.
http://pastie.org/2497461
Thank you
On Wed, Sep 7, 2011 at 4:43 AM, Pranith Kumar K <[email protected]
<mailto:[email protected]>> wrote:
hi Anthony,
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.
Pranith.
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 automounts.
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 md5sums.
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
accommodate.
Thank you
_______________________________________________
Gluster-users mailing list
[email protected] <mailto:[email protected]>
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
[email protected]
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
