From: Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: fcntl locks prevent unmounting of underlying filesystem
Date: Sun, 30 May 2004 08:51:52 +1000
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <16569.5128.54766.582893@cse.unsw.edu.au>
References: <1085589795.20517.41.camel@tesla.mmt.bellhowell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: nfs@lists.sourceforge.net
To: Jeffrey Layton <jtlayton@poochiereds.net>
In-Reply-To: message from Jeffrey Layton on Wednesday May 26
Errors-To: nfs-admin@lists.sourceforge.net

On Wednesday May 26, jtlayton@poochiereds.net wrote:
> I've seem to have run across a problem with NFS and fcntl locks. I'm
> trying to implement a HA-NFS solution using heartbeat, DRBD, LVM2, etc.
> I'm running the following:
> 
> 2.6.6 kernel
> nfs-kernel-server and nfs-common 1.0.6-3 (debian packages)
> 
> The underlying filesystem is reiserfs. Essentially what I'm seeing is
> that when I try to shut down NFS and unmount the filesystem for a
> failover, I'm unable to unmount if I have an fcntl lock on the file.

You need to make sure that lockd gets killed as well.
Just shutting down nfsd doesn't necessarily kill lockd, as if you have
any active nfs mounts lockd will stay up for them.
So, when you have shut down nfsd and before you try to unmount, could
you check if lockd is still running or not?
If it is, send it a SIGKILL.  It won't exit, but it should release any
locks that it is holding.

If lockd has gone away at this point but locks are still being held,
then that is a real problem and I will try to look into it.

NeilBrown


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs