Bug 771595

Summary: [glusterfs-3.3.0qa19]: application hung due to blocked locks
Product: [Community] GlusterFS Reporter: Raghavendra Bhat <rabhat>
Component: replicateAssignee: Pranith Kumar K <pkarampu>
Status: CLOSED CURRENTRELEASE QA Contact: Raghavendra Bhat <rabhat>
Severity: high Docs Contact:
Priority: high    
Version: pre-releaseCC: gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.4.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-24 17:58:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: glusterfs-3.3.0qa43 Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 817967    

Description Raghavendra Bhat 2012-01-04 09:12:11 UTC
Description of problem:
2x2 distributed replicate volume with quota and profile enabled. 1 fuse client executing a multithreaded program. 1 nfs client executing fs-perf-test. While tests were going had done replace brick twice. The multithreaded application i(which spawns threads, with each thread opening the same file, and performing different fops on their respective fds such as read, write, fcntl locking etc) is hung. No server was brought down. Statedumps indicate that blocked locks are present.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:

inodelk.inodelk[0](ACTIVE)=type=WRITE, start=9223372036854775806, len=0, pid=18446744072315678016, lk-owner=140250763177280, transport=0x23434
60, blocked at Wed Jan  4 03:26:26 2012
, granted at  Wed Jan  4 03:26:26 2012

inodelk.inodelk[1](ACTIVE)=type=WRITE, start=0, len=131072, pid=18446744073709551615, lk-owner=140250764101896, transport=0x2343460, granted a
t  Wed Jan  4 03:26:26 2012

inodelk.inodelk[2](BLOCKED)=type=WRITE, start=0, len=0, pid=18446744073709551615, lk-owner=140250764101896, transport=0x2343460, blocked at  Wed Jan  4 03:26:26 2012


Expected results:


Additional info:

Comment 1 Pranith Kumar K 2012-01-05 05:19:20 UTC
Johnny,
   Do you have the logs and statedumps of clients, bricks somewhere we can check?.
   Are you observing this issue on every run of this testcase?.

Pranith

Comment 2 Amar Tumballi 2012-03-12 09:46:59 UTC
please update these bugs w.r.to 3.3.0qa27, need to work on it as per target milestone set.

Comment 3 Anand Avati 2012-05-19 08:22:34 UTC
CHANGE: http://review.gluster.com/3370 (protocol/server: del_locker should delete one locker per unlock) merged in master by Anand Avati (avati)

Comment 4 Raghavendra Bhat 2012-05-21 07:38:04 UTC
Bug has been reproduced and patch has been submitted for this.

Comment 5 Raghavendra Bhat 2012-05-25 06:00:06 UTC
Checked with glusterfs-3.3.0qa43. And did not find the blocked inodelks.