{"thread":{"id":"23287","subject":"git gc error - cannot lock ref 'RENAMED-REF..1'","startedAt":"2010-04-01T17:37:46Z","lastAt":"2010-04-05T13:42:30Z","messageCount":6,"participants":["Eugene Sajine","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"138348","messageId":"j2k76c5b8581004011037rb81d80cdu1a4713cde31d4b56@mail.gmail.com","threadId":"23287","inReplyTo":null,"subject":"git gc error - cannot lock ref 'RENAMED-REF..1'","fromName":"Eugene Sajine","fromEmail":"euguess@gmail.com","sentAt":"2010-04-01T17:37:46Z","receivedAt":"2010-04-01T17:37:46Z","isPatch":false,"sender":{"key":"euguess@gmail.com","avatar":null},"body":"I was running git gc weekly on my machine and today for some reason it\nfailed on one of my repos with an error saying\n\nError: cannot lock ref ‘RENAMED-REF..1’\nError: failed to run ref-log\n\nThe problem is I have no idea what it is talking about… “git show-ref”\ndoesn’t show anything even close to this name. Fools day joke?;)\nAny advice?\n\nThanks in advance,\nEugene\n"},{"id":"138382","messageId":"g2x76c5b8581004011908r35cbaf3au545b7f11bd6db8fc@mail.gmail.com","threadId":"23287","inReplyTo":"j2k76c5b8581004011037rb81d80cdu1a4713cde31d4b56@mail.gmail.com","subject":"git gc error - cannot lock ref 'RENAMED-REF..1'","fromName":"Eugene Sajine","fromEmail":"euguess@gmail.com","sentAt":"2010-04-02T02:08:45Z","receivedAt":"2010-04-02T02:08:45Z","isPatch":false,"sender":{"key":"euguess@gmail.com","avatar":null},"body":"Hi,\n\nI was running git gc weekly on my machine and today for some reason it\nfailed on one of my repos with an error saying\n\nError: cannot lock ref ‘RENAMED-REF..1’\nError: failed to run ref-log\n\nThe problem is I have no idea what it is talking about… “git show-ref”\ndoesn’t show anything even close to this name. Fools day joke?;)\nAny advice?\n\nThanks in advance,\nEugene\n"},{"id":"138487","messageId":"u2s76c5b8581004022038rf8aa0017l5dea55689c738fd9@mail.gmail.com","threadId":"23287","inReplyTo":"g2x76c5b8581004011908r35cbaf3au545b7f11bd6db8fc@mail.gmail.com","subject":"Re: git gc error - cannot lock ref 'RENAMED-REF..1'","fromName":"Eugene Sajine","fromEmail":"euguess@gmail.com","sentAt":"2010-04-03T03:38:03Z","receivedAt":"2010-04-03T03:38:03Z","isPatch":false,"sender":{"key":"euguess@gmail.com","avatar":null},"body":"Hi,\n\nCan, please, somebody advise what do i have to do in the situation\ndescribed below?\n\nThanks,\nEugene\n\nOn Thu, Apr 1, 2010 at 10:08 PM, Eugene Sajine wrote:\n> Hi,\n>\n> I was running git gc weekly on my machine and today for some reason it\n> failed on one of my repos with an error saying\n>\n> Error: cannot lock ref ‘RENAMED-REF..1’\n> Error: failed to run ref-log\n>\n> The problem is I have no idea what it is talking about… “git show-ref”\n> doesn’t show anything even close to this name. Fools day joke?;)\n> Any advice?\n>\n> Thanks in advance,\n> Eugene\n>\n"},{"id":"138488","messageId":"20100403042211.GA22150@coredump.intra.peff.net","threadId":"23287","inReplyTo":"u2s76c5b8581004022038rf8aa0017l5dea55689c738fd9@mail.gmail.com","subject":"Re: git gc error - cannot lock ref 'RENAMED-REF..1'","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2010-04-03T04:22:11Z","receivedAt":"2010-04-03T04:22:11Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Fri, Apr 02, 2010 at 11:38:03PM -0400, Eugene Sajine wrote:\n\n> On Thu, Apr 1, 2010 at 10:08 PM, Eugene Sajine wrote:\n> > Hi,\n> >\n> > I was running git gc weekly on my machine and today for some reason it\n> > failed on one of my repos with an error saying\n> >\n> > Error: cannot lock ref ‘RENAMED-REF..1’\n> > Error: failed to run ref-log\n> >\n> > The problem is I have no idea what it is talking about… “git show-ref”\n> > doesn’t show anything even close to this name. Fools day joke?;)\n> > Any advice?\n\nIf you look in the .git directory, is there a file named RENAMED-REF..1?\nI have no idea how you would create such a ref, nor why it would fail to\nlock (perhaps because of the funny name?), but removing it should\nprobably clear up your problem at least.\n\nThe name \"RENAMED-REF\" is only used by git during ref renames, and those\nonly happen when renaming branches (via \"git branch -m\") or remotes (via\n\"git remote rename\"). So presumably the source of the problem is related\nto one of those operations.\n\n-Peff\n"},{"id":"138523","messageId":"v2i76c5b8581004032052q950584e1y603319ec6f341542@mail.gmail.com","threadId":"23287","inReplyTo":"20100403042211.GA22150@coredump.intra.peff.net","subject":"Re: git gc error - cannot lock ref 'RENAMED-REF..1'","fromName":"Eugene Sajine","fromEmail":"euguess@gmail.com","sentAt":"2010-04-04T03:52:35Z","receivedAt":"2010-04-04T03:52:35Z","isPatch":false,"sender":{"key":"euguess@gmail.com","avatar":null},"body":"On Sat, Apr 3, 2010 at 12:22 AM, Jeff King wrote:\n> On Fri, Apr 02, 2010 at 11:38:03PM -0400, Eugene Sajine wrote:\n>\n>> On Thu, Apr 1, 2010 at 10:08 PM, Eugene Sajine wrote:\n>> > Hi,\n>> >\n>> > I was running git gc weekly on my machine and today for some reason it\n>> > failed on one of my repos with an error saying\n>> >\n>> > Error: cannot lock ref ‘RENAMED-REF..1’\n>> > Error: failed to run ref-log\n>> >\n>> > The problem is I have no idea what it is talking about… “git show-ref”\n>> > doesn’t show anything even close to this name. Fools day joke?;)\n>> > Any advice?\n>\n> If you look in the .git directory, is there a file named RENAMED-REF..1?\n> I have no idea how you would create such a ref, nor why it would fail to\n> lock (perhaps because of the funny name?), but removing it should\n> probably clear up your problem at least.\n>\n> The name \"RENAMED-REF\" is only used by git during ref renames, and those\n> only happen when renaming branches (via \"git branch -m\") or remotes (via\n> \"git remote rename\"). So presumably the source of the problem is related\n> to one of those operations.\n>\n> -Peff\n>\n\nThanks Jeff,\n\ni will take a look if i will be able to find this ref. The problem\nthough is that i don't remeber doing any renaming of branches or\nremote in this repo. Probably somebody did and pushed it to the\nmainline where i got it from by pull... I'll tyr to check this out.\n\nThanks,\nEugene\n"},{"id":"138591","messageId":"l2m76c5b8581004050642n2ea328f6wdbfbe3991a1f5e50@mail.gmail.com","threadId":"23287","inReplyTo":"v2i76c5b8581004032052q950584e1y603319ec6f341542@mail.gmail.com","subject":"Re: git gc error - cannot lock ref 'RENAMED-REF..1'","fromName":"Eugene Sajine","fromEmail":"euguess@gmail.com","sentAt":"2010-04-05T13:42:30Z","receivedAt":"2010-04-05T13:42:30Z","isPatch":false,"sender":{"key":"euguess@gmail.com","avatar":null},"body":">> If you look in the .git directory, is there a file named RENAMED-REF..1?\n>> I have no idea how you would create such a ref, nor why it would fail to\n>> lock (perhaps because of the funny name?), but removing it should\n>> probably clear up your problem at least.\n>>\n>> The name \"RENAMED-REF\" is only used by git during ref renames, and those\n>> only happen when renaming branches (via \"git branch -m\") or remotes (via\n>> \"git remote rename\"). So presumably the source of the problem is related\n>> to one of those operations.\n>>\n>> -Peff\n>>\n>\n> Thanks Jeff,\n>\n> i will take a look if i will be able to find this ref. The problem\n> though is that i don't remeber doing any renaming of branches or\n> remote in this repo. Probably somebody did and pushed it to the\n> mainline where i got it from by pull... I'll tyr to check this out.\n>\n> Thanks,\n> Eugene\n>\n\nWell, I have removed the file \"RENAMEDREF..1\" and it didn't resolve\nthe problem. But then i made a \"find -name REN*\" and found another\ninstance in logs folder. Removing this actually resolved the problem\nwith gc. Still - i have no idea how this ref has appeared there as i\nbelieve there was no renaming operations done as well as no manual\ncreation of such ref of course...\n\nThanks,\nEugene\n"}]}