TW
Yeah, that would be good. Notable: - when writing to a block device, one likely would use `borg extract --stdout ... > /dev/blkxxx` to directly extract to the block device...
If A is archived data stream and F is the fs data stream: - iterate over A chunks list to get chunkid_A, size - read size bytes from F, compute...
Thanks for the detailed bug report.
BTW, do you use `borg break-lock` or `--bypass-lock` option in your automated scripts?
``` % borg debug get-obj --help usage: borg debug get-obj REPOSITORY ID PATH ``` thus, for the first repo: ``` borg debug get-obj /Backups/borg/home.borg \ 8a158ba7fdfae9b1373063a5bb5ea8ea6698c93ed7feff89ca6ff0a3c8842ebd \ 8a158ba7fdfae9b1373063a5bb5ea8ea6698c93ed7feff89ca6ff0a3c8842ebd.chunk ``` But...
The directory listings did not reveal anything special. But considering the described circumstances this looks like a bug.
In case we do not find the issue otherwise, maybe keep an unmodified copy of at least one of the repos until this is resolved.
OK, so the 1 missing index entry was an orphan chunk. That takes quite a bit of severity off from this ticket. :-) It can't be found in the index...
What could be done to determine the contents of the orphan chunk is to seek to the given offset into the given segment file and look what's there.
If a small not-used-anymore (== "deleted") chunk sits in a segment file with other still-used chunks, it might well stay there. borg computes a ratio deleted/total size and if the...