From: Jeff Layton <jtlayton@poochiereds.net>
Subject: Re: fcntl locks prevent unmounting of underlying filesystem
Date: Sun, 30 May 2004 06:53:04 -0400
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <1085914384.3079.2.camel@localhost>
References: <1085589795.20517.41.camel@tesla.mmt.bellhowell.com>
	 <16569.5128.54766.582893@cse.unsw.edu.au>
Mime-Version: 1.0
Content-Type: text/plain
Cc: nfs@lists.sourceforge.net
To: Neil Brown <neilb@cse.unsw.edu.au>
In-Reply-To: <16569.5128.54766.582893@cse.unsw.edu.au>
Errors-To: nfs-admin@lists.sourceforge.net

> 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

Ahh, Thanks for the info! That does indeed seem to take care of the hold
on the underlying filesystem. I need to do a little more testing to see
how locks are handled, but that at least removes my current logjam.

Cheers!
-- 
Jeff Layton <jtlayton@poochiereds.net>


-------------------------------------------------------
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