From owner-freebsd-questions@freebsd.org Mon Jul 13 23:40:50 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 595C1995D33 for ; Mon, 13 Jul 2015 23:40:50 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DE1E49FC for ; Mon, 13 Jul 2015 23:40:49 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from moby.local ([37.6.29.167]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MOOdZ-1ZINps2GOL-005tko; Tue, 14 Jul 2015 01:40:41 +0200 Message-ID: <55A44C50.70500@gmx.com> Date: Tue, 14 Jul 2015 02:40:00 +0300 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Polytropon CC: "freebsd-questions@freebsd.org Questions" Subject: Re: tar: Damaged tar archive, Retrying... References: <55A3F7F2.3060400@gmx.com> <20150713225709.55553c98.freebsd@edvax.de> In-Reply-To: <20150713225709.55553c98.freebsd@edvax.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:5v8xpx2bOh0LZdN8uANizQw5+coFi0TK9Dj2451XUZ86LwTZzFY 8uf3LlDdWIpN9qn5hSWrVnsEUL6MfS6v96O1f0ckNhGCzqwJWNhFrI0/Rg1mzSekd/0h119 RwLofZFBwDE9+0XUqgGRMminidCYPN4Bvp2Jdi9UF3S5YHCk2IeIPcxVr9SOm5CHKJqaJ56 rbpQenmBQ0GZd95Jm9fnA== X-UI-Out-Filterresults: notjunk:1;V01:K0:ZezLR4mPc7A=:ca4g+THHoAEigGNRAcr571 JcBr49cVXHeQRZdddAQ+nb7OHq1lR2wslUb6jJhY4JKW0+86w1lEQknT21dQdrV/T3hNlgr47 odg08OeFmQvTNZOHqrdKU/qEGTYoGW6NwilQZ76qEIGVkMQkDomF6ZOXs1gqLGmyAR/eRWPxW 9CzjCXBb/dwA+ABlbpsvk/2ToLVmoDo5BcSTJZky4pf1f067Gq2PJUa5P+EJhr+iY2EaRfque uR+sXYLFMvS4DzkpajO7ABqQFe1QMnsHBiqmLlWcH890EGC47VHSvj0DD0KHJL8th2El5a2GH QNlZ29IcCZmDqTeDQzhCeCCDLDPbTCZ0kA6YdAW/Ep+hhwDGgo0JRqSulivfNFxd6jUodA2yw qLkV2CrwOOOicSCAcc/FtHrWL4fN2Bh7SXUghSp0l633CBfwSDMYI/bGPkdk960YvvUUDtFSQ gBTYERq5jo3GtLlRu03rO4tW3JmVsQ3AxtjpfykFq5i1Bii7nMgcAunRizuZXOu7/Hi7tRclv v0jLU6wfbWbDBd9FCMlA6XkL8m176xvytWLRck/opn6HffdeFJVc1aTx1i2DJBAbxVU6oPxqT ifWCIiuqulk44ucjezsru0IkKdVpn+fAZt7QQObNvvZ0SO3rnZGUz20X4mr2Hcrx5eSVwFJrl jPjQjZHymwG4s/wRiMH3xLsJwNGPkwq91ntn6HQji3+emd4GmOWZnkO0bMPpqSyudDmc= 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: Mon, 13 Jul 2015 23:40:50 -0000 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. This is definitely something that should be further investigated:) > Furthermore: Are you using compression? If yes: Is it using > the same compression libraries on both sides? (Just a guess, > it should not have to matter...) > > > No, I am not using compression. Just tar. I am very curious regarding this.