This repository was archived by the owner on Nov 6, 2020. It is now read-only.
DB Corruption on parity v2.5.5 #10893
Labels
F1-panic 🔨
The client panics and exits without proper error handling.
M4-io 💾
Interaction with filesystem/databases.
Milestone
Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.
I just had a crash with DB corrupted on
v2.5.5
too.And parity isn't restoring anything it's simply stuck in limbo and requires full resync. Super annoying.
I don't see any errors in dmesg or anywhere else about failed sectors on my NVME drives, so it has to be something to do with parity:
The text was updated successfully, but these errors were encountered: