KurlesHS/restic
1
0
Fork 0
forked from TrueCloudLab/restic
Code Pull requests Activity

doc: suggest to follow troubleshooting steps if check reports error

Browse source
This commit is contained in:
Michael Eischer 2024-06-30 11:45:29 +02:00
parent fdc7349aa4
commit 283038056e
2 changed files with 17 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
doc/045_working_with_repos.rst
View file

@ -368,10 +368,22 @@ detect this and yield the same error as when you tried to restore:
$ restic -r /srv/restic-repo check $ restic -r /srv/restic-repo check
... ...
load indexes load indexes
error: error loading index de30f323: load <index/de30f3231c>: invalid data returned error: error loading index de30f3231ca2e6a59af4aa84216dfe2ef7339c549dc11b09b84000997b139628: LoadRaw(<index/de30f3231c>): invalid data returned
Fatal: LoadIndex returned errors
If the repository structure is intact, restic will show that no errors were found: The repository index is damaged and must be repaired. You must run `restic repair index' to correct this.
Fatal: repository contains errors
.. warning::
If ``check`` reports an error in the repository, then you must repair the repository.
As long as a repository is damaged, restoring some files or directories will fail. New
snapshots are not guaranteed to be restorable either.
For instructions how to repair a damaged repository, see the :ref:`troubleshooting`
section or follow the instructions provided by the ``check`` command.
If the repository structure is intact, restic will show that ``no errors were found``:
.. code-block:: console .. code-block:: console

2
doc/077_troubleshooting.rst
View file

@ -10,6 +10,8 @@
^ for subsubsections ^ for subsubsections
" for paragraphs " for paragraphs
.. _troubleshooting:
######################### #########################
Troubleshooting Troubleshooting
######################### #########################