Bug 1582080

Summary:	posix/ctime: The first lookup on file is not healing the gfid
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:	4.1	CC:	bugs, nchilaka
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-v4.1.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1580532	Environment:
Last Closed:	2018-06-20 18:07:14 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:	1580532
Bug Blocks:

Description Kotresh HR 2018-05-24 07:16:26 UTC

+++ This bug was initially created as a clone of Bug #1580532 +++

Description of problem:
With ctime feature enabled, the first lookup on the file is not healing the gfid if it's not present.

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

How reproducible:
Always

Steps to Reproduce:
1. Create dist-rep gluster volume (1*2) and mount at /mnt
2. Enable ctime feature
             gluster vol set <vol> utime on
             gluster vol set <vol> ctime on
3. Create a file on both replica brick in the backend (say file)
4. stat /mnt/file

Actual results:
The first stat is giving ENOENT and is not healing gfid

Expected results:
The first stat should heal the gfid

Additional info:

--- Additional comment from Worker Ant on 2018-05-21 13:35:56 EDT ---

REVIEW: https://review.gluster.org/20052 (posix/ctime: Fix gfid heal on first lookup) posted (#1) for review on master by Kotresh HR

--- Additional comment from Worker Ant on 2018-05-24 02:25:16 EDT ---

COMMIT: https://review.gluster.org/20052 committed in master by "Amar Tumballi" <amarts> with a commit message- posix/ctime: Fix gfid heal on first lookup

With ctime feature enabled, the gfid is
not healing on first lookup. The fresh
file logic depends on ctime and it was
fetching from backend instead of xattr
with ctime feature enabled. Fixed the
same.

Also fixed a possible hang with inode lock

Change-Id: I020875c0462b284d6fa0e68304a422fa3d6a3e73
fixes: bz#1580532
Signed-off-by: Kotresh HR <khiremat>

Comment 1 Worker Ant 2018-05-24 07:45:52 UTC

REVIEW: https://review.gluster.org/20079 (posix/ctime: Fix gfid heal on first lookup) posted (#1) for review on release-4.1 by Kotresh HR

Comment 2 Worker Ant 2018-05-24 19:13:53 UTC

COMMIT: https://review.gluster.org/20079 committed in release-4.1 by "Kotresh HR" <khiremat> with a commit message- posix/ctime: Fix gfid heal on first lookup

With ctime feature enabled, the gfid is
not healing on first lookup. The fresh
file logic depends on ctime and it was
fetching from backend instead of xattr
with ctime feature enabled. Fixed the
same.

Also fixed a possible hang with inode lock

Backport of:
 > Patch: https://review.gluster.org/20052
 > BUG: 1580532
 > Change-Id: I020875c0462b284d6fa0e68304a422fa3d6a3e73
 > Signed-off-by: Kotresh HR <khiremat>

fixes: bz#1582080
Change-Id: I020875c0462b284d6fa0e68304a422fa3d6a3e73
Signed-off-by: Kotresh HR <khiremat>

Comment 3 Shyamsundar 2018-06-20 18:07:14 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-v4.1.0, please open a new bug report.

glusterfs-v4.1.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] http://lists.gluster.org/pipermail/announce/2018-June/000102.html
[2] https://www.gluster.org/pipermail/gluster-users/