From: Brian Tinsley <btinsley@emageon.com>
To: Scott Mcdermott <smcdermott@questra.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Re: broken umount -f
Date: Tue, 14 Jan 2003 13:32:44 -0600 [thread overview]
Message-ID: <3E2465DC.8000706@emageon.com> (raw)
In-Reply-To: 20030114191953.GJ26872@questra.com
Scott Mcdermott wrote:
>Trond Myklebust on Tue 14/01 20:06 +0100:
>
>
>>Linux will not allow you to unmount without killing those processes,
>>and I'd be opposed to any patch that tries to kill active processes
>>from within the filesystem. This is something that needs to be
>>resolved in userland.
>>
>>
>
>Last I checked, the programs wouldn't die even with -KILL when they were
>stuck in device-wait state. The only way to reboot a machine with such
>processes is to reboot -f, which is wrong. The filesystems should be
>able to have forced umount at sysadmin's discretion.
>
>
I've had luck with:
kill -9 <pids>
umount -f <nfs_dirs>
kill -9 <pids>
umount -f <nfs_dirs>
The last umount always works for me.
--
Brian Tinsley
Chief Systems Engineer
Emageon
-------------------------------------------------------
This SF.NET email is sponsored by: Take your first step towards giving
your online business a competitive advantage. Test-drive a Thawte SSL
certificate - our easy online guide will show you how. Click here to get
started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-01-14 19:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 15:56 [NFS] Re: broken umount -f Lever, Charles
2003-01-14 15:56 ` Lever, Charles
2003-01-14 17:07 ` Scott Mcdermott
2003-01-14 19:06 ` Trond Myklebust
2003-01-14 19:19 ` Scott Mcdermott
2003-01-14 19:32 ` Brian Tinsley [this message]
2003-01-14 19:35 ` Trond Myklebust
2003-01-14 22:17 ` Scott Mcdermott
2003-01-14 22:29 ` Steven N. Hirsch
2003-01-14 22:27 ` Steven N. Hirsch
2003-01-14 19:39 ` Benjamin LaHaise
2003-01-14 19:52 ` Trond Myklebust
2003-01-14 19:56 ` Benjamin LaHaise
-- strict thread matches above, loose matches on Subject: below --
2003-01-14 19:30 Cole, Timothy D.
2003-01-14 19:36 Lever, Charles
2003-01-15 5:19 ` Scott Mcdermott
2003-01-15 5:21 ` Scott Mcdermott
2003-01-14 19:49 Cole, Timothy D.
2003-01-15 14:45 Lever, Charles
2003-01-15 16:32 ` Scott Mcdermott
2003-01-15 15:35 Murata, Dennis W (SAIC)
2003-01-15 17:04 Lever, Charles
2003-01-15 17:23 ` Scott Mcdermott
[not found] ` <20030115130759.B11894@ti19>
2003-01-15 18:22 ` Bill Rugolsky Jr.
2003-01-15 18:24 ` Scott Mcdermott
2003-01-16 20:49 ` Ion Badulescu
2003-01-15 18:46 Cole, Timothy D.
2003-01-15 19:59 Broken " Heflin, Roger A.
2003-01-16 3:37 ` Scott Mcdermott
2003-01-16 19:45 Cole, Timothy D.
2003-01-16 19:56 ` Scott Mcdermott
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=3E2465DC.8000706@emageon.com \
--to=btinsley@emageon.com \
--cc=nfs@lists.sourceforge.net \
--cc=smcdermott@questra.com \
/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.