How do I get rid of a wrong remote uuid?

Hello,

I had some trouble adding a remote (the files would not appear when I was copying them to the remote), so I started over and cloned an existing repository.

Of course, as I started over, I had a duplicate uuid for the remote, which would cause problems when trying to copy (I would have an error "git-annex-shell: expected repository UUID 70582c7b-0b57-4087-a9d1-77b5f5f3c75e but found UUID 335699ea-d5b8-49ff-b207-1571b5969afe").

I finally managed to find the wrong uuid in the .git/config file (there was a duplicated entry for the remote) and I'm now able to copy things to the remote repository, and "git annex sync" works well. However I still see a mention of this repository when I do a "git annex whereis":

cody:games schmitta$ git annex whereis
whereis dungeon_keeper_1.1.0.11.dmg (3 copies) 
    1cdfb490-0660-41fb-b7ce-74b89abb9aac -- top
    335699ea-d5b8-49ff-b207-1571b5969afe -- here (cody)
    70582c7b-0b57-4087-a9d1-77b5f5f3c75e

Where can I find where this last line come from, and how can I get rid of it? I tried saying that this uuid is dead, but git annex tells me it's not a remote name.

RSS Atom

comment 1

If it helps, I had a look at "git annex vicfg", and there is no mention of the extra UUID there.

Comment by Alan Schmitt — Sat Mar 8 06:42:29 2014

Remove comment

comment 2

Probably this will fix it:

git annex dead 70582c7b-0b57-4087-a9d1-77b5f5f3c75e

Comment by joeyh.name — Wed Mar 12 19:35:26 2014

Remove comment

comment 3

Unfortunately git annex tells me there is no such remote:

cody:games schmitta$ git annex dead 70582c7b-0b57-4087-a9d1-77b5f5f3c75e
dead 70582c7b-0b57-4087-a9d1-77b5f5f3c75e git-annex: there is no available git remote named "70582c7b-0b57-4087-a9d1-77b5f5f3c75e"

Comment by Alan Schmitt — Thu Mar 13 20:05:53 2014

Remove comment

comment 4

It seems that the git-annex branch's uuid.log must somehow not list this uuid, but it's used in the location tracking log files.

The only way I can think of that this could happen is if you had set up a repository, run git-annex init, and then went in and changed the annex.uuid setting to this other uuid, and added files with that misconfiguration. Does that sound like what happened?

The fix is just as evil as the cause -- you can edit .git/config to add a new, dummy git remote that has annex-uuid set to the problem uuid, and then git-annex dead can be used to kill the uuid via that remote. For example:

joey@darkstar:~/tmp/x>git annex whereis eep
whereis eep (1 copy) 
    00000a6d-e770-4ab9-a640-7d6272e9ffff
ok
joey@darkstar:~/tmp/x>git annex dead 00000a6d-e770-4ab9-a640-7d6272e9ffff
dead 00000a6d-e770-4ab9-a640-7d6272e9ffff git-annex: there is no available git remote named "00000a6d-e770-4ab9-a640-7d6272e9ffff"
- exit 1
joey@darkstar:~/tmp/x>git remote add dummy dummy
joey@darkstar:~/tmp/x>git config remote.dummy.annex-uuid 00000a6d-e770-4ab9-a640-7d6272e9ffff
joey@darkstar:~/tmp/x>git annex dead dummy
dead dummy ok
(Recording state in git...)
joey@darkstar:~/tmp/x>git annex whereis eep
whereis eep (0 copies) failed

Comment by joeyh.name — Fri Mar 14 17:46:23 2014

Remove comment

comment 5

Thanks, it worked!

Regarding how I got into that state, here is what happened: - I configured a new repository (git init, git annex init) on machine B - I added that repository as a remote from machine A - I started pushing files from machine A to machine B, starting with the file that later showed this problem - I then noticed that, although the files were said to be successfully sent, I could not see them on machine B (no symbolic link was created), even after a "git annex sync" there - I decided to start over, deleting the annex, and creating it from a clone of an existing annex - This resulted in a duplicated UUID for the same path, which led to this problem

Maybe some documentation on how to cleanly start over when things get in a bad state would be very useful.