[Bugs] [Bug 1329466] Gluster brick got inode-locked and freeze the whole cluster

[bugzilla at redhat.com]

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

Chen Chen <aflyhorse at hotmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?(aflyhorse at hotmail |
                   |.com)                       |



--- Comment #4 from Chen Chen <aflyhorse at hotmail.com> ---
I was running GATK CombineVariants (multi-threaded mode, -nt 16) when I noticed
this inode lock. I executed this from one client system.
https://www.broadinstitute.org/gatk/guide/tooldocs/org_broadinstitute_gatk_tools_walkers_variantutils_CombineVariants.php

Besides, in another lock (which failed to recover from "start force"), I was
running GATK HaplotypeCaller (single-threaded) from multiple clients.

The following is the statedump snapshot from this lock. I don't really know why
there were *write* operation on GATK jar. Both the brick and the volume were
mounted with noatime flag, and "ls -la" showed it has not been modified since I
downloaded the jar.

[xlator.features.locks.mainvol-locks.inode]
path=/home/analyzer/softs/bin/GenomeAnalysisTK.jar
mandatory=0
inodelk-count=4
lock-dump.domain.domain=mainvol-disperse-0:self-heal
lock-dump.domain.domain=mainvol-disperse-0
inodelk.inodelk[0](ACTIVE)=type=WRITE, whence=0, start=0, len=0, pid = 1,
owner=dc2d3dfcc57f0000, client=0x7ff03435d5f0,
connection-id=sm12-8063-2016/04/01-07:51:46:892384-mainvol-client-0-0-0,
blocked at 2016-04-01 16:52:58, granted at 2016-04-01 16:52:58
inodelk.inodelk[1](BLOCKED)=type=WRITE, whence=0, start=0, len=0, pid = 1,
owner=1414371e1a7f0000, client=0x7ff034204490,
connection-id=hw10-17315-2016/04/01-07:51:44:421807-mainvol-client-0-0-0,
blocked at 2016-04-01 16:58:51
inodelk.inodelk[2](BLOCKED)=type=WRITE, whence=0, start=0, len=0, pid = 1,
owner=a8eb14cd9b7f0000, client=0x7ff01400dbd0,
connection-id=sm14-879-2016/04/01-07:51:56:133106-mainvol-client-0-0-0, blocked
at 2016-04-01 17:03:41
inodelk.inodelk[3](BLOCKED)=type=WRITE, whence=0, start=0, len=0, pid = 1,
owner=b41a0482867f0000, client=0x7ff01800e670,
connection-id=sm15-30906-2016/04/01-07:51:45:711474-mainvol-client-0-0-0,
blocked at 2016-04-01 17:05:09

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