Date: Fri, 12 Feb 2010 20:54:22 +0300 From: Dmitry Marakasov <amdmi3@amdmi3.ru> To: Rick Macklem <rmacklem@uoguelph.ca> 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: <20100212175422.GB94665@hades.panopticon> In-Reply-To: <Pine.GSO.4.63.1002121227480.9893@muncher.cs.uoguelph.ca> References: <20100210174338.GC39752@hades.panopticon> <201002111255.46256.jhb@freebsd.org> <Pine.GSO.4.63.1002121227480.9893@muncher.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
* Rick Macklem (rmacklem@uoguelph.ca) wrote: > > Is it the hostname of the server or the client? > > My guess is that hades.panopticon (or something like that:-) is the Yes, that is the client. > As John said, it would be nice to try and narrow it down to client or > server side, too. 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. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100212175422.GB94665>