From owner-freebsd-questions@freebsd.org Tue Jul 14 00:10:05 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30F949995DF for ; Tue, 14 Jul 2015 00:10:05 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EA5E111EA for ; Tue, 14 Jul 2015 00:10:03 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-74-114.dynamic.qsc.de [92.195.74.114]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 8FD7A3CD88; Tue, 14 Jul 2015 02:10:00 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id t6E09x8p002976; Tue, 14 Jul 2015 02:10:00 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Tue, 14 Jul 2015 02:09:59 +0200 From: Polytropon To: Nikos Vassiliadis Cc: "freebsd-questions@freebsd.org Questions" Subject: Re: tar: Damaged tar archive, Retrying... Message-Id: <20150714020959.bf3d8121.freebsd@edvax.de> In-Reply-To: <55A44C50.70500@gmx.com> References: <55A3F7F2.3060400@gmx.com> <20150713225709.55553c98.freebsd@edvax.de> <55A44C50.70500@gmx.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2015 00:10:05 -0000 On Tue, 14 Jul 2015 02:40:00 +0300, Nikos Vassiliadis wrote: > > > On 07/13/15 23:57, Polytropon wrote: > > On Mon, 13 Jul 2015 20:40:02 +0300, Nikos Vassiliadis wrote: > >> Hi, > >> > >> I am currently using tar to copy some very files to another host and > >> got this: > >>> tar: Damaged tar archive > >>> tar: Retrying... > >>> tar: Damaged tar archive > >>> tar: Retrying... > >>> tar: Damaged tar archive > >>> tar: Retrying... > >>> tar: Damaged tar archive > >>> tar: Retrying... > >>> tar: Damaged tar archive > >> > >> The copy is done using tar|nc and nc|tar on the receiving host. > >> This looks like a bug and I wonder whether the copy is OK. > > > > Create a checksum list on the source and the target machine, > > them compare both. This should give you a good overview of > > the files to be identical. > > For sure a checksum will do that. I am lucky that the system has an > SSD, those files are huge. Results: > Two out of three files are OK. One was removed, maybe the one > that printed out the warnings. While md5 doesn't provide you an exact 1:1 comparison of files, it's good to spot irregularities, as you could see. So there really is something different on the target side. > This is definitely something that should be further investigated:) If you grep through the sources, you'll find that the error message originates from libarchive, not tar itself (directly). Involved files: /usr/src/lib/libarchive/archive_read_support_format_tar.c /usr/src/usr.bin/tar/read.c Is there a significant version mismatch between source and target system? It shouldn't affect readability of tar archives (simply because tar is _the_ universal archiving format across operating systems), but maybe you can check that. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...