mirror/borg
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2025-03-10 06:03:38 +00:00
Code Issues Releases Wiki Activity

Merge pull request #7548 from sashadev-sky/option-x-help-1.2

Browse source 
improve --one-file-system help /docs
This commit is contained in:
TW 2023-05-06 20:35:59 +02:00 • committed by GitHub
commit d1ddd57eaf
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
src/borg/archiver.py
View file

@ -3448,13 +3448,13 @@ class Archiver:
The ``-x`` or ``--one-file-system`` option excludes directories, that are mountpoints (and everything in them). The ``-x`` or ``--one-file-system`` option excludes directories, that are mountpoints (and everything in them).
It detects mountpoints by comparing the device number from the output of ``stat()`` of the directory and its It detects mountpoints by comparing the device number from the output of ``stat()`` of the directory and its
parent directory. Specifically, it excludes directories for which ``stat()`` reports a device number different parent directory. Specifically, it excludes directories for which ``stat()`` reports a device number different
from the device number of their parent. Be aware that in Linux (and possibly elsewhere) there are directories from the device number of their parent.
with device number different from their parent, which the kernel does not consider a mountpoint and also the In general: be aware that there are directories with device number different from their parent, which the kernel
other way around. Examples are bind mounts (possibly same device number, but always a mountpoint) and ALL does not consider a mountpoint and also the other way around.
subvolumes of a btrfs (different device number from parent but not necessarily a mountpoint). Therefore when Linux examples for this are bind mounts (possibly same device number, but always a mountpoint) and ALL
using ``--one-file-system``, one should make doubly sure that the backup works as intended especially when using subvolumes of a btrfs (different device number from parent but not necessarily a mountpoint).
btrfs. This is even more important, if the btrfs layout was created by someone else, e.g. a distribution macOS examples are the apfs mounts of a typical macOS installation.
installer. Therefore, when using ``--one-file-system``, you should double-check that the backup works as intended.
.. _list_item_flags: .. _list_item_flags:
@ -3580,7 +3580,8 @@ class Archiver:
fs_group = subparser.add_argument_group('Filesystem options') fs_group = subparser.add_argument_group('Filesystem options')
fs_group.add_argument('-x', '--one-file-system', dest='one_file_system', action='store_true', fs_group.add_argument('-x', '--one-file-system', dest='one_file_system', action='store_true',
help='stay in the same file system and do not store mount points of other file systems. This might behave different from your expectations, see the docs.') help='stay in the same file system and do not store mount points of other file systems - '
'this might behave different from your expectations, see the description below.')
fs_group.add_argument('--numeric-owner', dest='numeric_ids', action='store_true', fs_group.add_argument('--numeric-owner', dest='numeric_ids', action='store_true',
help='deprecated, use ``--numeric-ids`` instead') help='deprecated, use ``--numeric-ids`` instead')
fs_group.add_argument('--numeric-ids', dest='numeric_ids', action='store_true', fs_group.add_argument('--numeric-ids', dest='numeric_ids', action='store_true',