Bug 191807

Summary: lock_dlm assert line 428
Product: [Retired] Red Hat Cluster Suite Reporter: Lenny Maiorani <lenny>
Component: dlmAssignee: David Teigland <teigland>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: ccaulfie, cluster-maint, riaanvn
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-11-27 16:41:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
backtrace, stack dump, process list none

Description Lenny Maiorani 2006-05-15 21:15:02 UTC 
Was attempting to reboot a kdb'd node when node4 kdb'd with a lock_dlm
assertion. See attachment for console logs.

node4 had a CIFS share attached which was running from a Windows client.
When node3 was rebooted, this node kdb'd.

Kernel issued an assert from lock_dlm
lock_dlm:  Assertion failed on line 428 of file fs/gfs_locking/lock_dlm/lock.c
Comment 1 Lenny Maiorani 2006-05-15 21:15:02 UTC 
Created attachment 129123 [details]
backtrace, stack dump, process list
Comment 2 Christine Caulfield 2006-05-16 13:09:34 UTC 
I'd need to see a lot more of the syslog above that error to be sure, but I
suspect this is an instance of bug 187777
Comment 3 David Teigland 2006-09-21 15:50:19 UTC 
Has this issue been seen recently?
Comment 5 David Teigland 2006-11-27 16:41:30 UTC 
We'll reopen this if it's seen again.