git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
ESEugene Sajine <euguess@gmail.com>
Date
Apr 5, 2010, 13:42 UTC
Message-ID
<l2m76c5b8581004050642n2ea328f6wdbfbe3991a1f5e50@mail.gmail.com>
In-Reply-To
<v2i76c5b8581004032052q950584e1y603319ec6f341542@mail.gmail.com>
Show 23 quoted lines
>> 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
>

Well, I have removed the file "RENAMEDREF..1" and it didn't resolve the problem. But then i made a "find -name REN*" and found another instance in logs folder. Removing this actually resolved the problem with gc. Still - i have no idea how this ref has appeared there as i believe there was no renaming operations done as well as no manual creation of such ref of course...

Thanks, Eugene

Previous: Eugene Sajine
Message 6 of 6 in “git gc error - cannot lock ref 'RENAMED-REF..1'”
  1. Eugene SajineApr 1, 2010
  2. Eugene SajineApr 2, 2010
  3. Eugene SajineApr 3, 2010
  4. Jeff KingApr 3, 2010
  5. Eugene SajineApr 4, 2010
  6. Eugene SajineApr 5, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.