Date: Fri, 12 Feb 2010 14:12:28 -0500 (EST) From: Rick Macklem <rmacklem@uoguelph.ca> To: Dmitry Marakasov <amdmi3@amdmi3.ru> Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org, John Baldwin <jhb@freebsd.org> Subject: Re: NFS write corruption on 8.0-RELEASE Message-ID: <Pine.GSO.4.63.1002121410100.24931@muncher.cs.uoguelph.ca> In-Reply-To: <20100212175422.GB94665@hades.panopticon> References: <20100210174338.GC39752@hades.panopticon> <201002111255.46256.jhb@freebsd.org> <Pine.GSO.4.63.1002121227480.9893@muncher.cs.uoguelph.ca> <20100212175422.GB94665@hades.panopticon>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 12 Feb 2010, Dmitry Marakasov wrote: > > I'm planning a massive testing for this weekend, including removing > soft mount option and trying linux client/server. > > Btw, I forgot to mention that I'm experiencing other NFS problems from > time to time, including "death" of a mount (that is, all processes that > try to access it freeze; this cures itself in some time with a message > "server is alive again"). Also I've seen another strange thing - not > only the mount dies but the network is flooded with NFS traffic. > Last time I've seen it quite a while ago, so I don't remember the > circumstances and direction of the traffic. > There are some patches at: http://people.freebsd.org/~rmacklem that may be relevant if you are using vanilla FreeBSD-8.0. (They're all now in stable/8, but are post-release of 8.0.) rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.1002121410100.24931>