* Apparent bug in git-gc
@ 2014-09-15 23:34 Dale R. Worley
2014-09-16 0:30 ` Jeff King
0 siblings, 1 reply; 3+ messages in thread
From: Dale R. Worley @ 2014-09-15 23:34 UTC (permalink / raw)
To: git
I have an unpleasant bug in git-gc:
Git version: 1.8.3.1
Running on: Fedora 19 Gnu/Linux
I have an 11 GB repository. It passes git-fsck (though with a number
of dangling objects). But when I run git-gc on it, the file
refs/heads/master disappears. Since HEAD points to refs/heads/master,
this makes the repository unusable.
What should I do next?
Dale
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Apparent bug in git-gc
2014-09-15 23:34 Apparent bug in git-gc Dale R. Worley
@ 2014-09-16 0:30 ` Jeff King
2014-09-16 18:09 ` Dale R. Worley
0 siblings, 1 reply; 3+ messages in thread
From: Jeff King @ 2014-09-16 0:30 UTC (permalink / raw)
To: Dale R. Worley; +Cc: git
On Mon, Sep 15, 2014 at 07:34:03PM -0400, Dale R. Worley wrote:
> I have an 11 GB repository. It passes git-fsck (though with a number
> of dangling objects). But when I run git-gc on it, the file
> refs/heads/master disappears.
That's the expected behavior. Gc runs "git pack-refs", which puts an
entry into packed-refs and prunes the loose ref.
> Since HEAD points to refs/heads/master, this makes the repository
> unusable.
Unusable how? Does `git rev-parse refs/heads/master` still produce a
sha1? Does `git rev-parse HEAD`? If not, then that is definitely a bug.
-Peff
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Apparent bug in git-gc
2014-09-16 0:30 ` Jeff King
@ 2014-09-16 18:09 ` Dale R. Worley
0 siblings, 0 replies; 3+ messages in thread
From: Dale R. Worley @ 2014-09-16 18:09 UTC (permalink / raw)
To: Jeff King; +Cc: git
> From: Jeff King <peff@peff.net>
>
> > I have an 11 GB repository. It passes git-fsck (though with a number
> > of dangling objects). But when I run git-gc on it, the file
> > refs/heads/master disappears.
>
> That's the expected behavior. Gc runs "git pack-refs", which puts an
> entry into packed-refs and prunes the loose ref.
Arrrgh, damn! I knew that but I forgot it. Sorry about the trouble.
(At least I don't have to worry about fixing it now.)
Dale
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-09-16 18:09 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-09-15 23:34 Apparent bug in git-gc Dale R. Worley
2014-09-16 0:30 ` Jeff King
2014-09-16 18:09 ` Dale R. Worley
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.