Merge pull request #729 from restic/add-faq

Add FAQ document
This commit is contained in:
Alexander Neumann 2017-01-19 11:42:38 +01:00
commit f0eeb16b33
2 changed files with 22 additions and 1 deletions

View file

@ -11,7 +11,8 @@ restic is a backup program that is fast, efficient and secure. Detailed
information can be found in [the documentation](doc/index.md) and [the user information can be found in [the documentation](doc/index.md) and [the user
manual](doc/Manual.md). The [design document](doc/Design.md) lists the manual](doc/Manual.md). The [design document](doc/Design.md) lists the
technical background and gives detailed information about the structure of the technical background and gives detailed information about the structure of the
repository and the data saved therein. repository and the data saved therein. The file [FAQ.md](doc/FAQ.md) lists the
most frequently asked questions.
The latest documentation can be viewed online at The latest documentation can be viewed online at
<https://restic.readthedocs.io/en/latest>. On the bottom left corner there is <https://restic.readthedocs.io/en/latest>. On the bottom left corner there is

20
doc/FAQ.md Normal file
View file

@ -0,0 +1,20 @@
FAQ
===
This is the list of Frequently Asked Questions for restic.
`restic check` reports packs that aren't referenced in any index, is my repository broken?
------------------------------------------------------------------------------------------
When `restic check` reports that there are pack files in the repository that are not referenced in any index, that's (in contrast to what restic reports at the moment) not a source for concern. The output looks like this:
$ restic check
Create exclusive lock for repository
Load indexes
Check all packs
pack 819a9a52e4f51230afa89aefbf90df37fb70996337ae57e6f7a822959206a85e: not referenced in any index
pack de299e69fb075354a3775b6b045d152387201f1cdc229c31d1caa34c3b340141: not referenced in any index
Check snapshots, trees and blobs
Fatal: repository contains errors
The message means that there is more data stored in the repo than strictly necessary. With high probability this is duplicate data. In order to clean it up, the command `restic prune` can be used. The source of this additional data is not yet known.