Red Hat Bugzilla – Bug 382671
mount hung after recovery, lock_gulmd_LT in busy wait
Last modified: 2009-04-16 16:33:45 EDT
Description of problem:
While doing GFS recovery testing with lock_gulm a mount hung after shooting only
one node. The lock_gulmd_LT threads on all nodes are very busy. I did a packet
capture of port 41040 on the master to hopefully shed some light on what is
Version-Release number of selected component (if applicable):
Senario iteration 1.1 started at Tue Nov 13 16:09:51 CST 2007
Sleeping 5 minute(s) to let the I/O get its lock count up...
Senario: GULM kill Master
Those picked to face the revolver... morph-05
checking Gulm recovery...
Verifying that clvmd was started properly on the dueler(s)
mounting /dev/mapper/morph--cluster-morph--cluster0 on /mnt/morph-cluster0 on
mounting /dev/mapper/morph--cluster-morph--cluster1 on /mnt/morph-cluster1 on
The mount should not hang.
The recovery was done with a load on each node.
Created attachment 258231 [details]
gzipped tcpdump of port 41040 from morph-01
I think I've hit this twice now. The most recent time I thought it was a hung
mount after losing quorum, but after re-fencing the nodes which were fenced the
mount did not continue.
*** This bug has been marked as a duplicate of 252209 ***