Date: Fri, 12 Feb 2010 12:37:47 -0500 (EST) From: Rick Macklem <rmacklem@uoguelph.ca> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-hackers@freebsd.org, Dmitry Marakasov <amdmi3@amdmi3.ru>, freebsd-stable@freebsd.org Subject: Re: NFS write corruption on 8.0-RELEASE Message-ID: <Pine.GSO.4.63.1002121227480.9893@muncher.cs.uoguelph.ca> In-Reply-To: <201002111255.46256.jhb@freebsd.org> References: <20100210174338.GC39752@hades.panopticon> <201002111255.46256.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 11 Feb 2010, John Baldwin wrote: [good stuff snipped] >> >> Case1: single currupted block 3779CF88-3779FFFF (12408 bytes). >> Data in block is shifted 68 bytes up, loosing first 68 bytes are >> filling last 68 bytes with garbage. Interestingly, among that garbage >> is my hostname. > > Is it the hostname of the server or the client? > My guess is that hades.panopticon (or something like that:-) is the client. The garbage is 4 bytes (80 00 80 84) followed by the first part of the RPC header. (Bytes 5-8 vary because they are the xid and then the host name is part of the AUTH_SYS authenticator.) For Case2 and Case3, you see less of it, but it's the same stuff. Why? I have no idea, although it smells like some sort of corruption of the mbuf list. (It would be nice if you could switch to a different net interface/driver. Just a thought, since others don't seem to be seeing this?) As John said, it would be nice to try and narrow it down to client or server side, too. Don't know if this helps or is just noise, rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.1002121227480.9893>