Re: [Dar-support] dar creating corrupted archives

[Paul N. <ma...@pa...>]

On Wed, 17 Dec 2025 17:42:54 +0100
Denis Corbin via Dar-support <dar...@li...> wrote:

> Le 17/12/2025 à 13:43, Paul Neuwirth via Dar-support a écrit :
> > On Tue, 16 Dec 2025 16:15:00 +0100
> > Denis Corbin via Dar-support <dar...@li...>
> > wrote:  
> [...]
> >>
> >> Can you try reading/testing the corrupted backup in sequential read
> >> mode (add --sequential-read option when testing the archive)?
> >>  
> > 
> > /backup # dar --sequential-read -t backup-roothomeFull
> > Final memory cleanup...
> > FATAL error, aborting operation: Error while reading in-place path
> > using tape
> > marks//.localbackup-snapshots/localbackup-20251215-100708 is an not
> > a valid path: Empty string as subdirectory does not make a valid
> > path  
> 
> OK, this is a known bug in 2.7.18 (you were using 2.7.12 here), the 
> archive can be read normally in sequential-read mode only, using dar 
> version >= 2.7.18.
> 
> This bug was triggered by the double slash in the path.
> 
OK thanks. I solved it by just normalizing paths before calling dar in
my backup scripts.
good to know it was due to a upstream bug, no need to dig in openSUSE
patches.
> With a fixed release, you can repair the archive/backup to also be
> able to read in direct access mode (if only using sequential read
> mode, no need to repair):
> 
> dar -y fixed_backup -A broken_backup [... other options if needed]
> 
> refer to documentation for the available options in repair mode.
> 
no need to repair, but good to know
> 
> for the dar side of the problem, no need to go further: this is a
> known bug fixed in release 2.7.18 (May 2025). You should upgrade your
> version to 2.7.19 or 2.8.2.
> 
the latest packaged version for openSUSE and also SUSE SLE is 2.7.16,
would need to create a new dar project to fix that/upgrade.
For now I know what the problem is/was and work around it.

Thank you so much
Paul