From: Scott Mcdermott Subject: Re: Re: broken umount -f Date: Tue, 14 Jan 2003 14:19:53 -0500 Sender: nfs-admin@lists.sourceforge.net Message-ID: <20030114191953.GJ26872@questra.com> References: <6440EA1A6AA1D5118C6900902745938E07D551E8@black.eng.netapp.com> <20030114170755.GA18952@questra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: nfs@lists.sourceforge.net Return-path: Received: from ns1.questra.com ([64.132.48.186]) by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 18YWbL-0001sr-00 for ; Tue, 14 Jan 2003 11:19:55 -0800 Received: from questra.com (hades.roc.questra.com [64.132.48.226]) by ns1.questra.com (Postfix) with SMTP id D7AFBAB7A3 for ; Tue, 14 Jan 2003 14:19:53 -0500 (EST) To: Trond Myklebust In-Reply-To: Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: 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. ------------------------------------------------------- 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