Bug 140048 - gulm_put_lock called on a lock that is not unlocked!
gulm_put_lock called on a lock that is not unlocked!
Status: CLOSED CURRENTRELEASE
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: gulm (Show other bugs)
3
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Chris Feist
Cluster QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-11-19 09:38 EST by Derek Anderson
Modified: 2009-12-22 15:38 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-12-22 15:38:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
lockdump of /mnt/gfs1 on link-02 (332.94 KB, text/plain)
2004-11-19 09:39 EST, Derek Anderson
no flags Details

  None (edit)
Description Derek Anderson 2004-11-19 09:38:18 EST
Description of problem:

Nodes: link-01, link-02, link-08

Running vedder on a 3-node x86_64 cluster overnight.  During the 4th
iteration of revolver I started getting these messages on the link-02
console:

lock_gulm: ERROR On lock 0x4704676673310009090001001ab482000000
fsid=gfs1: gulm_put_lock called on a lock that is not unlocked!
Current state:0x1
lock_gulm: ERROR On lock 0x4704676673320009090001001ab48d000000
fsid=gfs2: gulm_put_lock called on a lock that is not unlocked!
Current state:0x1
lock_gulm: ERROR On lock 0x4704676673310009090001001bb1c2000000
fsid=gfs1: gulm_put_lock called on a lock that is not unlocked!
Current state:0x1link-02 login: lock_gulm: ERROR On lock
0x4704676673320009090001001cb159000000 fsid=gfs2: gulm_put_lock called
on a lock that is not unlocked! Current state:0x1

At this point link-02 is the Master.  The last thing that happened
was, link-08 was killed and rejoined the cluster.  I'll leave the
nodes in their current state for investigation.  Will also attach lock
dumps from link-02

Version-Release number of selected component (if applicable):
GFS-modules-smp-6.0.2-9

How reproducible:
First time seen.

Steps to Reproduce:
1.  Run 'vedder -S REG' or 'revolver' from sistina-test tree.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Derek Anderson 2004-11-19 09:39:19 EST
Created attachment 107054 [details]
lockdump of /mnt/gfs1 on link-02
Comment 2 Derek Anderson 2004-11-19 09:50:07 EST
lock_gulm dumps located in ~danderso/bugs/140048.
Comment 3 michael conrad tadpol tilstra 2004-11-19 09:57:05 EST
Other than the messages being printed out, is there anything not nice?
Comment 4 michael conrad tadpol tilstra 2004-11-19 14:03:40 EST
The message is extraneous.  Yet another case of something from the
past that I fixed, but left the old warning message in place.  Its
removed now.
Comment 5 Lon Hohberger 2009-12-22 15:38:56 EST
Cleanup.

This bugzilla should be resolved with the current packages from RHN for Red Hat Global File System for Red Hat Enterprise Linux 3.

GFS-6.0.2.36-9

Note You need to log in before you can comment on or make changes to this bug.