Re: git gc error - cannot lock ref 'RENAMED-REF..1'

From: Eugene Sajine <euguess@gmail.com>
Date: Apr 4, 2010, 03:52 UTC
Message-ID: <v2i76c5b8581004032052q950584e1y603319ec6f341542@mail.gmail.com>
In-Reply-To: <20100403042211.GA22150@coredump.intra.peff.net>

On Sat, Apr 3, 2010 at 12:22 AM, Jeff King <peff@peff.net> wrote:

Show 27 quoted lines

> On Fri, Apr 02, 2010 at 11:38:03PM -0400, Eugene Sajine wrote:
>
>> On Thu, Apr 1, 2010 at 10:08 PM, Eugene Sajine <euguess@gmail.com> wrote:
>> > Hi,
>> >
>> > I was running git gc weekly on my machine and today for some reason it
>> > failed on one of my repos with an error saying
>> >
>> > Error: cannot lock ref ‘RENAMED-REF..1’
>> > Error: failed to run ref-log
>> >
>> > The problem is I have no idea what it is talking about… “git show-ref”
>> > doesn’t show anything even close to this name. Fools day joke?;)
>> > Any advice?
>
> If you look in the .git directory, is there a file named RENAMED-REF..1?
> I have no idea how you would create such a ref, nor why it would fail to
> lock (perhaps because of the funny name?), but removing it should
> probably clear up your problem at least.
>
> The name "RENAMED-REF" is only used by git during ref renames, and those
> only happen when renaming branches (via "git branch -m") or remotes (via
> "git remote rename"). So presumably the source of the problem is related
> to one of those operations.
>
> -Peff
>

Thanks Jeff,

i will take a look if i will be able to find this ref. The problem though is that i don't remeber doing any renaming of branches or remote in this repo. Probably somebody did and pushed it to the mainline where i got it from by pull... I'll tyr to check this out.

Thanks, Eugene