Date: Mon, 1 Jun 1998 13:29:24 -0500 (CDT) From: Kevin Day <toasty@home.dragondata.com> To: mi@video-collage.com (Mikhail Teterin) Cc: current@FreeBSD.ORG Subject: Re: NFS discovery Message-ID: <199806011829.NAA20244@home.dragondata.com> In-Reply-To: <199806011751.NAA29921@xxx.video-collage.com> from Mikhail Teterin at "Jun 1, 98 01:51:03 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> Kevin Day once stated: > > =However entering this on the client machine > = > =mount -u -o async /home > = > =*while* the client's nfs is hosed will make it recover within 5 > =seconds. It even appears that all the writes that were queued are > =executed, and no data is lost. > > That's a great thing to know. Those hungups are damn annoying. > The reason is, probably, a side effect of how `-u'/`async' are > implemented. AFAIK, the fs is unmounted and then remounted with > async. Which is just what you wanted. That's my thought too, but: umount /home will freeze, so it's not exactly unmounting things. :) > > =Is there any way of making whatever it was that did this happen > =automatically every once in a while? :) > > NFS hung ups are a strange topic, in my experience. People agree > that they are "bad", but one is not supposed to complain about > them... Don't read my post as a complaint, rather as a 'hey, why does it do this?" :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806011829.NAA20244>