oh, and that probably goes for 'help' and other subcommands as well.

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.

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.

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?

It might make sense to put this functionality in git annex find. Perhaps a format string with a %s for example.

When I want that, I ls -l the file and look at the symlink to the key. Ie, in SHA1-s10481423--efc7eec0d711212842cd6bb8f957e1628146d6ed the size is 10481423 bytes.

It makes sense to have separate repositories when you have well-defined uses for them.

I have a separate repository just for music and podcasts, which I can put various places where I have no need of the overhead of a tree of other files.

If you're using it for whatever arbitrary large files you accumulate, I find it's useful to have them in one repository. This way I can rearrange things as makes sense. It might make sense to have "photos" and "isos" as categories today, but next year you might prefer to move those under 2011/{photos,isos}. It would certainly make sense to have different repositories for home, work, etc.

How to split repositories up for a home directory is a general problem that the vcs-home project has surely considered at one time or another.

Possible solutions:

This:

trusted repositories:
        UUID -- foo
semi-trusted repositories:
        UUID -- bar
untrusted repositories:
        UUID -- baz

or this:

        UUID -- trusted      -- foo
        UUID -- semi-trusted -- bar
        UUID -- untrusted    -- baz

or this:

known repositories (!/*/X):
        UUID -- ! foo
        UUID -- * bar
        UUID -- X baz

If you want to reformat this output, putting 'here', 'origin', etc into fixed formatting might make sense, as well. -- Richard

I could dig it out, but I am sure I said dots are fine and a whirly better.

Still, WONTFIX is fine.

After upgrading the repo, I still have to commit the changes, else git-annex won't let me uninit. Arguably a Good Thing, but I wanted to document it here.