The reported exit status is shifted left by 8 bits, so that means tar exited with status 2, which means failure.
You should look at the XferLOG to see what error(s) it reported. It could be something benign, but you should be sure before you start disabling error checking. Craig On Sat, Nov 28, 2020 at 8:59 AM Paul Leyland <paul.leyl...@gmail.com> wrote: > This is a golden oldie. At least a decade after > https://sourceforge.net/p/backuppc/mailman/backuppc-users/thread/AANLkTi%3DuzdiYV1jCzofkfeEQ6-czx34uEmYx2159Uxa%2B%40mail.gmail.com/#msg26616969 > appeared, Ubuntu still ships with a backuppc which reports > > backup failed (Tar exited with error 512 () status) > for the localhost target, even though the backup is, AFAICT, adequate in > every significant respect. > > Should the source be changed to mask off only the bottom 8 bits? > > For the time being I will add the option "--ignore-failed-read" to > TarClientCmd for localhost. Cosmetic, true, because the backup is fully > functional but still... > _______________________________________________ > BackupPC-users mailing list > BackupPC-users@lists.sourceforge.net > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: https://github.com/backuppc/backuppc/wiki > Project: https://backuppc.github.io/backuppc/ >
_______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
