1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2024-12-24 08:45:13 +00:00

cross-reference the status oddity in the usage

This commit is contained in:
Antoine Beaupré 2015-11-23 19:48:33 -05:00
parent af7b17960e
commit 48bb4c326d
2 changed files with 3 additions and 1 deletions

View file

@ -165,6 +165,8 @@ Yes, if you want to detect accidental data damage (like bit rot), use the
If you want to be able to detect malicious tampering also, use a encrypted If you want to be able to detect malicious tampering also, use a encrypted
repo. It will then be able to check using CRCs and HMACs. repo. It will then be able to check using CRCs and HMACs.
.. _a_status_oddity:
I am seeing 'A' (added) status for a unchanged file!? I am seeing 'A' (added) status for a unchanged file!?
----------------------------------------------------- -----------------------------------------------------

View file

@ -444,7 +444,7 @@ A uppercase character represents the status of a regular file relative to the
is not used). Metadata is stored in any case and for 'A' and 'M' also new data is not used). Metadata is stored in any case and for 'A' and 'M' also new data
chunks are stored. For 'U' all data chunks refer to already existing chunks. chunks are stored. For 'U' all data chunks refer to already existing chunks.
- 'A' = regular file, added - 'A' = regular file, added (see also :ref:`a_status_oddity` in the FAQ)
- 'M' = regular file, modified - 'M' = regular file, modified
- 'U' = regular file, unchanged - 'U' = regular file, unchanged
- 'E' = regular file, an error happened while accessing/reading *this* file - 'E' = regular file, an error happened while accessing/reading *this* file