Date: Fri, 12 Feb 2010 14:09:14 -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.1002121406010.24931@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: >> >> 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? > Oh, I realized the first 4 bytes of the garbage is the record mark that preceeds the RPC header for TCP, so the garbage is the first part of the RPC after the TCP/IP header. > > Can you reproduce this using a non-FreeBSD server with a FreeBSD client or a > non-FreeBSD client with a FreeBSD server? That would narrow down the breakage > to either the client or the server. > If using a non-FreeBSD client/server isn't convenient, another way would be to do a binary packet capture (something like "tcpdump -s 0 -w <file> <host>") and then looking at it in wireshark for a failed case and see if the data is corrupted on the wire. rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.1002121406010.24931>