Bug 1592275

Summary:	posix/ctime: Mdata value of a directory is different across replica/EC subvolume
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	posix	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1593537 (view as bug list)		Environment:
Last Closed:	2018-10-23 15:11:37 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:
Bug Blocks:	1593537

Description Kotresh HR 2018-06-18 10:03:42 UTC

Description of problem:
On a EC/replica volume, the mdata xattr is expected to be same. But it's different.

Version-Release number of selected component (if applicable):
mainline

How reproducible:
Mostly

Steps to Reproduce:
1. Create 2*(4+2) gluster disperse volume
2. Mount the volume
3. Create 1000 directories

Actual results:
The value of trusted.glusterfs.mdata is different on different subvolume of replica/EC set.

Expected results:
The value of trusted.glusterfs.mdata should be same on different subvolume of replica/EC set.

Additional info:

Comment 1 Worker Ant 2018-06-18 10:12:06 UTC

REVIEW: https://review.gluster.org/20281 (posix/ctime: Fix differential ctime duing entry operations) posted (#3) for review on master by Kotresh HR

Comment 2 Worker Ant 2018-06-20 06:51:50 UTC

COMMIT: https://review.gluster.org/20281 committed in master by "Amar Tumballi" <amarts> with a commit message- posix/ctime: Fix differential ctime duing entry operations

We should not be relying on backend file's time attributes
to load the initial ctime time attribute structure. This
is incorrect as each replica set would have witnessed the
file creation at different times.

For new file creation, ctime, atime and mtime should be
same, hence initiate the ctime structure with the time
from the frame. But for the files which were created
before ctime feature is enabled, this is not accurate
but still fine as the times would get eventually accurate.

fixes: bz#1592275
Change-Id: I206a469c83ee7b26da2fe096ae7bf8ff5986ad67
Signed-off-by: Kotresh HR <khiremat>

Comment 3 Shyamsundar 2018-10-23 15:11:37 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.

glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/