Date: Tue, 17 Oct 95 13:41 PDT From: pete@puffin.pelican.com (Pete Carah) To: questions@freebsd.org Subject: Re: Problems with 'df' not doing anything Message-ID: <m0t5Ip9-0000ReC@puffin.pelican.com> In-Reply-To: <199510171741.KAA27855@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <199510171741.KAA27855@phaeton.artisoft.com> Terry writes: ..... >You have a hard nfs mount where the server has gone away. >Change it to a soft mount, or use explicit FS names excluding the dead one. That last (explicit FS names) does little good in IRIX 4.x; you still get the timeouts even for fs's not mentioned in the args (at least we do all soft,bg mounts at that place; there are lots of nfs mounts and normally at least one is down any given time :-) (actually soft mounts are a bit dangerous in irix since they default to async, but normally it doesn't seem to hurt us.) Don't know about other sysv variants; most of SGI's network code is pretty direct from BSD anyhow and not sysv. I'd hope it helps FreeBSD correctly. Soft mounts are still annoying for 'df'; our timeout is set pretty long. Something that bothers me in freebsd is that you can't force-unmount a dead hard mount; we should have some provision for that since it leads to unnecessary dirty reboots. SGI did that one 'right' (it does wait an inordinate amount of time, like 3-5 minutes per mount, but at least it unmounts even with a dead server). I think umount -f is supposed to do this but it doesn't work, at least in 1.1.5 (which is all I've tried it in). -- Pete
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0t5Ip9-0000ReC>