Re: [Bug-tar] Separate return code when file changes while being read

[Steve Bergman]

Hi,

Yes, I see that it only happens on truncation. (Or if the file just
decreases in size?)

One thing puzzles me.  Why has there not been a great outcry about this?
Nightly backups for the machines that I support report a failed backup
with no obvious cause at seemingly random intervals. (Well, I know what
it is now.)

Is everyone using cpio for backups?  The problem is that cpio has its
own problems.  If, during the backup, it comes across a file to be
backed up that is > 4GB in size, it immediately aborts with an error.
(Yes, in the year 2006 it does this!)  And there are no definite plans
to fix it, as a new header style would have to be added to the format.
One can use the "old c" style header and increase that limit to 8GB...
as long as they don't have more than 65536 files to backup.

Is this return 2 on file truncation issue something that is likely to be
changed anytime soon?  Or should I plan on patching my own copies?

Thanks,
Steve