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

docs: document behavior for filesystems with inconsistent inodes, fixes borgbackup#5770 (#5965)

Browse source
This commit is contained in:
Jubjub 2021-08-25 21:43:47 +02:00 committed by GitHub
parent 795d9abad2
commit 0393cfac6c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/faq.rst
View file

@ -987,6 +987,12 @@ stable. If the directory where you mount a filesystem is different every time,
Borg assumes they are different files. This is true even if you backup these
files with relative pathnames - borg uses full pathnames in files cache regardless.
It is possible for some filesystems, such as ``mergerfs`` or network filesystems,
to return inconsistent inode numbers across runs, causing borg to consider them changed.
A workaround is to set the option ``--files-cache=ctime,size`` to exclude the inode
number comparison from the files cache check so that files with different inode
numbers won't be treated as modified.
Is there a way to limit bandwidth with Borg?
--------------------------------------------