Re: Corrupted output on errors

Thank you, Denis.  I can confirm that the newer version fixed the issue.

I have uploaded 2.7.2 to Debian's bullseye-backports and after review it
should be available to users of Debian stable.

Now that this is cleared up, I can see the errors:

Restoration of FSA for /bakfs/other-backups/dar/ada/var/log/sysstat aborted: Skipping backward is not possible on a pipe
Error while restoring data: Error while reading FSA from archive: Reached end of file before all data could be read
Final memory cleanup...
Error while restoring data: Error while reading FSA from archive: Reached end of file before all data could be read

It then exits with error 5.

This archive was generated by dar 2.6.13 on a Raspberry Pi running ext4 and unpacked
by 2.7.2 on x86_64 running ZFS.

The extraction command was:

dar --dirty-behavior no-warn --sequential-read -w -x - -R /bakfs/other-backups/dar/ada

And it was generated with:

Running dar -q -c - --aux /var/local/dar/1637242636 -A \
/var/local/dar/1637182897 -R /baksnap --empty-dir \
--retry-on-change 0 -P run -P tmp -P proc -P sys -P dev \
-P var/tmp -P var/cache/apt/archives -P media -P mnt \
-P cdrom -P var/cache/apt -P var/lib/mlocate -P var/lib/apt/lists \
-P var/log/journal -P var/spool/nncp -P var/local/dar \
-P var/cache/apt -P mythmount -P */no-backup -P home/*/.cache \
-P var/log/*log

There was no reference to var/log/sysstat at generation time, though I
did get a number of messages like this:

SECURITY WARNING! SUSPICIOUS FILE /baksnap/var/spool/anacron/cron.monthly: ctime changed since archive of reference was done, while no other inode information changed
SECURITY WARNING! SUSPICIOUS FILE /baksnap/var/spool/anacron/cron.weekly: ctime changed since archive of reference was done, while no other inode information changed

- John


On Tue, Nov 16 2021, Denis Corbin wrote:

> Hi,
>
> John, reading the Changelog for 2.6.15
>
> from 2.6.14 to 2.6.15
> - fixed error message formatting error leading message to contain
> garbage in place of system error information.
> [...]
>
> The problem you reported has already been fixed
>
> Cheers,
> Denis
>
> On 15/11/2021 19:25, Denis Corbin wrote:
>> On 15/11/2021 17:28, John Goerzen wrote:
>>> Hi,
>>
>> Hi,
>>
>>>
>>> I've noticed this for awhile; it seems the output gets all smooshed
>>> togehter when there are errors.  For instance:
>>>
>>> Restoration of FSA for /bakfs/other-backups/dar/sunlight/usr/local/etc aborted: Skipping backward is not possible on a pipe
>>> Error while restoring /bakfs/other-backups/dar/sunlight/usr/local/etc/mtree.excl : Cannot remove non-existent file from filesystem: /bakfs/other-backups/dar/sunlight/usr/local/etc/mtree.excl
>>> /bakfs/other-backups/dar/sunlight/usr/etcCould not restore original file ownership: No such file or directory
>>> Cannot restore permissions of /bakfs/other-backups/dar/sunlight/usr/etc : No such file or directory
>>> /bakfs/other-backups/dar/sunlight/localCould not restore original file ownership: No such file or directory
>>> Cannot restore permissions of /bakfs/other-backups/dar/sunlight/local : No such file or directory
>>> /bakfs/other-backups/dar/usrCould not restore original file ownership: No such file or directory
>>> Cannot restore permissions of /bakfs/other-backups/dar/usr : No such file or directory
>>> Error while restoring data: Error while reading FSA from archive: Reached end of file before all data could be read
>>> Final memory cleanup...
>>> Error while restoring data: Error while reading FSA from archive: Reached end of file before all data could be read
>>>
>>> There's no usr/etc/Could anywhere (no usr/etc either, for that matter)
>>> here.  There's also no /bakfs/other-backups/dar/usr (this is being
>>> extracted under /bakfs/other-backups/dar/sunlight).
>>
>> correct, I will see how to improve that,
>>
>>>
>>> dar 2.6.13 on Debian.
>>
>> OK
>>
>>>
>>> Thanks,
>>>
>>> John
>>>
>>
>>
>>