laanwj on Nostr: it's definitely not impossible that there's a bug in leveldb ! maybe it's possible to ...
it's definitely not impossible that there's a bug in leveldb ! maybe it's possible to diagnose it if it keeps happening more or less consistently there
it's just that, data corruption messages tend to show as "error in leveldb" (because that's the thing causing most of i/o) and thus people are first to blame leveldb, it's such a common trope
i've investigated a few corrupted databases back in the day and every time it was a bitflip or some other issue more likely to be caused by hardware than software problems
while on reliable hardware it tends to be possible to run syncs back to back in a loop without trouble
the thing is, there are few workloads that put modern hardware to the test, and are also super-critical about every bit of correctness like a blockchain sync, so it makes sense you're not seeing problems with anything else
still, it could potentially be a bug that happens in very specific circumstances
Published at
2024-10-28 17:48:29Event JSON
{
"id": "fd88a154c2b74a49aa0c4450e31575437fa98a7b6663dd6e98e6b6cd9237ae3b",
"pubkey": "0aa39e5aef99a000a7bdb0b499158c92bc4aa20fb65931a52d055b5eb6dff738",
"created_at": 1730137709,
"kind": 1,
"tags": [
[
"e",
"b2e70f430300defb97b57bf3d94cf6546f8308418d20448fd2aad82959a1949b",
"",
"root"
],
[
"e",
"202381aef19b980ce53d35c017df17bb99503d2dd52843e7bcb7972aa6197570",
"",
"reply"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245",
"",
"mention"
],
[
"p",
"d986b8a48cef4950fc62f7dc2e0d277ca505757b5aa73f0959b20659e71f7cac",
"",
"mention"
]
],
"content": "it's definitely not impossible that there's a bug in leveldb ! maybe it's possible to diagnose it if it keeps happening more or less consistently there\n\nit's just that, data corruption messages tend to show as \"error in leveldb\" (because that's the thing causing most of i/o) and thus people are first to blame leveldb, it's such a common trope\n\ni've investigated a few corrupted databases back in the day and every time it was a bitflip or some other issue more likely to be caused by hardware than software problems\nwhile on reliable hardware it tends to be possible to run syncs back to back in a loop without trouble\n\nthe thing is, there are few workloads that put modern hardware to the test, and are also super-critical about every bit of correctness like a blockchain sync, so it makes sense you're not seeing problems with anything else\n\nstill, it could potentially be a bug that happens in very specific circumstances\n",
"sig": "81b37e2699f98ed42319a8a1f17910ad56adfe43967d3d2a4b33143ce0677378e0c21846078237519b68cd2704b7eeaec4ba53939d058646c30c33118126df70"
}