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 ? TIA. RN.
Remy Nonnenmacher <remy.nonnenmacher at activnetworks.com> writes:> 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 ?I can't reproduce it on RELENG_9...
On Thu, Feb 13, 2014 at 6:45 AM, Remy Nonnenmacher <remy.nonnenmacher at 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