From b6556e50ad74a9d4ee029fc2d2ab4a376f46eb21 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 31 Jan 2017 12:47:49 -0400 Subject: [PATCH] response This commit was sponsored by Andreas on Patreon. --- ...t_1_48da28dbc7da82d4e06fd3ce7962dfc5._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/Git-annex_init_gets_stuck_on_exFAT/comment_1_48da28dbc7da82d4e06fd3ce7962dfc5._comment diff --git a/doc/forum/Git-annex_init_gets_stuck_on_exFAT/comment_1_48da28dbc7da82d4e06fd3ce7962dfc5._comment b/doc/forum/Git-annex_init_gets_stuck_on_exFAT/comment_1_48da28dbc7da82d4e06fd3ce7962dfc5._comment new file mode 100644 index 0000000000..7e44bab07e --- /dev/null +++ b/doc/forum/Git-annex_init_gets_stuck_on_exFAT/comment_1_48da28dbc7da82d4e06fd3ce7962dfc5._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2017-01-31T16:42:54Z" + content=""" +Despite v6 repo format being available now, git-annex still defaults to v5, +and so needs to use direct mode when run in a FAT filesystem. If you want +to use v6 repo mode, you will need to `git annex init --version=6` + +Based on some googling, "stuck" state in OSX top means that it's stuck in a +kernel call. This probably means that git-annex is waiting for a disk +access, or from output from one of its child processes (eg git commands). + +It would be helpful to look at the process tree and see what child +processes of git-annex are running at this point. +"""]]