octoleo/restic
2
2
Fork 0
mirror of https://github.com/octoleo/restic.git synced 2024-06-26 12:32:36 +00:00
Code Issues Releases Wiki Activity

Merge pull request #3626 from fkusche/issue-3620-doc-unreferenced-packs

Browse Source 
Update documentation regarding unreferenced packs
This commit is contained in:
MichaelEischer 2022-01-22 15:15:25 +01:00 committed by GitHub
commit f0a8182493
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
doc/faq.rst
View File

@ -40,18 +40,21 @@ looks like this:
::
$ restic check
Create exclusive lock for repository
Load indexes
Check all packs
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
2 additional files were found in the repo, which likely contain duplicate data.
You can run `restic prune` to correct this.
check snapshots, trees and blobs
[0:00] 100.00% 16 / 16 snapshots
no errors were found
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
cause of this bug is not yet known.
strictly necessary. This is uncritical. With high probability this is duplicate data
caused by an interrupted backup run or upload operation. In
order to clean it up, the command ``restic prune`` can be used.
I ran a ``restic`` command but it is not working as intended, what do I do now?
-------------------------------------------------------------------------------
@ -224,4 +227,4 @@ Restic backup command fails to find a valid file in Windows
-----------------------------------------------------------
If the name of a file in Windows contains an invalid character, Restic will not be
able to read the file. To solve this issue, consider renaming the particular file.
able to read the file. To solve this issue, consider renaming the particular file.