Recent comments posted to this site:
git-annex was not crashing due to content in the git-annex branch, but due to a symlink in one of your regular git branches, probably master and origin/master.
This bug is fixed in git master, if you need the fix before the next release.
git annex unused --debug
; this will tell us the git command that's outputing the data it cannot process. Then you can try running that git command and see what the problem filename is.
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 :-)
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.
Hey Joey!
I'm not very tech savvy, but here is my question. I think for all cloud service providers, there is an upload limitation on how big one file may be. For example, I can't upload a file bigger than 100 MB on box.net. Does this affect git-annex at all? Will git-annex automatically split the file depending on the cloud provider or will I have to create small RAR archives of one large file to upload them?
Thanks! James
locale
setting may also be relevant. FWIW, I've tried to create a file with \xb4
in its name and have not gotten git-annex unused to crash on it.
Complete fsck is good, but once a week probably enough.
But please see if you can make fsck optional depending on if the machine is running on battery.