From: nobodyinperson Date: Tue, 12 Dec 2023 12:44:38 +0000 (+0000) Subject: Added a comment X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~29^2~103^2~2 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=7aebfd606837fc8817102dc7f962aecda35d07fd;p=git-annex.git Added a comment --- diff --git a/doc/forum/very_slow_on_exfat_drives/comment_13_1d6588477082dd6de6eaad02fdc53463._comment b/doc/forum/very_slow_on_exfat_drives/comment_13_1d6588477082dd6de6eaad02fdc53463._comment new file mode 100644 index 0000000000..d99d5b0a61 --- /dev/null +++ b/doc/forum/very_slow_on_exfat_drives/comment_13_1d6588477082dd6de6eaad02fdc53463._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="nobodyinperson" + avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5" + subject="comment 13" + date="2023-12-12T12:44:38Z" + content=""" +A directory special remote is just a bunch of files. A bare repo has the git history and all the metadata for the bunch of files. Git itself on slow and bad filesystems is not fun and git-annex having to comb through many git objects to extract metadata for the actual annexed files is most likely the bottleneck here. Best is to not run any git-annex commands directly on the bad filesystem, but elsewhere and operate the bad filesystem repo as a remote. Then you let git-annex gather its information on a fast filesysetm and hardware and let it do only the copying of real files to and from the bad filesystem. At least that's my experience. +"""]]