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

FAQ: Why is backing up an unmodified FAT filesystem slow on Linux?

Browse source
This commit is contained in:
Helmut Grohne 2024-09-23 09:52:14 +02:00 committed by Thomas Waldmann
parent f859100f84
commit f0bd01b98d
No known key found for this signature in database
GPG key ID: 243ACFA951F78E01
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/faq.rst
View file

@ -478,6 +478,17 @@ will only be applied to new chunks, not existing chunks. So it's safe
to change them.
Why is backing up an unmodified FAT filesystem slow on Linux?
-------------------------------------------------------------
By default, the files cache used by BorgBackup considers the inode of files.
When an inode number changes compared to the last backup, it hashes the file
again. The ``vfat`` kernel driver does not produce stable inode numbers by
default. One way to achieve stable inode numbering is mounting the filesystem
using ``nfs=nostale_ro``. Doing so implies mounting the filesystem read-only.
Another option is to not consider inode numbers in the files cache by passing
``--files-cache=ctime,size``.
Security
########