mirror of
https://github.com/borgbackup/borg.git
synced 2025-02-28 00:36:33 +00:00
clarify documentation on the A status oddity
This commit is contained in:
parent
a75d77226b
commit
af7b17960e
1 changed files with 7 additions and 3 deletions
10
docs/faq.rst
10
docs/faq.rst
|
@ -168,9 +168,9 @@ repo. It will then be able to check using CRCs and HMACs.
|
||||||
I am seeing 'A' (added) status for a unchanged file!?
|
I am seeing 'A' (added) status for a unchanged file!?
|
||||||
-----------------------------------------------------
|
-----------------------------------------------------
|
||||||
|
|
||||||
The files cache (which is used to determine whether |project_name| already
|
The files cache is used to determine whether |project_name| already
|
||||||
"knows" / has backed up a file and if so, to skip the file from chunking)
|
"knows" / has backed up a file and if so, to skip the file from
|
||||||
does intentionally *not* contain files that:
|
chunking. It does intentionally *not* contain files that:
|
||||||
|
|
||||||
- have >= 10 as "entry age" (|project_name| has not seen this file for a while)
|
- have >= 10 as "entry age" (|project_name| has not seen this file for a while)
|
||||||
- have a modification time (mtime) same as the newest mtime in the created
|
- have a modification time (mtime) same as the newest mtime in the created
|
||||||
|
@ -191,6 +191,10 @@ will often be the same and already stored in the repo (except in the above
|
||||||
mentioned rare condition), it will just re-use them as usual and not store new
|
mentioned rare condition), it will just re-use them as usual and not store new
|
||||||
data chunks.
|
data chunks.
|
||||||
|
|
||||||
|
Since only the files cache is used in the display of files status,
|
||||||
|
those files are reported as being added when, really, chunks are
|
||||||
|
already used.
|
||||||
|
|
||||||
Why was Borg forked from Attic?
|
Why was Borg forked from Attic?
|
||||||
-------------------------------
|
-------------------------------
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue