From owner-freebsd-questions Sun Jan 5 7:10:27 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56F1237B401 for ; Sun, 5 Jan 2003 07:10:25 -0800 (PST) Received: from smtp808.mail.sc5.yahoo.com (smtp808.mail.sc5.yahoo.com [66.163.168.187]) by mx1.FreeBSD.org (Postfix) with SMTP id A034243EB2 for ; Sun, 5 Jan 2003 07:10:24 -0800 (PST) (envelope-from fscked@pacbell.net) Received: from adsl-66-124-232-253.dsl.snfc21.pacbell.net (HELO pacbell.net) (fscked@pacbell.net@66.124.232.253 with plain) by smtp-sbc-v1.mail.vip.sc5.yahoo.com with SMTP; 5 Jan 2003 15:10:24 -0000 Message-ID: <3E184AED.B5A37863@pacbell.net> Date: Sun, 05 Jan 2003 07:10:37 -0800 From: richard childers / kg6hac X-Mailer: Mozilla 4.79 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: lewiz Cc: freebsd-mobile@freebsd.org, FreeBSD-questions Subject: Re: Working around problems when an NFS server dies / is unavailable. References: <20030105001254.GA48290@lewiz.org> <3E1781E0.20D76CB8@pacbell.net> <20030105113403.GE48290@lewiz.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Make sure no one (including you) is using (including your shell's current working directory) the directory which is acting as a mount point, when you umount(8). Otherwise, you'll get a message about the filesystem being in use ... (-: -- richard lewiz wrote: > On Sat, Jan 04, 2003 at 04:52:48PM -0800, richard childers / kg6hac wrote: > > I seem to recall a 'nomount' option in fstab(5), the manual page that > > describes the contents of the /etc/fstab ('filesystem table') file. > > > > That plus amd(8) should, in theory, get you a relatively stateless NFS > > connection. > > I must admit, I've never worked with amd but it may be worth a try -- it > can't be any worse than the situation I'm in at the moment. Thanks for > bringing it to my attention ;) > > > I've had some success using 'umount -f' to forcibly umount NFS filesystems, > > from the client side, in the past. > > This surprised me. I had assumed a forced umount would actually force > the umount, yet, it seems not to have done. I am confuzed as to what is > and what isn't a bug (often I'm screwing things up myself, I'm sure). > Do you think this would count as a bug? If other people have had > problems too, it almost suggests it might be. > > > However, NFS, while stateless in intent, is really not a good > > infrastructural element for a plug-and-play network. Plugging in is easy; > > unplugging may require an explicit shutdown to properly deallocate > > resources. > > Yeah, I'm starting to learn this now. I don't really know what else to > use. I've heard of CODA and even AFS but I don't know their suitability > to my purpose. I think I might do a bit more research then ask again on > this list. > > Thanks for your information, I'll go read about amd ;) > > -lewiz. > > -- > All true wisdom is found on T-shirts. > ------------------------------------------------------------------------ > --|| url: http://lewiz.info/ | http://www.westwood.karoo.net/pgpkey ||-- > > ----------------------------------------------------------------- > Part 1.2Type: application/pgp-signature To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message