Date: Fri, 20 Jul 2001 02:50:01 -0700 (PDT) From: Ian Dowse <iedowse@maths.tcd.ie> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/11005: `umount -f' does not work if the NFS-server is down Message-ID: <200107200950.f6K9o1v60889@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/11005; it has been noted by GNATS. From: Ian Dowse <iedowse@maths.tcd.ie> To: mike@FreeBSD.org Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: bin/11005: `umount -f' does not work if the NFS-server is down Date: Fri, 20 Jul 2001 10:40:54 +0100 In message <200107200153.f6K1rqE67671@freefall.freebsd.org>, mike@FreeBSD.org w rites: >Synopsis: `umount -f' does not work if the NFS-server is down > >State-Changed-From-To: open->closed >This is apparently a duplicate of PR: bin/841. That PR says that >this problem should be fixed in 3.3-RELEASE and up. Yes, umount -f seems to work now if the server is down, but only if there are no outstanding operations in progress. If the NFS mount isn't interruptible then there is no way to cancel outstanding operations, so umount -f will just hang forever. I guess this is expected behaviour if you specifically ask for a non-interruptible mount (by not adding the -i option to mount_nfs). It's maybe not so expected behaviour if you have to kill all the stuck processes on an interruptible NFS mount before umount -f works. I guess in the forced case, the NFS unmount code could go around and mark all outstanding requests as terminated. I'll think about this a bit more, and I might grab and reopen the PR if it seems feasible. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200107200950.f6K9o1v60889>