From owner-freebsd-questions@FreeBSD.ORG Fri Aug 22 19:51:18 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6287D16A4BF for ; Fri, 22 Aug 2003 19:51:18 -0700 (PDT) Received: from kyoto.meibin.net (kyoto.meibin.net [219.166.101.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFC9143F85 for ; Fri, 22 Aug 2003 19:51:16 -0700 (PDT) (envelope-from lukek@meibin.net) Received: (qmail 56814 invoked by uid 89); 23 Aug 2003 02:49:49 -0000 Received: from unknown (HELO yujo) (192.168.10.8) by kyoto.meibin.net with SMTP; 23 Aug 2003 02:49:49 -0000 Message-ID: <005e01c36920$bafeda40$080aa8c0@yujo> From: "lukek" To: "FreeBSD-questions" Date: Sat, 23 Aug 2003 11:43:18 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Wierd problems with rsync X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Aug 2003 02:51:18 -0000 Hi, I have managed to generate some weird errors over the last few years playing with *nix type systems but this one takes the cake. Whilst rsync'ing a directory I got the following error twice in a row Disconnecting: Corrupted MAC on input. rsync: connection unexpectedly closed (426487689 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) rsync: connection unexpectedly closed (182042 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) Does anyone have any ideas ? -bash-2.05b$ uname -r 4.8-RELEASE -bash-2.05b$ rsync -v rsync version 2.5.6 protocol version 26 Any pointers are really appreciated, This machine is a file server that has sucessfully crashed four times in the last week with hardware issues and just when I thought I had that beat I get this lot. Regards, LukeK