Bazaar on the slow track

Quite. I'd venture to say that if you're using git fsck, you haven't had a hardware failure, and you're not hacking git, you're probably doing something unnecessary. It's *that* reliable. (I'd actually almost forgotten that git fsck existed: I haven't run it in anger in years.)

I concur that it is nearly impossible to lose work in git: making a new branch before doing something you're scared about suffices in basically all cases, and if you forget that there is the reflog. I've done massive history rewrites and routinely do partial history rewrites and tree partitions and have never lost a byte. (Having said that, I'm sure something horrible will happen now and I'll lose the last year's work or something. Not even git is immune to Murphy's Law.)