From owner-freebsd-hackers Sat Jul 21 0:37:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 60CEB37B403 for ; Sat, 21 Jul 2001 00:37:55 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.134.98.Dial1.SanJose1.Level3.net [209.245.134.98]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA06609; Sat, 21 Jul 2001 00:37:49 -0700 (PDT) Message-ID: <3B593172.1AD11A3@mindspring.com> Date: Sat, 21 Jul 2001 00:38:26 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ian Dowse Cc: mjacob@feral.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Default retry behaviour for mount_nfs References: <200107202327.aa64363@salmon.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ian Dowse wrote: > > In message <3B585C76.696F1E2A@mindspring.com>, Terry Lambert writes: > >> FWIW, I vote that we rever to the traditional default and require > >> -R1 or -b to avoid boot time hangs. The standard behaviour for most > >> NFS implementations that I'm aware of would do this. > > > >I agree; people at work have bitched about this. We have a > >FreeBSD NFS server that's flakey. > > Ok, from the small set of responses so far, it seems that the most > acceptable option is to change mount_nfs to behave in the old way > where it will retry forever by default even in foreground mode. > Below is a proposed patch that does this. It also adds two paragraphs > near the start of the manpage which describe the default behaviour > and point readers at the relevant options. Comments welcome. > > >The other thing is that it appears to break amd behaviour. > > Does amd use mount_nfs(8)? I thought it did the mount syscalls > directly. I don't care to understand the bowels of amd, since I see enough of their product... 8-|. But it seems the behaviour changed between 4.3 and later, and it's been a problem (things like "cd" time out instead of waiting until they can get a good grip on the NFS server. Very frustrating, when your CVS tree or home directory lives on another machine. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message