mirror of
https://github.com/borgbackup/borg.git
synced 2024-12-24 16:55:36 +00:00
Merge pull request #3288 from ThomasWaldmann/doc-updates2
Doc updates 2
This commit is contained in:
commit
febb7ffca8
2 changed files with 8 additions and 10 deletions
|
@ -7,6 +7,7 @@ CHUNK_MIN_EXP and CHUNK_MAX_EXP give the exponent N of the 2^N minimum and
|
||||||
maximum chunk size. Required: CHUNK_MIN_EXP < CHUNK_MAX_EXP.
|
maximum chunk size. Required: CHUNK_MIN_EXP < CHUNK_MAX_EXP.
|
||||||
|
|
||||||
Defaults: 19 (2^19 == 512KiB) minimum, 23 (2^23 == 8MiB) maximum.
|
Defaults: 19 (2^19 == 512KiB) minimum, 23 (2^23 == 8MiB) maximum.
|
||||||
|
Currently it is not supported to give more than 23 as maximum.
|
||||||
|
|
||||||
HASH_MASK_BITS is the number of least-significant bits of the rolling hash
|
HASH_MASK_BITS is the number of least-significant bits of the rolling hash
|
||||||
that need to be zero to trigger a chunk cut.
|
that need to be zero to trigger a chunk cut.
|
||||||
|
|
|
@ -2691,9 +2691,6 @@ def define_archive_filters_group(subparser, *, sort_by=True, first_last=True):
|
||||||
and not include any other contents of the containing folder, this can be enabled
|
and not include any other contents of the containing folder, this can be enabled
|
||||||
through using the ``--keep-exclude-tags`` option.
|
through using the ``--keep-exclude-tags`` option.
|
||||||
|
|
||||||
Borg respects the nodump flag. Files flagged nodump will be marked as excluded (x)
|
|
||||||
in ``--list`` output.
|
|
||||||
|
|
||||||
Item flags
|
Item flags
|
||||||
++++++++++
|
++++++++++
|
||||||
|
|
||||||
|
@ -3307,13 +3304,13 @@ def define_archive_filters_group(subparser, *, sort_by=True, first_last=True):
|
||||||
|
|
||||||
borg delete borg
|
borg delete borg
|
||||||
|
|
||||||
Unless ``--inplace`` is specified, the upgrade process first
|
Unless ``--inplace`` is specified, the upgrade process first creates a backup
|
||||||
creates a backup copy of the repository, in
|
copy of the repository, in REPOSITORY.before-upgrade-DATETIME, using hardlinks.
|
||||||
REPOSITORY.before-upgrade-DATETIME, using hardlinks. This takes
|
This requires that the repository and its parent directory reside on same
|
||||||
longer than in place upgrades, but is much safer and gives
|
filesystem so the hardlink copy can work.
|
||||||
progress information (as opposed to ``cp -al``). Once you are
|
This takes longer than in place upgrades, but is much safer and gives
|
||||||
satisfied with the conversion, you can safely destroy the
|
progress information (as opposed to ``cp -al``). Once you are satisfied
|
||||||
backup copy.
|
with the conversion, you can safely destroy the backup copy.
|
||||||
|
|
||||||
WARNING: Running the upgrade in place will make the current
|
WARNING: Running the upgrade in place will make the current
|
||||||
copy unusable with older version, with no way of going back
|
copy unusable with older version, with no way of going back
|
||||||
|
|
Loading…
Reference in a new issue