TW
`M` means that borg thinks the file is modified. This slows it down significantly as it will read and chunk the file again. `d` is just for directory, nothing special...
it will be one time slow and then much faster again.
Hmm, changing all the absolute paths will create cache misses. But once it was read/chunked/hashed at the new position, it will have a new files cache entry with the new...
For `--debug-topic=files_cache` you need a newer borg than 1.1.15.
The ubuntu borgbackup maintainer's ppa has borg 1.2.x or you could use the binary from github releases page.
@djxpace does it work quicker now?
no response, so guess it was solved.
If you use --prefix for prune, you can just rename an archive to a non-matching name, so it won't prune it.
Yes, currently one has to be sure about having a "valid" (untampered) repo state before writing to it with append-mode=0. borg list repo, borg list archive, borg extract --dry-run archive...
I reviewed the code where `repository.delete(id)` is used: - by `borg delete archive` in `Archive.delete()` (via `chunk_decref()`) - by `borg debug delete-obj` - by `borg check --repair` - with `--verify-data`...