git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Faheem Mitha <faheem@faheem.info>
To: git@vger.kernel.org
Subject: corrupt repos does not return error with `git fsck`
Date: Wed, 20 May 2015 21:47:15 +0530 (IST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1505202142540.9343@orwell.homelinux.org> (raw)


Hi,

Clone the repos https://github.com/fmitha/SICL.

Then

     git show 280c12ab49223c64c6f914944287a7d049cf4dd0

gives

     fatal: bad object 280c12ab49223c64c6f914944287a7d049cf4dd0

But

     git fsck

gives

     Checking object directories: 100% (256/256), done.
     Checking objects: 100% (49356/49356), done.

So `git fsck` does not return an error, though the repos is corrupt. This 
may be of interest to the developers.

Please CC me on any reply, I'm not subscribed to the list. Thanks.

                                             Regards, Faheem Mitha

             reply	other threads:[~2015-05-20 16:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 16:17 Faheem Mitha [this message]
2015-05-20 17:19 ` [PUB]corrupt repos does not return error with `git fsck` Matthieu Moy
2015-05-20 17:40   ` Johannes Schindelin
2015-05-20 18:02     ` Stefan Beller
2015-05-20 18:19       ` John Keeping
2015-05-20 18:22       ` Jeff King
2015-05-20 18:31         ` Jeff King
2015-05-20 20:39           ` Junio C Hamano
2015-05-20 20:57             ` Stefan Beller
2015-05-20 21:06               ` Junio C Hamano
2015-05-20 21:13                 ` Stefan Beller
2015-05-20 21:55             ` Jeff King
2015-05-20 20:16         ` Junio C Hamano
2015-05-20 18:24       ` Faheem Mitha
2015-05-20 18:54         ` Stefan Beller
2015-05-20 19:13           ` Faheem Mitha
2015-05-20 21:03       ` Matthieu Moy
2015-05-20 17:58   ` Faheem Mitha
2015-05-21  8:09     ` Matthieu Moy

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.11.1505202142540.9343@orwell.homelinux.org \
    --to=faheem@faheem.info \
    --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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).