Oddbean new post about login | logout fwiw, i kind of doubt it's a leveldb issue, i've done thousands of syncs from scratch without corruption, usually these kind of things are due to specific hardware conflicts or bugs
really man? I have had this happen on many different drives, 20+ times the past couple years. this never used to happen.
doesn't have to be the drive, could be a CPU issue too, or memory, or OS, anything can introduce corruption bitcoind has always been a graet burn-in test for hardware
> bitcoind has always been a graet burn-in test for hardware No kidding. It's been difficult provisioning resources in my cluster to bitcoin, like it gets expensive if you run an enterprise stack. It feels like it was made to run on mostly shit hardware, more bang for the buck than consuming my expensive redundant/HA resources. I've also had some serious history with bitcoind corruption too. I had a support contract for a while and there was no shortage of DB corruption, mostly on junker hardware though.
usually I can just chainstate reindex but this is the first time I've had to do a full redownload... sigh.