Stable yes, but no protection from bitrot, and the journal of ext4 is the band aid, instead of a cow fs like zfs or btrfs.
Stable yes, but no protection from bitrot, and the journal of ext4 is the band aid, instead of a cow fs like zfs or btrfs.
btrfs with its send/receive (incremental fs-level backups) is already stable enough for mostly everything (just has some issues with raid 5/6), and is much more performant than zfs. And it is also in the linux kernel tree (quite hugely useful). Of course, if more zfs-like functionality is what you look for.
It’s more like “Demoting Windows API from a virtual machine to some .so libraries and a loader executable”
Dual boot issues like this is why I stopped using windows not in a VM.
The only backup’ed data I have (/home) passes without fail with rsync -rlvnx -I --checksum
. Not sure what files could be corrupt :)
Memtest passed. Also, it got reproduced when I start a scrub again (the SIGILL)
This is a single SSD on my laptop.
I have a recent backup, but I think the problem might be it was done recently (within last week - within scrub timer), and while generally reading everything also works like a scrub, I dont have a dmesg error notifier. The backup is done by btrfs send/receive.
I think it is worth reading the actual discussion on github. Having votes public and having them visibly public on the web interface has compelling reasons. Namely enshittification hardening.
It’s also quite natural to stand by your words (or vote). I personally don’t think people should feel like the internet is their anonimized alt character of life. And if they need/want that, just do a throwaway account and hard vpn. Otherwise NSA (or equivalents) track us anyway.