From fbecae73628e84892babc97160bec86b094d2545 Mon Sep 17 00:00:00 2001 From: Alexander Neumann Date: Wed, 18 Jan 2017 21:48:39 +0100 Subject: [PATCH] Add FAQ document --- README.md | 3 ++- doc/FAQ.md | 20 ++++++++++++++++++++ 2 files changed, 22 insertions(+), 1 deletion(-) create mode 100644 doc/FAQ.md diff --git a/README.md b/README.md index a7d34897d..a837b442f 100644 --- a/README.md +++ b/README.md @@ -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 manual](doc/Manual.md). The [design document](doc/Design.md) lists 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 . On the bottom left corner there is diff --git a/doc/FAQ.md b/doc/FAQ.md new file mode 100644 index 000000000..c420d3c02 --- /dev/null +++ b/doc/FAQ.md @@ -0,0 +1,20 @@ +FAQ +=== + +This ist 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.