The following occurs in a directory that is shared on an NFS server:

/media/mybook/movies $ git init
Initialized empty Git repository in /media/mybook/movies/.git/
/media/mybook/movies $ git annex init mybook-movies
init mybook-movies 
git-annex: waitToSetLock: resource exhausted (No locks available)
failed
git-annex: init: 1 failed
/media/mybook/movies $

This happens reliably. Is there any way around it? I have shell access on the NFS server, but it is a NAS, so I don't think it is capable of running git-annex.

done

git-annex uses locking to avoid problems if multiple processes are run at the same time.

I just tested on NFS, with Linux on the server and client, and it works ok. It seems your NFS client (or server) must not support fncl locking. What OS is your NAS running?

Comment by http://joey.kitenet.net/ Tue Nov 15 04:40:35 2011

You might try mounting your NAS with the mount option local_lock=all

This will keep the lock files on your (I assume linux) client. If you do this make sure you don't have another client using git-annex in the same NFS directory.

Comment by http://joey.kitenet.net/ Tue Nov 15 04:46:13 2011
I did a bit of research and my NAS had ancient NFS software on it. I upgraded that and things are now working as expected. Sorry for the noise.
Comment by http://cgray.myopenid.com/ Tue Nov 15 05:14:03 2011
Comments on this page are closed.