This works with bind-mount, I might try with softlinks as well.
Going through git's data on push/pull can take ages on a spindle disk even if the repo is rather small in size. This is especially true if you are used to ssd speeds, but ssd storage is expensive. Storing the annex objects on a cheap spindle disk and everything else on a ssd makes things a lot faster.
Update: git-annex supports
.git/annex/being moved to a different disk than the rest of the repisitory, but does not support individual subdirectories, like.git/annex/objects/being on a different disk than the main.git/annex/directory. --Joey
I'll give it a try as soon as I get rid of this:
fatal: index file smaller than expected fatal: index file smaller than expected % git status fatal: index file smaller than expected %
And no, I am not sure where that is coming from all of a sudden... (it might have to do with a hard lockup of the whole system due to a faulty hdd I tested, but I didn't do anything to it for ages before that lock-up. So meh. Also, this is prolly off topic in here)
Richard
For future reference, git can recover from a corrupted index file with
rm .git/index; git reset --mixed.Of course, you lose any staged changes that were in the old index file, and may need to re-stage some files.
I had my git annex directory on a ssd and .git/annex on a hdd (using a symlink). I got errors when adding files because a move failed. I forgot to copy the error message. When I had .git/annex/objects on a hdd, everything worked as expected, there were no problems.
So what exactly will go wrong if I only have this one subdirectory on another filesystem?