From bb9ba8dd94d91cd577ddde08343c8e7ec14f6d58 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 29 Nov 2023 13:42:12 -0400 Subject: [PATCH] comment --- ...1_65460ed123404478ae59fed1b5cff627._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/forum/very_slow_on_exfat_drives/comment_11_65460ed123404478ae59fed1b5cff627._comment diff --git a/doc/forum/very_slow_on_exfat_drives/comment_11_65460ed123404478ae59fed1b5cff627._comment b/doc/forum/very_slow_on_exfat_drives/comment_11_65460ed123404478ae59fed1b5cff627._comment new file mode 100644 index 0000000000..5b4cac8ac2 --- /dev/null +++ b/doc/forum/very_slow_on_exfat_drives/comment_11_65460ed123404478ae59fed1b5cff627._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 11""" + date="2023-11-29T17:36:28Z" + content=""" +What might be happening on the exfat drive is, every time that filesystem +is mounted, it generates new inode numbers for all the files. So when you +run `git status`, git sees the new inode and needs to do work to determine +if it's changed. When the file is an annexed file that is unlocked (which +all annexed files necessarily are on this filesystem since it doesn't +support symlinks), git status needs to ask git-annex about it. +And git-annex has to either re-hash the file (for SHA) or do a +smaller amount of work (for WORM). + +A bare repository does get around that. But what I tend to use in these +situations is a [[/special_remotes/directory]] special remote configured +with `ignoreinodes=yes`. +"""]]