Red Hat Bugzilla – Bug 1025956
Dist-geo-rep : 'stime' xattr is not the minimum of all distribute subvolumes
Last modified: 2014-08-24 20:50:31 EDT
+++ This bug was initially created as a clone of Bug #1025955 +++
Description of problem:
'stime' xattr is not fetched as the minimum of all distribute subvolumes. This is required by geo-replication for correctly identify the slave lag.
Version-Release number of selected component (if applicable):
Please provide steps to verify.
Steps to verify:
1. Create and start a distributed volume and mount the volume
2. Perform some I/O on the mount
3. Check the 'stime' extended-attribute for the brick (on the backend)
4. From the mount fetch the extended attribute (name to be taken from step 3)
5. The value of the xattr should be the minimum value on the bricks.
Verified on the build glusterfs-18.104.22.168rhs
on the mount point
[root@shaktiman ~]# getfattr -d -m . -e hex /mnt/master/
getfattr: Removing leading '/' from absolute path names
# file: mnt/master/
and the value of stime from the backends,
and 5285f40b00065b94 is the minimum stime, which got on mount point.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.