Doing,

sudo sysctl -w kern.maxfilesperproc=400000

Somewhat works for me, git-annex watch at least starts up and takes a while to scan the directory, but it's not ideal. Also, creating files seems to work okay, when I remove a file the changes don't seem to get pushed across my other repos, running a sync on the remote repo fixes things.

That is a known problem/bug which is listed at inotify

Yes, the problem is fixed.

The repository was a normal git repository with path /tmp/çüş (git init) and with annex description "çüş" (git annex init çüş)

afaict, i can't reproduce the problem anymore either :-)

Use du -L for the disk space used locally. The other number is not currently available, but it would be nice to have. I also sometimes would like to have data on which backends are used how much, so making this git annex status --subdir is tempting. Unfortunatly, it's current implementation scans .git/annex/objects and not the disk tree (better for accurate numbers due to copies), so it would not be a very easy thing to add. Not massively hard, but not something I can pound out before I start work today..

Hi @joey! Perfect!... I'll do that then!

Thanks for your time man!

Since I can't reproduce it I am not sure, but it may be fixed by the commits I've just made.

I don't think this has to do with the path name of the repository containing utf-8 at all.

Your recipe for reproducing this depends on some pre-existing repository that I don't know how to set up to reproduce this bug. All I can guess is that, based on the "decodeUtf8" in the error message, it's coming from the one part of the code that still uses that, the union merger.

This is indeed the problem I've planned to work on today, as I see it too when things don't start off perfectly in sync.

Yes, this is a known problem with kqueue, it has to keep every directory in the tree open. On inotify I have a note that it may need to fork off extra watcher processes to deal with this. Of course that adds significant complication.

In the meantime, you may be able to increase your system's maximum allowed number of open files per process somehow.

(I doubt that the ssh-agent is related; git-annex does not use ssh-agent directly anyway..)

@Agustin you should be able to work around that with: cabal install git-annex --flags=-Inotify

I've fixed it properly for the next release, it should only be using that library on Linux.