In message <b0459d5c050918200370e7f7b5@mail.gmail.com>, matthew sporleder write
s:
>I don't think this is new behavior.  I've known about it for at least
>two-three years, anyway.

The new behavior isn't that gzip has problems on large files.  It's that, now,
it indicates an error status so that Amanda trashes the backup.

So, maybe 6 months ago, the resulting file was valid and usable, but "gzip -t"
would indicate an error because the size reported was wrong.  But it worked.

Now, gzip exits with error status 1, so amanda gives up.

-s