From owner-freebsd-stable Tue Apr 21 06:34:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07716 for freebsd-stable-outgoing; Tue, 21 Apr 1998 06:34:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ren.dtir.qld.gov.au (firewall-user@ns.dtir.qld.gov.au [203.108.138.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07701 for ; Tue, 21 Apr 1998 13:34:43 GMT (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id XAA21321; Tue, 21 Apr 1998 23:34:14 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma021310; Tue, 21 Apr 98 23:33:49 +1000 Received: from troll.dtir.qld.gov.au (troll.dtir.qld.gov.au [167.123.8.1]) by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with ESMTP id XAA12669; Tue, 21 Apr 1998 23:33:48 +1000 (EST) Received: from localhost (syssgm@localhost) by troll.dtir.qld.gov.au (8.8.5/8.8.5) with SMTP id XAA12764; Tue, 21 Apr 1998 23:33:45 +1000 (EST) Message-Id: <199804211333.XAA12764@troll.dtir.qld.gov.au> X-Authentication-Warning: troll.dtir.qld.gov.au: syssgm@localhost didn't use HELO protocol To: Mattias Pantzare cc: freebsd-stable@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: make buildworld over NFS References: <199804211257.OAA28387@zed.ludd.luth.se> In-Reply-To: <199804211257.OAA28387@zed.ludd.luth.se> from Mattias Pantzare at "Tue, 21 Apr 1998 14:57:51 +0200" Date: Tue, 21 Apr 1998 23:33:44 +1000 From: Stephen McKay Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Tuesday, 21st April 1998, Mattias Pantzare wrote: >> BTW, I use hard mounts, not soft. It's a bad idea to use soft except with >> read-only mounts. > >Why? Nobody explains it much: To quote from the Solaris mount_nfs page "File systems that are mounted read-write or that contain executable files should always be mounted with the hard option. Applications using soft mounted file systems may incur unexpected I/O errors." And Digital Unix offers: "File systems that are mounted rw (read-write) should use the hard option", which is just ripped off from SunOS. But it's really quite simple: soft mounts are allowed to return errors after a certain number of timeouts. So your programs will fail when the server goes down or temporarily is hard to reach. Hard mounts must retry until doomsday. So, in theory, the writes will complete when the server comes back up, even if it is next year. Same deal for executables running off NFS. Hard mounts should just block the process until the server comes back. Soft mounts will let them die if they need some new text pages and the server is unavailable. Also, nfsiod is doing write-behind for you, so you probably could lose writes without your programs even noticing if the server drops out then returns. I just made the mistake of trying to verify this by reading the code. Oh, my head! Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message