That is caused by the transaction system used by ZFS: all writes are committed in 5 second transactions, and before that the blocks reserved for the write and the original blocks for CoW are both “used”

This is kind of the shittier part of the FS, as it means sync writes run twice: one to the ZIL, and then to the actual disk.

Reply to this note

Please Login to reply.

Discussion

i may literally lose my entire stack because of ZFS, shitty is not really quite sufficient

also should point out that it's lucky that i actually DID make a backup of my .bitcoin directory to an ext4 filesystem because there literally is no recovery methods for this

there is a tool that can search for bitcoin wallet.dat files, and i used it, and it found many possible candidates but the tool doesn't actually write the blocks anywhere that it finds the data on, idk even what this thing is fore tbh

but testdisk is finding filesystem header data all over this other disk that i'm pretty sure is where i just made a backup today, which should have the latest wallet.dat file and once i find that file and recover it, my ass is saved

but until then, i am in the waiting room for hell because if i've lost this wallet my life is rather difficult right now

Makes sense. Thanks for the explanation.