Hide Forgot
Self-heal is triggered even when there is no disconnection Client-log [2009-10-20 03:19:14] D [inode.c:572:__inode_replace] fuse/inode: inode(787820) replaced (787820 [2009-10-20 03:19:14] D [inode.c:572:__inode_replace] fuse/inode: inode(14943397) replaced (14943397 [2009-10-20 03:19:14] D [inode.c:572:__inode_replace] fuse/inode: inode(787808) replaced (787808 [2009-10-20 03:19:16] D [afr-self-heal-entry.c:1880:afr_sh_entry_sync_prepare] replicate2: self-healing directory /clients/client0/~dmtmp/WORDPRO from subvolume remote4 to 1 other [2009-10-20 03:19:16] D [afr-self-heal-entry.c:1880:afr_sh_entry_sync_prepare] replicate1: self-healing directory /clients/client1/~dmtmp/WORDPRO from subvolume remote2 to 1 other [2009-10-20 03:19:18] D [afr-self-heal-entry.c:1880:afr_sh_entry_sync_prepare] replicate2: self-healing directory /clients/client8/~dmtmp/WORDPRO from subvolume remote4 to 1 other [2009-10-20 03:19:19] D [inode.c:572:__inode_replace] fuse/inode: inode(722356) replaced (722356 [2009-10-20 03:19:19] D [afr-self-heal-entry.c:1880:afr_sh_entry_sync_prepare] replicate2: self-healing directory /clients/client6/~dmtmp/WORDPRO from subvolume remote4 to 1 other [2009-10-20 03:19:19] D [afr-self-heal-entry.c:1880:afr_sh_entry_sync_prepare] replicate2: self-healing directory /clients/client15/~dmtmp/WORDPRO from subvolume remote3 to 1 other [2009-10-20 03:19:19] D [afr-self-heal-entry.c:1880:afr_sh_entry_sync_prepare] replicate2: self-healing directory /clients/client1/~dmtmp/WORDPRO from subvolume remote4 to 1 other [2009-10-20 03:19:19] D [afr-self-heal-entry.c:1880:afr_sh_entry_sync_prepare] replicate2: self-healing directory /clients/client8/~dmtmp/WORDPRO from subvolume remote4 to 1 other [2009-10-20 03:19:19] D [inode.c:572:__inode_replace] fuse/inode: inode(787856) replaced (787856
This bug seems to be much older. It exists even in 2.0.4 . The dbench client dir doesn't delete itself on completion
*** Bug 330 has been marked as a duplicate of this bug. ***
PATCH: http://patches.gluster.com/patch/1982 in master (cluster/afr: Prevent spurious entry self-heal.)
PATCH: http://patches.gluster.com/patch/1983 in release-2.0 (cluster/afr: Prevent spurious entry self-heal.)
PATCH: http://patches.gluster.com/patch/2064 in master (storage/posix: Refactor xattrop)
PATCH: http://patches.gluster.com/patch/2065 in master (storage/posix: Serialize do_xattrop.)
PATCH: http://patches.gluster.com/patch/2066 in release-2.0 (storage/posix: Refactor xattrop)
PATCH: http://patches.gluster.com/patch/2067 in release-2.0 (storage/posix: Serialize do_xattrop.)
PATCH: http://patches.gluster.com/patch/2087 in master (cluster/afr: Don't try to self-heal if there are locks held)
PATCH: http://patches.gluster.com/patch/2090 in release-2.0 (cluster/afr: Don't try to self-heal if there are locks held)
PATCH: http://patches.gluster.com/patch/2516 in master (cluster/afr: Don't mark the fop as failed if rmdir returns ENOTEMPTY.)
PATCH: http://patches.gluster.com/patch/2598 in master (cluster/afr: Hold inode lock on 0-infinity for a flush transaction.)
PATCH: http://patches.gluster.com/patch/2599 in master (cluster/afr: Don't do entry self-heal in the background.)