Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Feb 2014 18:40:33 -0500
From:      Eitan Adler <lists@eitanadler.com>
To:        Remy Nonnenmacher <remy.nonnenmacher@activnetworks.com>
Cc:        freebsd-stable List <freebsd-stable@freebsd.org>
Subject:   Re: Damaged tar files
Message-ID:  <CAF6rxgkMBZ0gSAOTKTZu6k8BBh1%2Bj3%2BdSAdGAX-DLW3a6AF8jg@mail.gmail.com>
In-Reply-To: <52FCB056.6030007@activnetworks.com>
References:  <52FCB056.6030007@activnetworks.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 13, 2014 at 6:45 AM, Remy Nonnenmacher
<remy.nonnenmacher@activnetworks.com> wrote:
> Hi there,
>
> While moving big files using tar c | tar x, I found that every time, at 30GB
> sent, the receiving tar outputs a "tar: Damaged tar archive". I also checked
> that a Linux machine also sees a broken stream.
>
> It seems that in stable -10 and stable -9, tar creation is broken
> (libarchive update ?).
>
> Have someone seen this before I fill a PR ?


Is this true for all large files or just some?  Does it stop at a
deterministic point in each file?  If multiple files are affected does
it stop at the same byte count for each file, or does it stop around
the same point?

-- 
Eitan Adler



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgkMBZ0gSAOTKTZu6k8BBh1%2Bj3%2BdSAdGAX-DLW3a6AF8jg>