Even things like basic GUI installers that can set up your filesystem don't exist! Manually screwing with partition layouts to get volume encryption isn't easy to use at all, honestly. Admittedly I think we're better off than we were 7 years ago, but it's still not a grand slam. I think I spent something like 3 weeks porting my server configuration from Ubuntu to NixOS, by hand, piece by piece, many years ago. Despite the prosthelytization you'll get from many died-in-the-wool users who forgot what it was like in the beginning, in order to use NixOS effectively you either need to learn Nix, or be willing to spend a lot of time on IRC asking questions, which will end up with. I'm sure it's possible to trash a ZFS volume but it's stood strong on some pretty dubious hardware configurations for me and where most other file systems would have failed. Not to mention frequent unscheduled power cuts, kernel panics (unrelated to ZFS), and so on and so forth. It's worked flawlessly when SATA controllers have died (one motherboard would randomly drop HDDs when the controllers experienced high IOPS - which would be enough to trash any normal file system but ZFS survived it with literally no data loss). If Btrfs only works when hardware is behaving then that is absolutely a problem with Btrfs.Īs for my experience with ZFS, it's kept consistency when disks have died. Heck, even in the 90s this was a known problem hence chkdsk on DOS marking bad sectors to somewhat mitigate data corruption on FAT file systems. ZFS was very much intended to be resilient when faced with bad hardware. That's the whole point of raiding and checksumming. Next gen file systems are supposed to be resilient even if hardware fails. if you dig deep enough into the problem, often the hardware is found to be at fault
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |