Bug 818578 - [glusterfs-3.3.0qa39]: blocked entrylks when rm -rf and replace-brick happening parallely
Summary: [glusterfs-3.3.0qa39]: blocked entrylks when rm -rf and replace-brick happeni...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact: Pranith Kumar K
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-05-03 12:30 UTC by Raghavendra Bhat
Modified: 2013-07-24 17:19 UTC (History)
1 user (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:19:04 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions: glusterfs-3.3.0qa40
Embargoed:


Attachments (Terms of Use)
statedump of the source brick (359.63 KB, application/octet-stream)
2012-05-03 12:31 UTC, Raghavendra Bhat
no flags Details

Description Raghavendra Bhat 2012-05-03 12:30:41 UTC
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.features.locks.new-locks.inode]
path=<gfid:4a142098-c7be-40d0-9fcf-04cf9f8fe2e5>
mandatory=0
entrylk-count=2
lock-dump.domain.domain=new-pump
xlator.feature.locks.lock-dump.domain.entrylk.entrylk[0](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[1](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):


How reproducible:


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)
  
Actual results:

rm -rf hung due to blocked entrylks

Expected results:

rm -rf should not hang

Additional info:

Comment 1 Raghavendra Bhat 2012-05-03 12:31:48 UTC
Created attachment 581848 [details]
statedump of the source brick

Comment 2 Anand Avati 2012-05-03 19:22:21 UTC
CHANGE: http://review.gluster.com/3270 (cluster/afr: Fix race in nonblocking entrylk) merged in master by Anand Avati (avati)

Comment 3 Raghavendra Bhat 2012-05-10 07:26:23 UTC
Tested with glusterfs-3.3.0qa40 and rm -rf completed successfully without hanging when replace-brick was going on and replace-brick also completed.


Note You need to log in before you can comment on or make changes to this bug.