From: Jeff King <peff@peff.net>
To: 이규형 <leekyoohyung@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: The outputs of "git fsck --full" are not same. sometimes the outputs are OK, but sometimes it says a corrupted object.
Date: Mon, 7 Mar 2011 11:21:43 -0500 [thread overview]
Message-ID: <20110307162143.GC11934@sigill.intra.peff.net> (raw)
In-Reply-To: <4D73AC10.90902@gmail.com>
On Mon, Mar 07, 2011 at 12:45:20AM +0900, 이규형 wrote:
> I am using GIT to control the version of documents in my office.
>
> and I think it is very useful solution to manage Word, Powerpoint and Excel documents.
>
> But there is one problem. The outputs of "git fsck --full" are not same.
>
> sometimes the outputs are OK, but sometimes it says a corrupted object.
Fsck should be deterministic. So either there is a bug in git, or there
is a problem with your hardware. Have you tried copying the repository
to a different machine and repeating your fsck? I'm wondering if your
disk is bad and giving inconsistent data.
-Peff
prev parent reply other threads:[~2011-03-07 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 15:45 The outputs of "git fsck --full" are not same. sometimes the outputs are OK, but sometimes it says a corrupted object 이규형
2011-03-07 16:21 ` Jeff King [this message]
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=20110307162143.GC11934@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=leekyoohyung@gmail.com \
/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).