From owner-freebsd-hackers Sun Aug 29 12:18:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by hub.freebsd.org (Postfix) with ESMTP id 4102815884; Sun, 29 Aug 1999 12:18:00 -0700 (PDT) (envelope-from blapp@attic.ch) Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by bastian.attic.ch (8.9.1a/8.9.1a) with SMTP id VAA21908; Sun, 29 Aug 1999 21:16:58 +0200 (CEST) Date: Sun, 29 Aug 1999 21:16:57 +0200 (CEST) From: Martin Blapp To: hackers@FreeBSD.ORG Cc: dillon@apollo.backplane.com, alfred@FreeBSD.ORG Subject: NFS unmounts while reboot ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Problem: -------- As I notized, a FreeBSD NFS-client does not unmount it's NFS-mounts during reboot. This can cause problems on the server if it's not BSD. At least Linux complains if there are still nfs-mounted filesystems on the server. It also would be a Good Thing (TM) if /var/db/mountdtab is properly handled. Umount(8) is fixed now for doing the rpc calls properly and the patch is reviewed by Alfred and billf. Description: ------------ One could just made a quick and dirty solution as Linux has, like one line in rc.shutdown: umount -Avt nfs The problem with this solution is that umount just hangs if one nfs server is not available. If umount does hang, reboot hangs too. There exists also 'umount -f' , but this does not do the rpc call to the server. Possible Solutions: ------------------ 1.) Add a option to umount to accept some max. delay. If the Server does not respond, we just do the next unmount. 2.) fork some prozess in background that does the rpc call. We don't wait till it is back. What do you propose and think about this issue ? Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message