mirror/borg
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2024-12-23 08:16:54 +00:00
Code Issues Releases Wiki Activity

Fixed more in usage.rst. - → –; – → -- (CLI); Bullet list.

Browse source
This commit is contained in:
Robin Schneider 2016-01-17 22:23:54 +01:00
parent 1f1ff61375
commit 89ce86a33b
No known key found for this signature in database
GPG key ID: 489A4D5EC353C98A
1 changed files with 6 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
docs/usage.rst
View file

@ -463,11 +463,11 @@ or not). For each item, it prefixes a single-letter flag that indicates type
and/or status of the item. and/or status of the item.
If you are interested only in a subset of that output, you can give e.g. If you are interested only in a subset of that output, you can give e.g.
`--filter=AME` and it will only show regular files with A, M or E status (see ``--filter=AME`` and it will only show regular files with A, M or E status (see
below). below).
A uppercase character represents the status of a regular file relative to the A uppercase character represents the status of a regular file relative to the
"files" cache (not relative to the repo - this is an issue if the files cache "files" cache (not relative to the repo -- this is an issue if the files cache
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.
@ -519,6 +519,7 @@ In the worst case (all files are big and were touched in between backups), this
will store all content into the repository again. will store all content into the repository again.
Usually, it is not that bad though: Usually, it is not that bad though:
- usually most files are not touched, so it will just re-use the old chunks - usually most files are not touched, so it will just re-use the old chunks
it already has in the repo it already has in the repo
- files smaller than the (both old and new) minimum chunksize result in only - files smaller than the (both old and new) minimum chunksize result in only
@ -556,7 +557,7 @@ You need to be careful with what you give as filename when using ``--read-specia
e.g. if you give ``/dev/zero``, your backup will never terminate. e.g. if you give ``/dev/zero``, your backup will never terminate.
The given files' metadata is saved as it would be saved without The given files' metadata is saved as it would be saved without
``--read-special`` (e.g. its name, its size [might be 0], its mode, etc.) - but ``--read-special`` (e.g. its name, its size [might be 0], its mode, etc.) -- but
additionally, also the content read from it will be saved for it. additionally, also the content read from it will be saved for it.
Restoring such files' content is currently only supported one at a time via Restoring such files' content is currently only supported one at a time via