Bug 1582516

Summary:	libgfapi: glfs init fails on afr volume with ctime feature enabled
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	libgfapi	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, nchilaka
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1583016 (view as bug list)		Environment:
Last Closed:	2018-10-23 15:10:12 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:	1583016

Description Kotresh HR 2018-05-25 13:08:45 UTC

Description of problem:
With ctime feature enabled on afr volume libgfapi programs fail.
Basically glfs_init fails.

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

How reproducible:
Always

Steps to Reproduce:
1.  Create replicated gluster volume
2.  Write and run a libgfapi program to use the volume


Actual results:
libgfapi program fails on afr volume.

Expected results:
libgfapi program should not fail on afr volume.


Additional info:

Comment 1 Worker Ant 2018-05-25 13:13:22 UTC

REVIEW: https://review.gluster.org/20086 (libgfapi: Fix lookup on root) posted (#1) for review on master by Kotresh HR

Comment 2 Worker Ant 2018-05-28 04:57:49 UTC

COMMIT: https://review.gluster.org/20086 committed in master by "Amar Tumballi" <amarts> with a commit message- libgfapi: Fix lookup on root

Lookup on root was sending "/" as the path.
This will break the basename calculation in
loc_copy and hence lookup on root was failing
if the loc_copy was involved in the stack.

With ctime, a first lookup on root initiates
a metadata self heal because of ctime xattr
not being same on all afr subvolumes. This
results in loc_copy and hence the failure
of lookup.

Fix would be to send path with "." for the root.

fixes: bz#1582516
Change-Id: Iafe4b99f249a4f5034ad34c1d30590de0e35aa0d
Signed-off-by: Kotresh HR <khiremat>

Comment 3 Worker Ant 2018-10-09 08:00:11 UTC

REVIEW: https://review.gluster.org/21371 (libgfapi: Send path with \".\" for the root) posted (#1) for review on master by Kinglong Mee

Comment 4 Worker Ant 2018-10-16 06:43:20 UTC

COMMIT: https://review.gluster.org/21371 committed in master by "Amar Tumballi" <amarts> with a commit message- libgfapi: Send path with "." for the root when loc.parent is set

fixes: bz#1582516
Change-Id: Ia9649d7c3c0930dfec656d364cf6e9a98c774dd2
Signed-off-by: Kinglong Mee <mijinlong>

Comment 5 Shyamsundar 2018-10-23 15:10:12 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/

Comment 6 Shyamsundar 2019-03-25 16:30:27 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-6.0, please open a new bug report.

glusterfs-6.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/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/