public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: "Stefan Näwe" <stefan.naewe@atlas-elektronik•com>
To: Git list <git@vger•kernel.org>
Subject: git gc gives "error: Could not read..."
Date: Mon, 1 Jun 2015 09:37:17 +0200	[thread overview]
Message-ID: <556C0BAD.80106@atlas-elektronik.com> (raw)

Hi there.

One of my repos started giving an error on 'git gc' recently:

 $ git gc
 error: Could not read 7713c3b1e9ea2dd9126244697389e4000bb39d85
 Counting objects: 3052, done.
 Delta compression using up to 4 threads.
 Compressing objects: 100% (531/531), done.
 Writing objects: 100% (3052/3052), done.
 Total 3052 (delta 2504), reused 3052 (delta 2504)
 error: Could not read 7713c3b1e9ea2dd9126244697389e4000bb39d85

(Yes, the error comes twice).

I tried:

 $ git cat-file -t 7713c3b1e9ea2dd9126244
 fatal: Not a valid object name 7713c3b1e9ea2dd9126244


Otherwise, everything works fine.

I used that repo initially on Win7 with an older msysgit installation but
also tried the latest git-for-windows installer, and version 2.4.2 on linux.
All give the same error (no matter if I clone or copy the repo).

Unfortunately I cannot make the repo publically available.

Any chance to get rid of that error ?

Thanks,
  Stefan
-- 
----------------------------------------------------------------
/dev/random says: When it comes to humility, I'm the very BEST there is!
python -c "print '73746566616e2e6e616577654061746c61732d656c656b74726f6e696b2e636f6d'.decode('hex')" 
GPG Key fingerprint = 2DF5 E01B 09C3 7501 BCA9  9666 829B 49C5 9221 27AF

next             reply	other threads:[~2015-06-01  7:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01  7:37 Stefan Näwe [this message]
2015-06-01  8:14 ` git gc gives "error: Could not read..." Jeff King
2015-06-01  8:40   ` Stefan Näwe
2015-06-01  8:52     ` Jeff King
2015-06-01  9:14       ` Stefan Näwe
2015-06-01  9:58         ` Jeff King
2015-06-01 10:08           ` Stefan Näwe
2015-06-01 10:22             ` Jeff King
2015-06-01  9:54       ` [RFC/PATCH 0/3] silence missing-link warnings in some cases Jeff King
2015-06-01  9:56         ` [PATCH 1/3] add quieter versions of parse_{tree,commit} Jeff King
2015-06-01  9:56         ` [PATCH 2/3] silence broken link warnings with revs->ignore_missing_links Jeff King
2015-06-01  9:56         ` [PATCH 3/3] suppress errors on missing UNINTERESTING links Jeff King
2015-06-01 15:03         ` [RFC/PATCH 0/3] silence missing-link warnings in some cases Junio C Hamano
2015-06-01 15:41           ` Jeff King
2015-06-01 16:11             ` 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=556C0BAD.80106@atlas-elektronik.com \
    --to=stefan.naewe@atlas-elektronik$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox