* git gc error - cannot lock ref 'RENAMED-REF..1'
@ 2010-04-01 17:37 Eugene Sajine
2010-04-02 2:08 ` Eugene Sajine
0 siblings, 1 reply; 6+ messages in thread
From: Eugene Sajine @ 2010-04-01 17:37 UTC (permalink / raw)
To: git, Eugene Sajine
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?
Thanks in advance,
Eugene
^ permalink raw reply [flat|nested] 6+ messages in thread
* git gc error - cannot lock ref 'RENAMED-REF..1'
2010-04-01 17:37 git gc error - cannot lock ref 'RENAMED-REF..1' Eugene Sajine
@ 2010-04-02 2:08 ` Eugene Sajine
2010-04-03 3:38 ` Eugene Sajine
0 siblings, 1 reply; 6+ messages in thread
From: Eugene Sajine @ 2010-04-02 2:08 UTC (permalink / raw)
To: git
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?
Thanks in advance,
Eugene
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: git gc error - cannot lock ref 'RENAMED-REF..1'
2010-04-02 2:08 ` Eugene Sajine
@ 2010-04-03 3:38 ` Eugene Sajine
2010-04-03 4:22 ` Jeff King
0 siblings, 1 reply; 6+ messages in thread
From: Eugene Sajine @ 2010-04-03 3:38 UTC (permalink / raw)
To: git
Hi,
Can, please, somebody advise what do i have to do in the situation
described below?
Thanks,
Eugene
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?
>
> Thanks in advance,
> Eugene
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: git gc error - cannot lock ref 'RENAMED-REF..1'
2010-04-03 3:38 ` Eugene Sajine
@ 2010-04-03 4:22 ` Jeff King
2010-04-04 3:52 ` Eugene Sajine
0 siblings, 1 reply; 6+ messages in thread
From: Jeff King @ 2010-04-03 4:22 UTC (permalink / raw)
To: Eugene Sajine; +Cc: git
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: git gc error - cannot lock ref 'RENAMED-REF..1'
2010-04-03 4:22 ` Jeff King
@ 2010-04-04 3:52 ` Eugene Sajine
2010-04-05 13:42 ` Eugene Sajine
0 siblings, 1 reply; 6+ messages in thread
From: Eugene Sajine @ 2010-04-04 3:52 UTC (permalink / raw)
To: Jeff King, git
On Sat, Apr 3, 2010 at 12:22 AM, Jeff King <peff@peff.net> wrote:
> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: git gc error - cannot lock ref 'RENAMED-REF..1'
2010-04-04 3:52 ` Eugene Sajine
@ 2010-04-05 13:42 ` Eugene Sajine
0 siblings, 0 replies; 6+ messages in thread
From: Eugene Sajine @ 2010-04-05 13:42 UTC (permalink / raw)
To: Jeff King, git
>> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2010-04-05 13:50 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-04-01 17:37 git gc error - cannot lock ref 'RENAMED-REF..1' Eugene Sajine
2010-04-02 2:08 ` Eugene Sajine
2010-04-03 3:38 ` Eugene Sajine
2010-04-03 4:22 ` Jeff King
2010-04-04 3:52 ` Eugene Sajine
2010-04-05 13:42 ` Eugene Sajine
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.