mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2023-11-29 13:42:12 -04:00
parent e66a082b4e
commit bb9ba8dd94
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 18 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

18
doc/forum/very_slow_on_exfat_drives/comment_11_65460ed123404478ae59fed1b5cff627._comment Normal file
View file

@ -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`.
"""]]