Bug 1025956

Summary:	Dist-geo-rep : 'stime' xattr is not the minimum of all distribute subvolumes
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Venky Shankar <vshankar>
Component:	geo-replication	Assignee:	Bug Updates Notification Mailing List <rhs-bugs>
Status:	CLOSED ERRATA	QA Contact:	Vijaykumar Koppad <vkoppad>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.1	CC:	aavati, amarts, bbandari, csaba, gluster-bugs, grajaiya, vagarwal, vkoppad, vshankar
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.4.0.39rhs	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1025955	Environment:
Last Closed:	2013-11-27 15:45:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1025955
Bug Blocks:

Description Venky Shankar 2013-11-02 13:20:18 UTC

+++ 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):
mainline

How reproducible:
always

Comment 2 Amar Tumballi 2013-11-02 16:27:42 UTC

https://code.engineering.redhat.com/gerrit/#/c/15077/

Comment 3 Gowrishankar Rajaiyan 2013-11-11 10:31:02 UTC

Please provide steps to verify.

Comment 4 Venky Shankar 2013-11-11 11:03:17 UTC

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.

Comment 5 Vijaykumar Koppad 2013-11-15 10:30:19 UTC

Verified on the build glusterfs-3.4.0.44rhs

on the mount point 

[root@shaktiman ~]# getfattr -d -m . -e hex /mnt/master/
getfattr: Removing leading '/' from absolute path names
# file: mnt/master/
trusted.glusterfs.b2a5d205-79ec-471e-a72f-782a2063c683.c261bc11-9898-4e49-83e8-758c494a82e9.stime=0x5285f40b00065b94
trusted.glusterfs.b2a5d205-79ec-471e-a72f-782a2063c683.xtime=0x5285f40b000c343f
trusted.glusterfs.volume-id=0xb2a5d20579ec471ea72f782a2063c683

and the value of stime from the backends, 

>>> int("5285f40b00065b94",16)
5946427211094842260
>>> int("5285f40c0003a98a",16)
5946427215389632906
>>> int("5285f40b00065b94",16)
5946427211094842260
>>> int("5285f40b00065b94",16)
5946427211094842260
>>> min(5946427211094842260,5946427215389632906,5946427211094842260,5946427211094842260)
5946427211094842260

and 5285f40b00065b94 is the minimum stime, which got on mount point.

Comment 6 errata-xmlrpc 2013-11-27 15:45:55 UTC

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.

http://rhn.redhat.com/errata/RHBA-2013-1769.html