RIP, a lot of files are corrupted...
https://nostr.download/c1f041dab282be896f5c85cf6aacc7b4dad2cfec89059723d74574882e50abc7.webp
Discussion
What does "corrupted" mean?
Does it really the case that those files' contents don't each hash to their name?
Yea, the filename is (was) the hash so im just hashing the file again and comparing it to the filename
If those file contents don't each hash to their name and they're not empty contents: Is it possible that there is some common "seed" that they were hashed with and you just need to find that seed? Or some common xor that is needed but not known that makes them appear "corrupted"? If they're not empty contents, I wouldn't ditch them just yet.
This whole ordeal made me triple check my backups yesterday 🫡
Yes, ill be putting a serious backup plan in place in future for everything i build, this is not worth the headache.
This is the first seriously data loss event I've had in many years of running stuff.
No backups?
None, but going forward there will be, this is nostr.download data btw
19,899 files remain, before disk fuck up, there was ~80k files