"Git gc" complains about a bad object, but "Git fsck" does not. How can I find references to this bad object?

When I run git gc

I get the following output:

error: Could not read bf493234ee6eb0ca12573136510e35d12f1adc51
Counting objects: 885373, done.
Delta compression using up to 12 threads.
Compressing objects: 100% (150591/150591), done.
Writing objects: 100% (885373/885373), done.
Total 885373 (delta 480155), reused 885373 (delta 480155)
Removing duplicate objects: 100% (256/256), done.
error: Could not read bf493234ee6eb0ca12573136510e35d12f1adc51
Checking connectivity: 908348, done.

      

However, at startup git fsck

, only the number of dangling objects is displayed, and no distortion was detected. Likewise, a grep -r "bf49" ~/git/.git/logs

does not appear.

How can I track down what is referencing this non-existent object and why is it not finding git fsck

it?

+3


source to share


1 answer


Before git fsck

do git gc --aggressive --prune=now

.



This will clear all wrapped data. after it starts up again fsck

.

-1


source







All Articles