From e7ae63f1f629407380162294a32e78a2f6be0855 Mon Sep 17 00:00:00 2001 From: Thomas Waldmann Date: Sun, 5 Nov 2017 20:06:23 +0100 Subject: [PATCH] clarify same-filesystem requirement for borg upgrade, fixes #2083 (cherry picked from commit fe746fa5948f948bb963830298d5f86b5e53ea12) --- src/borg/archiver.py | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/src/borg/archiver.py b/src/borg/archiver.py index 89e842b47..ac5d0bffd 100644 --- a/src/borg/archiver.py +++ b/src/borg/archiver.py @@ -3499,13 +3499,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