From d463b7380511de07f3e28b0104a59a969652e022 Mon Sep 17 00:00:00 2001 From: "dermungo@19d0cb1f22d4169b48363cfff60c9ede2c14fffa" Date: Wed, 11 Jan 2017 14:10:51 +0000 Subject: [PATCH] --- .../Git-annex_init_gets_stuck_on_exFAT.mdwn | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 doc/forum/Git-annex_init_gets_stuck_on_exFAT.mdwn diff --git a/doc/forum/Git-annex_init_gets_stuck_on_exFAT.mdwn b/doc/forum/Git-annex_init_gets_stuck_on_exFAT.mdwn new file mode 100644 index 0000000000..4910d80e92 --- /dev/null +++ b/doc/forum/Git-annex_init_gets_stuck_on_exFAT.mdwn @@ -0,0 +1,30 @@ +I have just started using git annex, and I cloned the annex onto an external usb formatted as exFAT. I am using Mac OS X. + +The clone went fine, but when running `git annex init` the following happened + +``` + Detected a filesystem without fifo support. + + Disabling ssh connection caching. + + Detected a crippled filesystem. + + Disabling core.symlinks. +(merging origin/git-annex into git-annex...) +(recording state in git...) + + Enabling direct mode. +``` +then git annex appears to get stuck according to `top`: + +``` +PID COMMAND %CPU TIME #TH #WQ #PORT MEM PURG CMPRS PGRP PPID STATE BOOSTS + +86934 git-annex 0.0 01:07.09 4 0 13 4152K 0B 5684K 86933 86933 stuck *0[1] +``` + +I am running git-annex 6.20170101, so direct mode should no longer be used. Is that correct? If so what should I do to figure out what's going on? + + The most relevant related thread I could find was this one [Bare repo on USB ...](http://git-annex.branchable.com/forum/Bare_repo_on_USB_drive_not_providing_files/) which suggests exFAT may not work well on Linux. However, I mainly use this USB on my Macbook to supplement the SSD. Another possibly relevant thread is this one [Android table ... only exFAT...](http://git-annex.branchable.com/forum/Using_git_annex_with_Android_tablet_which_only_has_exFAT_and_no_symlinks/). + +I appreciate any assitance.