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

Merge pull request #3288 from ThomasWaldmann/doc-updates2

Browse source 
Doc updates 2
This commit is contained in:
TW 2017-11-05 22:18:41 +01:00 committed by GitHub
commit febb7ffca8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 8 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
docs/misc/create_chunker-params.txt
View file

@ -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.
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
that need to be zero to trigger a chunk cut.

17
src/borg/archiver.py
View file

@ -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
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
++++++++++
@ -3307,13 +3304,13 @@ def define_archive_filters_group(subparser, *, sort_by=True, first_last=True):
borg delete borg
Unless ``--inplace`` is specified, the upgrade process first
creates a backup copy of the repository, in
REPOSITORY.before-upgrade-DATETIME, using hardlinks. This takes
longer than in place upgrades, but is much safer and gives
progress information (as opposed to ``cp -al``). Once you are
satisfied with the conversion, you can safely destroy the
backup copy.
Unless ``--inplace`` is specified, the upgrade process first creates a backup
copy of the repository, in REPOSITORY.before-upgrade-DATETIME, using hardlinks.
This requires that the repository and its parent directory reside on same
filesystem so the hardlink copy can work.
This takes longer than in place upgrades, but is much safer and gives
progress information (as opposed to ``cp -al``). Once you are satisfied
with the conversion, you can safely destroy the backup copy.
WARNING: Running the upgrade in place will make the current
copy unusable with older version, with no way of going back