From owner-freebsd-bugs Fri Jul 20 17: 4:44 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9218737B406; Fri, 20 Jul 2001 17:04:33 -0700 (PDT) (envelope-from iedowse@FreeBSD.org) Received: (from iedowse@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f6L01te46431; Fri, 20 Jul 2001 17:01:55 -0700 (PDT) (envelope-from iedowse) Date: Fri, 20 Jul 2001 17:01:55 -0700 (PDT) From: Message-Id: <200107210001.f6L01te46431@freefall.freebsd.org> To: mi@aldan.algebra.com, iedowse@FreeBSD.org, freebsd-bugs@FreeBSD.org, iedowse@FreeBSD.org Subject: Re: bin/11005: `umount -f' does not work if the NFS-server is down Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: `umount -f' does not work if the NFS-server is down State-Changed-From-To: closed->open State-Changed-By: iedowse State-Changed-When: Fri Jul 20 16:44:59 PDT 2001 State-Changed-Why: I've looked into this a bit further, and it seems to be relatively straightforward to make umount -f work in all cases, including when processes are uninterruptibly hung. We need to set a non-zero socket timeout even for non-interruptible mounts, and then for a forced unmount, walk the list of outstanding requests for that mountpoint, marking each one with R_SOFTTERM. There are still a few details to be ironed out, so it may be a while before I get around to implementing this. I'll take the PR as a reminder. Responsible-Changed-From-To: freebsd-bugs->iedowse Responsible-Changed-By: iedowse Responsible-Changed-When: Fri Jul 20 16:44:59 PDT 2001 Responsible-Changed-Why: I'll look into this. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=11005 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message