Re: Massive repository corruptions
- From
- Enrico Weigelt <weigelt@metux.de>
- Date
- Jul 13, 2010, 05:03 UTC
- Message-ID
- <20100713050350.GB29392@nibiru.local>
- In-Reply-To
- <AANLkTilXQ3VgPjihf0pjt4QPN-nCjwAWyHwoosLMeRpH@mail.gmail.com>
* Avery Pennarun <apenwarr@gmail.com> wrote:
Show 5 quoted lines
> Multiple simultaneous gc's shouldn't be a problem - git locks things > as it needs them. Plus, git only removes objects after it has safely > created a new packfile that contains them. Maybe a filesystem filling > up could cause a problem, but git should be detecting that if it > happens (maybe there's a bug that causes it to not notice, though).
Okay.
> You could experience corruption if your computer crashed before > everything was synced to disk.
No machine crash, and no sign of filesystem or disk problems (according to kernel log).
> Do you know which packfiles are corrupted? Does 'git index-pack' on > the files reveal anything?
git@blackwidow ~/metux/work.git/pack $ git index-pack pack-3b6cbd5dc5f54cf390cfaa479cac6a99d7401375.pack error: inflate: data stream error (incorrect data check) fatal: pack has bad object at offset 37075832: inflate returned -3
(that's essentially the same git-gc says)
git@blackwidow ~/metux/work.git/pack $ git unpack-objects -r < pack-3b6cbd5dc5f54cf390cfaa479cac6a99d7401375.pack error: inflate: data stream error (incorrect data check) error: inflate returned -3
error: inflate: data stream error (incorrect data check) error: inflate returned -3
Unpacking objects: 100% (1223/1223), done. fatal: final sha1 did not match
cu
-- ---------------------------------------------------------------------- Enrico Weigelt, metux IT service -- http://www.metux.de/ phone: +49 36207 519931 email: weigelt@metux.de mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 ---------------------------------------------------------------------- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme ----------------------------------------------------------------------