Red Hat Bugzilla – Bug 818578
[glusterfs-3.3.0qa39]: blocked entrylks when rm -rf and replace-brick happening parallely
Last modified: 2013-07-24 13:19:04 EDT
Description of problem:
Created a single brick volume. Untarred linux-kernel tarball and glusterfs tarball. Gave replace-brick and after some time ran rm -rf on the fuse mount parallely.
After somefiles were deleted rm -rf hung.
xlator.feature.locks.lock-dump.domain.entrylk.entrylk(ACTIVE)=type=ENTRYLK_WRLCK on basename=.sys_ia32.o.cmd, pid = 484620988, owner=bcbae2
1c097f0000, transport=(nil), , granted at Thu May 3 15:49:45 2012
xlator.feature.locks.lock-dump.domain.entrylk.entrylk(BLOCKED)=type=ENTRYLK_WRLCK on basename=.sys_ia32.o.cmd, pid = 484620988, owner=bcbae21c097f0000, transport=(nil), , blocked at Thu May 3 15:49:45 2012
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a single brick volume and start it.
2. Create files and directories (may be untarring of linux-kernel, glusterfs etc)
3. Give replace brick and after some time do rm -rf on the mount point (replace-brick should be going on)
rm -rf hung due to blocked entrylks
rm -rf should not hang
Created attachment 581848 [details]
statedump of the source brick
CHANGE: http://review.gluster.com/3270 (cluster/afr: Fix race in nonblocking entrylk) merged in master by Anand Avati (firstname.lastname@example.org)
Tested with glusterfs-3.3.0qa40 and rm -rf completed successfully without hanging when replace-brick was going on and replace-brick also completed.