2023-10-22 18:24:02 +00:00
|
|
|
Bugfix: Update zstd library to fix possible data corruption at max. compression
|
|
|
|
|
|
2023-10-23 18:45:15 +00:00
|
|
|
In restic 0.16.0, backups where the compression level was set to `max` (using
|
|
|
|
|
`--compression max`) could in rare and very specific circumstances result in
|
|
|
|
|
data corruption due to a bug in the library used for compressing data.
|
2023-10-22 18:24:02 +00:00
|
|
|
|
|
|
|
|
Restic now uses the latest version of the library used to compress data, which
|
2023-10-23 18:45:15 +00:00
|
|
|
includes a fix for this issue. Please note that the `auto` compression level
|
|
|
|
|
(which restic uses by default) was never affected, and even if you used `max`
|
|
|
|
|
compression, chances of being affected by this issue were very small.
|
|
|
|
|
|
|
|
|
|
To check a repository for any corruption, run `restic check --read-data`. This
|
|
|
|
|
will download and verify the whole repository and can be used at any time to
|
|
|
|
|
completely verify the integrity of a repository. If the `check` command detects
|
|
|
|
|
anomalies, follow the suggested steps.
|
|
|
|
|
|
|
|
|
|
To simplify any needed repository repair and minimize data loss, there is also
|
|
|
|
|
a new and experimental `repair packs` command that salvages all valid data from
|
|
|
|
|
the affected pack files (see `restic help repair packs` for more information).
|
2023-10-22 18:24:02 +00:00
|
|
|
|
|
|
|
|
https://github.com/restic/restic/issues/4523
|
|
|
|
|
https://github.com/restic/restic/pull/4530
|
