Red Hat Bugzilla – Bug 765572
Detect and repair root gfid when a volume is created from a former volume's parent dir
Last modified: 2014-08-24 20:49:17 EDT
The following was reported via IRC where the user had created a volume using /hekafs-export/www as the brick directory. Later, he removed that volume and used /hekafs-export as the brick directory. This led to an endless series of this error message:
Dec 2 01:32:44 hakafs01 GlusterFS: [2011-12-02 01:32:44.661161] C [inode.c:232:__is_dentry_cyclic] 0-posix-acl-autoload/inode: detected cyclic loop formation during inode linkage. inode (1/00000000-0000-0000-0000-000000000001) linking under itself as www
getfattr -m . -d -e hex /hekafs-export /hekafs-export/www
getfattr: Entferne führenden '/' von absoluten Pfadnamen
# file: hekafs-export
# file: hekafs-export/www
The user did not understand the error message, nor was he able to deduce from the error what needed to be done to correct the problem. It seems like this should be able to be self-corrected.
CHANGE: http://review.gluster.com/781 (extras: clean up a brick's gfid xattr) merged in master by Vijay Bellur (email@example.com)
CHANGE: http://review.gluster.com/2514 (extras: add check for brick path existence) merged in master by Vijay Bellur (firstname.lastname@example.org)
This patch doesn't seem to do any behavioural changes. Its just a script clear_xattr.sh in the glusterFS source which can be used to remove xattr from the bricks previously belong to some other volume. I think this should be documented properly. Moving it to DP .
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.0, please reopen this bug report.
glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist , 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.