TW
duplicate of #6687? if you could run a full borg check (including the archives check), we could see if there is any serious issue.
@DSpammy if you simplify your reproducer script by removing `--cleanup-commits` from the `borg compact` invocation, does it still reproduce the issue?
@DSpammy can you use the code from #6918 and run `borg compact` with `--debug`?
You can either take the repository.py file and copy it over the original one or apply the patch.
Hmm, yeah, there were changes in other parts of the code also, so just applying the patch would work, but taking the whole repository.py does not.
Patch: ``` commit e5b6670bc662882d3961808a0ed6c3d0af574ba6 (origin/compaction-debugging-1.2, compaction-debugging-1.2) Author: Thomas Waldmann Date: Sun Jul 31 19:01:09 2022 +0200 repository: add debug logging for issue #6687 i suspect that compact_segments wrongly drops some...
it dropped 1st DEL for `e92b` from segment 49494 because 48506 was not in the shadow_index, see `si [49862]`. it dropped 2nd DEL for `e92b` from segment 50870 because shadow_index...
Did it complain about orphans (in the archives checking part) as I suspected above?
Entire archive yes, but only the metadata stream, not the files' content data, you can use: ``` borg extract repo::archive what/i/want ``` borg mount + rsync only may help if...
Some notes: - borg does not explicitly archive directory contents (like having a directory item that includes all fs object names in that directory), this information is only implicitly stored...