Date: Mon, 10 Oct 2011 16:27:59 -0400 From: John Baldwin <jhb@freebsd.org> To: Larry Rosenman <ler@lerctr.org> Cc: freebsd-stable@freebsd.org Subject: Re: rsync corrupted MAC Message-ID: <201110101627.59173.jhb@freebsd.org> In-Reply-To: <4E933BBF.6070209@lerctr.org> References: <alpine.BSF.2.00.1110091604450.94525@lrosenman.dyndns.org> <201110101147.30558.jhb@freebsd.org> <4E933BBF.6070209@lerctr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, October 10, 2011 2:38:55 pm Larry Rosenman wrote: > On 10/10/2011 10:47 AM, John Baldwin wrote: > > On Sunday, October 09, 2011 5:06:26 pm Larry Rosenman wrote: > >> Any ideas on which side or what might be broke here? > >> > >> ler/MAIL-ARCHIVE/2008/12/INBOX > >> Corrupted MAC on input. > >> Disconnecting: Packet corrupt > >> rsync: connection unexpectedly closed (33845045 bytes received so far) > > [receiver] > >> rsync error: error in rsync protocol data stream (code 12) at io.c(605) > > [receiver=3.0.9] > >> rsync: connection unexpectedly closed (1450 bytes received so far) > > [generator] > >> rsync error: unexplained error (code 255) at io.c(605) [generator=3.0.9] > > I've had somewhat similar issues (ssh getting corruption in its data stream) > > when a NIC in my netbook was corrupting packet data when it ran at 1G (it > > worked fine at 10/100). Pyun eventually fixed the issue by applying enough > > workarounds (it was likely a hardware bug in the NIC's chipset). However, it > > wasn't easy to debug unfortunately. :( > > > Any ideas on where to start? > > from the 8.2 box (tbh.lerctr.org in the script): > > 8.2->PIX->Provider->Internet->Motorola SBG6580 (Time-Warner)->Trendnet > TEG-160WS Gig switch->9.0 box (borg.lerctr.org). > > So, where do I start? In my case I was seeing other issues with the NIC (it would periodically "freeze" spewing a constant stream of pause frames onto the LAN and refusing to receive more frames), so I already suspected it of being an issue. When I turned off flow control so it wouldn't freeze, it started corrupting the packets instead. Without that kind of smoking gun I would probably have had a hard time figuring out the issue. I would try switching various parts out to see if you can narrow the issue down to a single component. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201110101627.59173.jhb>