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): mainline How reproducible: always
REVIEW: http://review.gluster.org/6214 (cluster/dht: fix 'stime' getxattr getting overwritten) posted (#1) for review on master by Venky Shankar (vshankar)
This looks like it might have been fixed by http://review.gluster.org/#/c/6405. Can you please check and update the BZ?
The intended patch in comment 1 is fixed as part of https://review.gluster.org/#/c/6405. From the commit messag: glusterd/geo-rep: more glusterd and cli fixes for geo-rep. -> handle option validation cases in reset case. -> Creating valid conf path when glusterd restarts. -> Reading the gsyncd worker thread status and displaying it. -> Displaying status-detail per worker. -> Fetch checkpoint info in geo-rep status. -> use-tarssh value validation added. misc: misc geo-rep fixes based on cluster, logrotate etc.. -> cluster/dht: fix 'stime' getxattr getting overwritten. -> cluster/afr: return max of 'stime' values in subvol. -> geo-rep-logrotate: Sending SIGHUP to geo-rep auxiliary. -> cluster/dht: fix convoluted logic while aggregating. -> cluster/*: fix 'stime' min/max fetch logic. <--- fix for stime logic Marking this as closed since the patch is already merged.