Linux NFS development
 help / color / mirror / Atom feed
From: Scott Mcdermott <smcdermott@questra.com>
To: nfs@lists.sourceforge.net
Subject: Re: Re: broken umount -f
Date: Wed, 15 Jan 2003 00:19:28 -0500	[thread overview]
Message-ID: <20030115051928.GB30478@questra.com> (raw)
In-Reply-To: <6440EA1A6AA1D5118C6900902745938E07D551EB@black.eng.netapp.com>

Lever, Charles on Tue 14/01 11:36 -0800:
> > 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.
> 
> do you remember which kernel this was?
> 
> trond fixed a long-standing "processes stuck in 'D' state" bug in
> 2.4.20.  this bug may be the reason these processes didn't die when
> you killed them.

<on client>

# uname -r
2.4.21-pre3-NFS_ALL

# showmount --exports nfsserver
Export list for nfsserver
/tmp           10.0.0.5

# mount nfsserver:/tmp /mnt/tmp

# cd /mnt/tmp

# ssh nfsserver /etc/init.d/nfs stop
Shutting down NFS mountd: [  OK  ]
Shutting down NFS daemon: [  OK  ]
Shutting down NFS services:  [  OK  ]
Shutting down NFS quotas: [  OK  ]

# /bin/pwd
nfs: server nfsserver not responding, still trying

<hangs>

<now on other tty with pwd=/>

# ps -eo state,wchan,pid,command | grep ^D
D end     1472 /bin/pwd

# kill -KILL 1472

# umount -f /mnt/tmp
Cannot MOUNTPROG RPC: RPC: Program not registered
umount2: Device or resource busy
umount: /mnt/tmp: device is busy

# kill -KILL 1472
# kill -KILL 1472

# umount -f /mnt/tmp
Cannot MOUNTPROG RPC: RPC: Program not registered
umount2: Device or resource busy
umount: /mnt/tmp: device is busy

# kill -KILL 1472
# kill -KILL 1472
# kill -KILL 1472
# kill -KILL 1472
# kill -KILL 1472
# kill -KILL 1472
# kill -KILL 1472

# umount -f /mnt/tmp
Cannot MOUNTPROG RPC: RPC: Program not registered
umount2: Device or resource busy
umount: /mnt/tmp: device is busy

# kill -KILL 1472

# ps -eo state,wchan,pid,command | grep ^D
D end     1472 /bin/pwd


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

  reply	other threads:[~2003-01-15  5:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14 19:36 Re: broken umount -f Lever, Charles
2003-01-15  5:19 ` Scott Mcdermott [this message]
2003-01-15  5:21   ` Scott Mcdermott
  -- strict thread matches above, loose matches on Subject: below --
2003-01-16 19:45 Re: Broken " Cole, Timothy D.
2003-01-16 19:56 ` Scott Mcdermott
2003-01-15 19:59 Heflin, Roger A.
2003-01-16  3:37 ` Scott Mcdermott
2003-01-15 18:46 Re: broken " Cole, Timothy D.
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 15:35 Murata, Dennis W (SAIC)
2003-01-15 14:45 Lever, Charles
2003-01-15 16:32 ` Scott Mcdermott
2003-01-14 19:49 Cole, Timothy D.
2003-01-14 19:30 Cole, Timothy D.
2003-01-14 15:56 [NFS] " 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
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

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=20030115051928.GB30478@questra.com \
    --to=smcdermott@questra.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox