From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Git ML <git@vger.kernel.org>, "Shawn O. Pearce" <spearce@spearce.org>
Subject: gc considered dangerous
Date: Sun, 8 Feb 2009 03:47:25 +0100 [thread overview]
Message-ID: <200902080347.25970.robin.rosenberg.lists@dewire.com> (raw)
I've seen this. Running git gc on Windows, while having Elipse open can kill your
object database.
Eclipse keeps the pack files open most of the time. Then you
launch git gui which recommends the user to do a git gc. I never
do (it *always* wants to do this), so I haven't encountered the
issue, but if gc doesn't find a new optimal pack it tries to rewrite a
new pack with the same id. So it rm's the idx file (fine) and the the
pack file (not ok) and gives up, which means it has a .pack file with
no index, so it cannot use it. Trying git gc again after eclipse exits
will execute the final stab on your objects.
The underlying bug is ofcource that Windows locks files when
they are open. A *nix* user does not suffer from this problem.
I'll investigate more at some other time. This is a preliminary
analysis.
-- robin
next reply other threads:[~2009-02-08 14:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 2:47 Robin Rosenberg [this message]
2009-02-08 14:34 ` gc considered dangerous Robin Rosenberg
2009-02-08 14:56 ` Johannes Schindelin
2009-02-08 16:04 ` Robin Rosenberg
2009-02-08 17:18 ` Johannes Schindelin
2009-02-08 18:24 ` Steffen Prohaska
2009-02-08 19:37 ` Robin Rosenberg
2009-02-08 20:00 ` Junio C Hamano
2009-02-08 20:08 ` Robin Rosenberg
2009-02-08 20:10 ` Robin Rosenberg
2009-02-09 6:59 ` Mike Hommey
2009-02-09 7:43 ` Junio C Hamano
2009-02-08 20:09 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200902080347.25970.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).