{"thread":{"id":"10893","subject":"git-svn fetch failure: index.lock file exists","startedAt":"2007-11-16T00:07:20Z","lastAt":"2007-11-26T07:59:46Z","messageCount":3,"participants":["Ollie Wild","Eric Wong"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"60044","messageId":"65dd6fd50711151607x50639232w6d79322129c3d82@mail.gmail.com","threadId":"10893","inReplyTo":null,"subject":"git-svn fetch failure: index.lock file exists","fromName":"Ollie Wild","fromEmail":"aaw@google.com","sentAt":"2007-11-16T00:07:20Z","receivedAt":"2007-11-16T00:07:20Z","isPatch":false,"sender":{"key":"aaw@google.com","avatar":null},"body":"Hi,\n\nI've been using git-svn for a while now to work on gcc. Last night, I did a\n\n git svn fetch\n\nand got the following failure:\n\n Found possible branch point: svn+ssh://aaw@gcc.gnu.org/svn/gcc/trunk =>\n svn+ssh://aaw@gcc.gnu.org/svn/gcc/tags/libbid-last-merge, 128810\n Found branch parent: (tags/libbid-last-merge)\n 789aa951bbc6a49f791bf5109136335fc33222c5\n fatal: unable to create\n'.git/svn/tags/libbid-last-merge/index.lock': File exists\n read-tree 789aa951bbc6a49f791bf5109136335fc33222c5:\n command returned error: 128\n\nNaively, it looks to me like I've just got a stale lock file from a\nprevious run. However, I have no idea what the correct recovery\nstrategy is. Can I just delete the lock file? Do I need to do some\nsort of data validation?\n\nI'm using git version 1.5.2.5 with subversion version 1.4.5 (r25188).\n\nThanks,\nOllie\n"},{"id":"60173","messageId":"20071117211549.GC31598@mayonaise","threadId":"10893","inReplyTo":"65dd6fd50711151607x50639232w6d79322129c3d82@mail.gmail.com","subject":"Re: git-svn fetch failure: index.lock file exists","fromName":"Eric Wong","fromEmail":"normalperson@yhbt.net","sentAt":"2007-11-17T21:15:49Z","receivedAt":"2007-11-17T21:15:49Z","isPatch":false,"sender":{"key":"e@80x24.org","avatar":null},"body":"Ollie Wild wrote:\n> Hi,\n> \n> I've been using git-svn for a while now to work on gcc. Last night, I did a\n> \n> git svn fetch\n> \n> and got the following failure:\n> \n> Found possible branch point: svn+ssh://aaw@gcc.gnu.org/svn/gcc/trunk =>\n> svn+ssh://aaw@gcc.gnu.org/svn/gcc/tags/libbid-last-merge, 128810\n> Found branch parent: (tags/libbid-last-merge)\n> 789aa951bbc6a49f791bf5109136335fc33222c5\n> fatal: unable to create\n> '.git/svn/tags/libbid-last-merge/index.lock': File exists\n> read-tree 789aa951bbc6a49f791bf5109136335fc33222c5:\n> command returned error: 128\n> \n> Naively, it looks to me like I've just got a stale lock file from a\n> previous run. However, I have no idea what the correct recovery\n> strategy is. Can I just delete the lock file? Do I need to do some\n> sort of data validation?\n> \n> I'm using git version 1.5.2.5 with subversion version 1.4.5 (r25188).\n\nDid you interrupt git-svn in a previous run? But you should be able to\njust remove it; git-svn should verify that the index is in a consistent\nstate before it attempts to fetch again.\n\n-- \nEric Wong\n"},{"id":"60913","messageId":"65dd6fd50711252359y301aa775mc60cadbc59b682d0@mail.gmail.com","threadId":"10893","inReplyTo":"20071117211549.GC31598@mayonaise","subject":"Re: git-svn fetch failure: index.lock file exists","fromName":"Ollie Wild","fromEmail":"aaw@google.com","sentAt":"2007-11-26T07:59:46Z","receivedAt":"2007-11-26T07:59:46Z","isPatch":false,"sender":{"key":"aaw@google.com","avatar":null},"body":"Thanks, Eric. I managed to get things working before your response\nwhich means that (a) I'm a bit fuzzy on what I did and (b) I didn't\nrecord all the various messages that might be useful for debugging.\n\nI ended up having to delete the entire .git/svn/libbid-last-merge\ndirectory, as the fetch failed even with the lockfile removed. After\nthat, git-svn fetch retrieved a lot of old changes which had already\nbeen synched before but seems to have gotten itself back into a\nconsistent state.\n\nAs for whether or not I interrupted a previous fetch, it's possible,\nbut I don't remember doing so. I'd been doing mostly rebases against\nthe trunk, though, so any corruption could have occurred some time\nback.\n\nIf I run into any more problems, I'll let you know and provide more\ndetailed feedback about the types of errors I'm seeing and the steps\nrequired to correct it. Otherwise, I'll chalk this up to a one-off\nfailure due to a poorly timed interrupt.\n\nOllie\n\nOn Nov 17, 2007 1:15 PM, Eric Wong wrote:\n>\n> Ollie Wild wrote:\n> > Hi,\n> >\n> > I've been using git-svn for a while now to work on gcc. Last night, I did a\n> >\n> > git svn fetch\n> >\n> > and got the following failure:\n> >\n> > Found possible branch point: svn+ssh://aaw@gcc.gnu.org/svn/gcc/trunk =>\n> > svn+ssh://aaw@gcc.gnu.org/svn/gcc/tags/libbid-last-merge, 128810\n> > Found branch parent: (tags/libbid-last-merge)\n> > 789aa951bbc6a49f791bf5109136335fc33222c5\n> > fatal: unable to create\n> > '.git/svn/tags/libbid-last-merge/index.lock': File exists\n> > read-tree 789aa951bbc6a49f791bf5109136335fc33222c5:\n> > command returned error: 128\n> >\n> > Naively, it looks to me like I've just got a stale lock file from a\n> > previous run. However, I have no idea what the correct recovery\n> > strategy is. Can I just delete the lock file? Do I need to do some\n> > sort of data validation?\n> >\n> > I'm using git version 1.5.2.5 with subversion version 1.4.5 (r25188).\n>\n> Did you interrupt git-svn in a previous run? But you should be able to\n> just remove it; git-svn should verify that the index is in a consistent\n> state before it attempts to fetch again.\n>\n> --\n> Eric Wong\n>\n"}]}