Bug 436174

Summary:	nfslock failing
Product:	Red Hat Enterprise Linux 5	Reporter:	Mike McGrath <mmcgrath>
Component:	nfs-utils	Assignee:	Steve Dickson <steved>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	5.1	CC:	nstraz
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-09-18 14:56:37 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:

Description Mike McGrath 2008-03-05 19:15:44 UTC

Description of problem:
nfslock seems to be freezing and causing locking to fail.  It can't be restarted
and seems to be holding the port open.  Only a reboot of the machine has seemed
to fix it.

Steps to reproduce:
We've not been able to force this to happen, it seems to happen between 1 and 3
times a week.

Comment 1 Mike McGrath 2008-03-22 12:48:53 UTC

ping?

Comment 2 Steve Dickson 2008-03-24 11:34:51 UTC

The next time the hang happens, please get a system backtrack
by doing a "echo t > /proc/sysrq-trigger" and then doing
a "dmesg > /tmp/dmesg". That will at least give me a starting
point...

Comment 3 RHEL Program Management 2008-06-02 20:15:33 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 4 Steve Dickson 2008-09-18 14:07:12 UTC

Mike,

This problem has basically gone way after a ext3 problem was fixed, true?

Comment 5 Mike McGrath 2008-09-18 14:28:37 UTC

I think so, I've seen it maybe once or twice since then.  But its not happening many times a week as it was.  I'd say go ahead and close the ticket (especially if no one else is seeing the problem)  And if something creeps up again I'll re-open it or open a new one.