Description of problem: Unable to self-heal symbolic links Version-Release number of selected component (if applicable): glusterfs 3git built on Dec 26 2013 How reproducible: always Steps to Reproduce: 1. Create replicate volume 2. create a file and directory from mount point 3. Kill one brick 4. Create symbolic link to file and directory 5. Bring back the killed brick up. 6. At mount point execute ls Actual results: Symbolic links are not getting healed Expected results: Symbolic link should get healed. Additional info:
REVIEW: http://review.gluster.org/6599 (cluster/afr: Unable to self heal symbolic links) posted (#1) for review on master by venkatesh somyajulu (vsomyaju)
REVIEW: http://review.gluster.org/6600 (cluster/afr: Unable to self heal symbolic links) posted (#1) for review on release-3.5 by venkatesh somyajulu (vsomyaju)
Are you sure?In glusterfs-3.4.1, I do this case, kill one brick,then link -s dir, restart the brick, heal the symlink by glusterfsd.
REVIEW: http://review.gluster.org/6599 (cluster/afr: Unable to self heal symbolic links) posted (#2) for review on master by venkatesh somyajulu (vsomyaju)
REVIEW: http://review.gluster.org/6600 (cluster/afr: Unable to self heal symbolic links) posted (#2) for review on release-3.5 by venkatesh somyajulu (vsomyaju)
REVIEW: http://review.gluster.org/6599 (cluster/afr: Unable to self heal symbolic links) posted (#5) for review on master by venkatesh somyajulu (vsomyaju)
REVIEW: http://review.gluster.org/6600 (cluster/afr: Unable to self heal symbolic links) posted (#4) for review on release-3.5 by venkatesh somyajulu (vsomyaju)
REVIEW: http://review.gluster.org/6599 (cluster/afr: Unable to self heal symbolic links) posted (#7) for review on master by venkatesh somyajulu (vsomyaju)
COMMIT: http://review.gluster.org/6599 committed in master by Anand Avati (avati) ------ commit ce86c132347f0a788ab50ffbd6795a2eb982074e Author: Venkatesh Somyajulu <vsomyaju> Date: Fri Jan 3 13:54:25 2014 +0530 cluster/afr: Unable to self heal symbolic links Problem: Under the entry self heal, readlink is done at the source and sink. When readlink is done at the sink, because link is not present at the sink, afr expects ENOENT. AFR translator takes decisions for new link creation based on ENOENT but server translator is modified to return ESTALE because of which afr xlator is not able to heal. Fix: The check for inode absence at server includes ESTALE as well. Change-Id: I319e4cb4156a243afee79365b7b7a5a7823e9a24 BUG: 1046624 Signed-off-by: Venkatesh Somyajulu <vsomyaju> Reviewed-on: http://review.gluster.org/6599 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati>
COMMIT: http://review.gluster.org/6600 committed in release-3.5 by Niels de Vos (ndevos) ------ commit f46a3198b1a3d794c23b8ac2ab9334326c4918c8 Author: Venkatesh Somyajulu <vsomyaju> Date: Fri Jan 3 13:54:25 2014 +0530 cluster/afr: Unable to self heal symbolic links Problem: Under the entry self heal, readlink is done at the source and sink. When readlink is done at the sink, because link is not present at the sink, afr expects ENOENT. AFR translator takes decisions for new link creation based on ENOENT but server translator is modified to return ESTALE because of which afr xlator is not able to heal. Fix: The check for inode absence at server includes ESTALE as well. Change-Id: I9218da214ed44f7219570ad9dae298d6b5cbded9 BUG: 1046624 Signed-off-by: Venkatesh Somyajulu <vsomyaju> Reviewed-on: http://review.gluster.org/6600 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Niels de Vos <ndevos>
The first (and last?) Beta for GlusterFS 3.5.1 has been released [1]. Please verify if the release solves this bug report for you. In case the glusterfs-3.5.1beta release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-May/040377.html [2] http://supercolony.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-3.5.1, please reopen this bug report. glusterfs-3.5.1 has been announced on the Gluster Users mailinglist [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://supercolony.gluster.org/pipermail/gluster-users/2014-June/040723.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user