[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



--- Comment #5 from Chen Chen <aflyhorse at hotmail.com> ---
Any scheduled update? I don't know what is the GlusterFS equivalent of RHGS
3.1.3.

Again, another tight lock here. Couldn't release by force start. So I
cold-reset the infected node (which has a noticable huge 1min-load).

[xlator.features.locks.mainvol-locks.inode]
path=<gfid:62adaa3a-a1b8-458c-964f-5742f942cd0f>/.WGC037694D_combined_R1.fastq.gz.gzT9LR
mandatory=0
inodelk-count=38
lock-dump.domain.domain=mainvol-disperse-1:self-heal
inodelk.inodelk[0](ACTIVE)=type=WRITE, whence=0, start=0, len=0, pid =
18446744073709551610, owner=c4dd93ee0c7f0000, client=0x7f3eb4887cc0,
connection-id=hw10-18694-2016/05/02-05:57:47:620063-mainvol-client-6-0, blocked
at 2016-05-11 08:22:56, granted at 2016-05-11 08:27:07
inodelk.inodelk[1](BLOCKED)=type=WRITE, whence=0, start=0, len=0, pid =
18446744073709551610, owner=98acff20d77f0000, client=0x7f3ea869e250,
connection-id=sm16-23349-2016/05/02-05:57:01:49902-mainvol-client-6-0, blocked
at 2016-05-11 08:27:07
inodelk.inodelk[2](BLOCKED)=type=WRITE, whence=0, start=0, len=0, pid =
18446744073709551610, owner=8004a958097f0000, client=0x7f3ebc66e630,
connection-id=sm15-28555-2016/05/02-05:57:53:27608-mainvol-client-6-0, blocked
at 2016-05-11 08:27:07
......(tailored)

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