Date: Tue, 5 Jan 1999 17:24:52 -0500 (EST) From: Alfred Perlstein <bright@hotjobs.com> To: Robert Withrow <bwithrow@BayNetworks.COM> Cc: hackers@FreeBSD.ORG, witr@rwwa.com Subject: Re: 3.0-REL NFS interop problems redux Message-ID: <Pine.BSF.4.05.9901051714390.37756-100000@bright.fx.genx.net> In-Reply-To: <199901052143.VAA15097@tuva.engeast.baynetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 5 Jan 1999, Robert Withrow wrote: > I whined before about my problem where a specific NFS mount goes > deaf on me for a period of time and then wakes up later. I said > that I would sniff out the problem... Well I finally got my office > set up so that I could get a sniffer to capture the session and I have > that capture (about 600 packets). I've looked at it and I can see > where it goes wrong, but I can't see *why* it is wrong. I'm wondering > if there is an NFS hacker who can work with me on this. as a workaround, have you tried: a) tcp mounts b) nfs 3 c) cvsup'ing to a new -current (there was some problems with signals being delivered during NFS activity in -release) at work, i'm a NFS client to a solaris box and 'a' and 'b' seems to have solved my hanging problems, i used to have a NFS hang for several minutes occasionally, going tcp helped that. (however i'm not using AMD) you also may want to look into the bugfixes that were done post-release i know those aren't _solutions_ but they may be able to help Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9901051714390.37756-100000>