Re: Suggestion: "verify/repair" option for 'git gc'
- From
- Alexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com>
- Date
- Oct 14, 2021, 12:47 UTC
- Message-ID
- <96bf2eff-f4c8-cae8-76cb-6eeb233cd1d3@syntevo.com>
- In-Reply-To
- <87h7dkh04o.fsf@evledraar.gmail.com>
On 14.10.2021 4:19, Ævar Arnfjörð Bjarmason wrote:
> I'd be interested in a copy of it, I've been slowly trying to improve > these sorts of corruption cases.
Sent.
> I wonder if this and other issues you encountered wouldn't need a full > "fsck", but merely gc triggering a complete repack.
That sounds slow :( For example, it's going to be a lot of disk write bandwidth. Just doing the verification along with regular gc sounds faster.
> Yes, we still definitely have cases where dealing with this sort of > thing can be very painful.
With the new remote promisor code, I think that auto-fixing corrupted blobs is easy enough (provided they can be found on any remote) ?