upstream/borgbackup
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2026-02-22 17:31:10 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

#2800 - Better explanation of the --ignore-inode option relevance (#2802)

Browse source 
Fixes #2800
This commit is contained in:
Wladimir Palant 2017-07-05 17:16:31 +02:00 committed by enkore
parent 6ffa797bde
commit 7be39af581
1 changed files with 8 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
src/borg/archiver.py
View file

@ -2767,10 +2767,14 @@ class Archiver:
In the archive name, you may use the following placeholders:
{now}, {utcnow}, {fqdn}, {hostname}, {user} and some others.
To speed up pulling backups over sshfs and similar network file systems which do
not provide correct inode information the ``--ignore-inode`` flag can be used. This
potentially decreases reliability of change detection, while avoiding always reading
all files on these file systems.
Backup speed is increased by not reprocessing files that are already part of
existing archives and weren't modified. Normally, detecting file modifications
will take inode information into consideration. This is problematic for files
located on sshfs and similar network file systems which do not provide stable
inode numbers, such files will always be considered modified. The
``--ignore-inode`` flag can be used to prevent this and improve performance.
This flag will reduce reliability of change detection however, with files
considered unmodified as long as their size and modification time are unchanged.
The mount points of filesystems or filesystem snapshots should be the same for every
creation of a new archive to ensure fast operation. This is because the file cache that