mirror of
https://github.com/borgbackup/borg.git
synced 2025-01-03 05:35:58 +00:00
Merge pull request #8408 from helmutg/faq-slow-fat
FAQ: Why is backing up an unmodified FAT filesystem slow on Linux?
This commit is contained in:
commit
1e6f71f2f5
1 changed files with 11 additions and 0 deletions
11
docs/faq.rst
11
docs/faq.rst
|
@ -357,6 +357,17 @@ to change them.
|
||||||
|
|
||||||
Use ``borg repo-compress`` to efficiently recompress a complete repository.
|
Use ``borg repo-compress`` to efficiently recompress a complete repository.
|
||||||
|
|
||||||
|
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
|
Security
|
||||||
########
|
########
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue