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:
REVIEW: https://review.gluster.org/20086 (libgfapi: Fix lookup on root) posted (#1) for review on master by Kotresh HR
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>
REVIEW: https://review.gluster.org/21371 (libgfapi: Send path with \".\" for the root) posted (#1) for review on master by Kinglong Mee
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>
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/
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/