From: Sitaram Chamarty <sitaramc@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: does a successful 'git gc' imply 'git fsck'
Date: Sun, 2 Dec 2012 08:01:49 +0530 [thread overview]
Message-ID: <CAMK1S_iBq1ReGkjuy2UBENSQXOWyKj2ZzSCcg7Z89FVtVL2wMw@mail.gmail.com> (raw)
Hi,
Background: I have a situation where I have to fix up a few hundred
repos in terms of 'git gc' (the auto gc seems to have failed in many
cases; they have far more than 6700 loose objects). I also found some
corrupted objects in some cases that prevent the gc from completing.
I am running "git gc" followed by "git fsck". The majority of the
repos I have worked through so far appear to be fine, but in the
larger repos (upwards of 2-3 GB) the git fsck is taking almost 5 times
longer than the 'gc'.
If I could assume that a successful 'git gc' means an fsck is not
needed, I'd save a lot of time. Hence my question.
--
Sitaram
next reply other threads:[~2012-12-02 2:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-02 2:31 Sitaram Chamarty [this message]
2012-12-02 4:28 ` does a successful 'git gc' imply 'git fsck' Shawn Pearce
2012-12-02 8:46 ` Sitaram Chamarty
2012-12-02 9:31 ` Junio C Hamano
2012-12-03 13:14 ` Sitaram Chamarty
2012-12-03 13:46 ` Matthieu Moy
2012-12-03 14:06 ` 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=CAMK1S_iBq1ReGkjuy2UBENSQXOWyKj2ZzSCcg7Z89FVtVL2wMw@mail.gmail.com \
--to=sitaramc@gmail.com \
--cc=git@vger.kernel.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).