From: "Lever, Charles" <Charles.Lever@netapp.com>
Subject: RE: Re: broken umount -f
Date: Tue, 14 Jan 2003 11:36:29 -0800
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <6440EA1A6AA1D5118C6900902745938E07D551EB@black.eng.netapp.com>
Mime-Version: 1.0
Content-Type: text/plain
Cc: nfs@lists.sourceforge.net
To: "'Scott Mcdermott'" <smcdermott@questra.com>
Errors-To: nfs-admin@lists.sourceforge.net

> -----Original Message-----
> From: Scott Mcdermott [mailto:smcdermott@questra.com]
> Sent: Tuesday, January 14, 2003 2:20 PM
> To: Trond Myklebust
> Cc: nfs@lists.sourceforge.net
> Subject: Re: [NFS] Re: broken umount -f
> 
> 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.


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