TW

@awgcooper No, it does not work like that. But you can use `borg recreate` to rewrite all the archives that contain the unwanted file (or the directory). Just be very...

About "what do we win?" (see top post): I guess the only thing would be the "deduplication factor", computed as: ``` DF = total_deduplicated_size_uncompressed / total_undeduplicated_size_uncompressed ``` The first value...

The refcount field was removed from the ChunkIndexEntry namedtuple. compact now just uses a single bit (`F_USED`) to "know" which objects are used and which are not.

1. I don't think a hash over the chunker params is useful. These are only a few values and looking at them "as is" is simpler than at a hash...

https://github.com/borgbackup/borg/blob/1.1-maint/src/borg/helpers.py#L1240 comment about special character.

Due to @solrize asking about it on IRC, I have thought about such a "full file hash" (computed over the chunkids list) again. Guess, as it is now, the code...

Some improvements were done in #8468: It builds a ChunkIndex in the repository part of the check (for close to zero addtl. cost) and reuses it in the archives part...

About the SMART stats: - it has 16 reallocated sectors. so it has some issues. you should keep an eye on this: if the count stays stable, it could be...

About borg: - if you use a `ssh:` repo, the segment checksums (crc32) are computed server-side (on the machine running `borg serve`). - borg serve receives chunk data from the...

So, considering you have multiple error-free runs of memtest86+ (?) and the disk definitely has some issues, I'ld exchange the HDD. It does not show many runtime hours, but otoh...