Re: [Bug-tar] Strange behaviour using stdout and compressed tars

[Helmut Waitzmann]

Aviv Greenberg <address@hidden> writes:

[writing compressed tape archives to a file (m1 files) or to stdout (m2
files)]

>I examined the files in xxd, the compressed m2 files have trailing
>zeroes for some reason.
>
>The files are not corrupted tough, and they can be untarred with a
>"bzip2: (stdin): trailing garbage after EOF ignored"
>warning.

Look in the info: (tar)Blocking Factor
and search for "trailing garbage" or read this quotation:

     In previous versions of GNU `tar', the `--compress-block' option
     (or even older: `--block-compress') was necessary to reblock
     compressed archives.  It is now a dummy option just asking not to
     be used, and otherwise ignored.  If the output goes directly to a
     local disk, and not through stdout, then the last write is not
     extended to a full record size.  Otherwise, reblocking occurs.


>Is this the expected behaviour? If not, what can i do to help fix that?

What about using a small blocking factor?
-- 
Wenn Sie mir E-Mail schreiben, stellen |  When writing me e-mail, please
Sie bitte vor meine E-Mail-Adresse     |  precede my e-mail address with
meinen Vor- und Nachnamen, etwa so:    |  my full name, like
Helmut Waitzmann <address@hidden>, (Helmut Waitzmann) address@hidden