# recovering a corrupted git repo

2 messages from 2013-01-07 to 2013-01-07. Participants: Phillip Susi, Christian Couder.
Thread: https://gitlist.dev/t/32547

## Phillip Susi, 2013-01-07 03:44

Subject: recovering a corrupted git repo
Message-ID: <50EA44BA.2030107@ubuntu.com>
URL: https://gitlist.dev/e/50EA44BA.2030107%40ubuntu.com

```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have not had any issue until I ran a git fsck recently, which
repored gzip and crc errors in some pack files.  git fsck does not
seem to repair the errors, only report them.  I would like to try to
rebuild my repository, without downloading any more from the origin
than I have to.  All of the commits I have added seem to still be
intact, so I assume the corruption in somewhere in the upstream
history packs.

How can I correct the errors, and fetch the corrupted upstream
history, while preserving my patches?  So far I have exported my
patches as bundles, and made a fresh clone from upstream, then pulled
the bundles back in, but there must be a better way that only fetches
the corrupted bits from upstream?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQEcBAEBAgAGBQJQ6kS6AAoJEJrBOlT6nu75tFgIAJCI+DEWDVxddEQM5qhmz1y8
3JuqjTHp7gIXmQv6WGbEIehJrRfTBudQn+Ip2jLMwavvL16oZe+cf/uuLo393Z+T
pxEcWHOtjdU/XZeQOV//R/Cfo7PY5n8wfasgFYZuFesJchInwFocTI6S5x2B9kIB
dvLonoiDQwe9JqQaoAxM0OLTWe9aj0gc3c36+WUlRgRZijUhEogYQwU8aEoa+TMq
s2p+tbaNYKocRAafQ4824DMnuQTWb+HJVU4uI1pH2yB964Urq9ELSX2jxeSRdlaH
d+AoJ8oMdymmUwPeuyivcmQQHEGGsxxgCOuLSSHh1hcxMaytZNcEkVQ6OzuGyZk=
=yUr4
-----END PGP SIGNATURE-----

```

## Christian Couder, 2013-01-07 09:33

Subject: Re: recovering a corrupted git repo
Message-ID: <CAP8UFD2zRsJgUf9+EoCDURL4ywQFyPLTkQEGK1Af73m7e=ct5w@mail.gmail.com>
URL: https://gitlist.dev/e/CAP8UFD2zRsJgUf9%2BEoCDURL4ywQFyPLTkQEGK1Af73m7e%3Dct5w%40mail.gmail.com
In-Reply-To: <50EA44BA.2030107@ubuntu.com>

```
On Mon, Jan 7, 2013 at 4:44 AM, Phillip Susi <psusi@ubuntu.com> wrote:
>
> I have not had any issue until I ran a git fsck recently, which
> repored gzip and crc errors in some pack files.  git fsck does not
> seem to repair the errors, only report them.  I would like to try to
> rebuild my repository, without downloading any more from the origin
> than I have to.  All of the commits I have added seem to still be
> intact, so I assume the corruption in somewhere in the upstream
> history packs.
>
> How can I correct the errors, and fetch the corrupted upstream
> history, while preserving my patches?  So far I have exported my
> patches as bundles, and made a fresh clone from upstream, then pulled
> the bundles back in, but there must be a better way that only fetches
> the corrupted bits from upstream?

The documentation about fixing broken repo is this one:

https://git.wiki.kernel.org/index.php/GitFaq#fix-broken-repo

Hope this helps,
Christian.

```
