Skip to content

Commit

Permalink
Merge pull request #8408 from helmutg/faq-slow-fat
Browse files Browse the repository at this point in the history
FAQ: Why is backing up an unmodified FAT filesystem slow on Linux?
  • Loading branch information
ThomasWaldmann authored Sep 23, 2024
2 parents 5274548 + 70f173c commit 1e6f71f
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions docs/faq.rst
Original file line number Diff line number Diff line change
Expand Up @@ -357,6 +357,17 @@ to change them.

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
########

Expand Down

0 comments on commit 1e6f71f

Please sign in to comment.