Date: Mon, 1 Jun 1998 11:55:45 -0500 (CDT) From: Kevin Day <toasty@home.dragondata.com> To: current@FreeBSD.ORG Subject: NFS discovery Message-ID: <199806011655.LAA13043@home.dragondata.com>
next in thread | raw e-mail | index | archive | help
Here's my setup: 2.2.6 NFS server with /home exported -current NFS client mounting server:/home under /home If the server gets rebooted or their link is temporarily severed, the client never recovers. Any attempt to read anything from /home causes the process to get wedged pretty nicely. (even kill -9 won't kill it) 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. Is there any way of making whatever it was that did this happen automatically every once in a while? :) Does specificing async on an nfs mount even do anything? Also.... Unrelated, but still with NFS... Some of my customers are complaining that their log files are getting other users's deleted files mixed in with theirs. (all of this is over nfs). Any idea how? 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?199806011655.LAA13043>