Red Hat Bugzilla – Bug 1477169
AFR entry self heal removes a directory's .glusterfs symlink.
Last modified: 2017-12-08 12:36:32 EST
Description of problem:
Steps to Reproduce:
-Create 1x2 replica, fuse mount it
-kill one brick and rename the dir: `mv fuse_mount/d1/dir use_mount/d2`
-Bring all bricks up and trigger heal.
fuse_mount/d2/dir won't have any gfid symlink.
For replica 3 volume, the heal won't even complete, see the .t attached.
REVIEW: https://review.gluster.org/17945 (posix: add sanity checks for removing the gfid symlink for directories) posted (#1) for review on master by Ravishankar N (firstname.lastname@example.org)
REVIEW: https://review.gluster.org/17945 (posix: add sanity checks for removing the gfid symlink for directories) posted (#2) for review on master by Ravishankar N (email@example.com)
COMMIT: https://review.gluster.org/17945 committed in master by Jeff Darcy (firstname.lastname@example.org)
Author: Ravishankar N <email@example.com>
Date: Mon Jul 31 23:38:20 2017 +0530
posix: add sanity checks for removing the gfid symlink for directories
...during mkdir and rmdir. Otherwise, during entry self-heal, the
directory could be left out without a .glusterfs symlink causing fops like
opendir, readdir to fail. The only chance the missing symlink will be
created is when a fresh lookup comes on it.
Signed-off-by: Ravishankar N <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Raghavendra Bhat <email@example.com>
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.13.0, please open a new bug report.
glusterfs-3.13.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.