On Thu, Jun 08, 2017 at 09:44:07AM +0200, David Coppa wrote: > > Straightforward update to git-2.13.1.
Hi, With this update, many of my repos started looking corrupted. Whatever I did generated messages like this: $ git status error: sha1 mismatch 12cc7ead7a435b5f2617e0a6c069bb6fcb155703 fatal: bad object HEAD $ git log error: sha1 mismatch 12cc7ead7a435b5f2617e0a6c069bb6fcb155703 fatal: bad object HEAD and git fsck only spits out tons of errors like this: error: sha1 mismatch for .git/objects/f9/cd88b8c0f7c4028cab06db0574af5d9c867fce (expected f9cd88b8c0f7c4028cab06db0574af5d9c867fce) error: f9cd88b8c0f7c4028cab06db0574af5d9c867fce: object corrupt or missing: .git/objects/f9/cd88b8c0f7c4028cab06db0574af5d9c867fce error: sha1 mismatch for .git/objects/fa/e5d73ad3484aab54ad2913af285855652daca6 (expected fae5d73ad3484aab54ad2913af285855652daca6) error: fae5d73ad3484aab54ad2913af285855652daca6: object corrupt or missing: .git/objects/fa/e5d73ad3484aab54ad2913af285855652daca6 [...] error: HEAD: invalid reflog entry e6eeef466d4ba8e6e61867bf0bf6f60f42ba4cf7 error: HEAD: invalid reflog entry 12cc7ead7a435b5f2617e0a6c069bb6fcb155703 error: refs/heads/master: invalid reflog entry 9b750e8e1b77f5a07feba5277e6d17ff0f959796 error: refs/heads/master: invalid reflog entry 9b750e8e1b77f5a07feba5277e6d17ff0f959796 [...] Reverting to 2.13.0p0 appears to have fixed all the problems I saw.
