From: Erik Hensema <erik@hensema.net>
Subject: Locking broke after client reset
Date: Thu, 11 Oct 2007 15:50:20 +0200
Message-ID: <200710111550.22405.erik@hensema.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: nfs@lists.sourceforge.net
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

Situation:

openSUSE 10.2 NFS server, 2.6.18 kernel as supplied by novell.
openSUSE 10.1 client, 2.6.16 kernel as supplied by novell.

After a crash of the client and a reboot, locking over nfs broke. 
Processes just wait indefinitely on a lock they'll never get.
Rebooting the client doesn't help.

Restarting the nfs server by removing all kernel modules and reloading 
doesn't help either. I'd like to avoid rebooting the machine if 
possible.

How can I reset the locks? It's no problem to unmount the share on all 
clients if necessary.

I'm using nfsv4. Possibly the NLM lock recovery fails because the name 
returned by 'uname -n' does not fully match the reverse dns of the 
machine. I'm not sure how to make uname -n return the internal dns 
name but still have daemons such as sendmail use the external name 
(the machine's got two interfaces, one on the internet, one internal 
to the nfs server).
Currently uname -n returns the short hostname of the machine, not a 
fully qualified one.

Any help would be appreciated.

Met vriendelijke groet,

Erik Hensema
-- 
Email: erik@hensema.net
Website: http://www.hensema.net/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs