diff options
| author | Thomas Waldmann <tw@waldmann-edv.de> | 2023-11-01 17:40:47 +0100 |
|---|---|---|
| committer | Thomas Waldmann <tw@waldmann-edv.de> | 2023-11-01 18:04:24 +0100 |
| commit | 6b928dac93a7a198811a939d1c1d7e6274dbc291 (patch) | |
| tree | 9d415eb6eca833ef36d675fbb8d92fe90ff96900 | |
| parent | da4fcc5a66798da68e2e9db280e4b3629de34c53 (diff) | |
docs: not only attack/unsafe, can also be a fs issue, fixes #7853
| -rw-r--r-- | docs/faq.rst | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/faq.rst b/docs/faq.rst index 550b7f2e7..f782629f8 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -113,6 +113,9 @@ run into this by yourself by restoring an older copy of your repository. "attack": maybe an attacker has replaced your repo by an older copy, trying to trick you into AES counter reuse, trying to break your repo encryption. +Borg users have also reported that fs issues (like hw issues / I/O errors causing +the fs to become read-only) can cause this warning, see :issue:`7853`. + If you'ld decide to ignore this and accept unsafe operation for this repository, you could delete the manifest-timestamp and the local cache: |