From: Jeff Layton <jtlayton@poochiereds.net>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: nfs@lists.sourceforge.net
Subject: Re: fcntl locks prevent unmounting of underlying filesystem
Date: Sun, 30 May 2004 06:53:04 -0400 [thread overview]
Message-ID: <1085914384.3079.2.camel@localhost> (raw)
In-Reply-To: <16569.5128.54766.582893@cse.unsw.edu.au>
> 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
next prev parent reply other threads:[~2004-05-30 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 16:43 fcntl locks prevent unmounting of underlying filesystem Jeffrey Layton
2004-05-27 14:27 ` Jeffrey Layton
2004-05-27 17:31 ` Jeffrey Layton
2004-05-29 22:51 ` Neil Brown
2004-05-30 10:53 ` Jeff Layton [this message]
2004-06-04 12:03 ` [NFS] " Jeffrey Layton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1085914384.3079.2.camel@localhost \
--to=jtlayton@poochiereds.net \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.