[Bugs] [Bug 1455049] [GNFS+EC] Unable to release the lock when the other client tries to acquire the lock on the same file

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1455049



--- Comment #3 from Ashish Pandey <aspandey at redhat.com> ---



[xlator.features.locks.testvol-locks.inode]
path=/file
mandatory=0
inodelk-count=1
lock-dump.domain.domain=testvol-disperse-0
inodelk.inodelk[0](ACTIVE)=type=WRITE, whence=0, start=0, len=0, pid = 20283,
owner=70e500f8957f0000, client=0x7f6ff80b08b0,
connection-id=apandey-20134-2017/05/24-07:57:36:665823-testvol-client-0-0-0,
granted at 2017-05-24 07:59:24   <<<<<<<<<<<<< EC lock taken by second lock
request 
posixlk-count=2  
posixlk.posixlk[0](ACTIVE)=type=WRITE, whence=0, start=0, len=10, pid = 20266,
owner=2f33c5d2250866c3, client=0x7f6ff80b08b0, connection-id=(null), granted at
2017-05-24 07:58:18   <<<<<<<<<<<<<< Posix lock taken by first lock request 

posixlk.posixlk[1](BLOCKED)=type=WRITE, whence=0, start=0, len=10, pid = 20283,
owner=9f4f2ac611372d51, client=0x7f6ff80b08b0, connection-id=(null), blocked at
2017-05-24 07:59:24  <<<<<<<<<<<<<< Second posix lock  request BLOCKED 


Now, to unlock the first posix lock, we have to take EC lock which can not be
taken as it is taken by second request.

That caused deadlock.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.