Hacker News new | ask | show | jobs
by assttoasstmgr 1464 days ago
Recently had an OpenBSD VM experience disk corruption so badly it rendered itself unbootable (and the UFS fsck made the problem worse). The corruption happened as a result of an improper shutdown of the hypervisor due to HW failure. (All the Windows and Linux VMs recovered gracefully.) The only fix was to reinstall the entire base OS from the DVD (the rest of the data was still on the disk; the system was simply unbootable). I can't say I've ever had Linux become unbootable due to ext{2,3,4} corruption in probably 20 years. With OBSD I wouldn't even think about filing a bug report for something like this because I don't have desire to get flamed on mailing lists. My critique here is the standard Linux filesystems like ext4 have reached or exceeded NTFS levels of maturity and stability while I cannot say the same about the BSDs. (Though you can enjoy the same experience with XFS unless things have changed...)
2 comments

Yes I think the state of UFS in OpenBSD is the biggest sore point for me. If I can’t rely on a basic building block of the OS what can I really use it for?

I will say FreeBSD is stellar with ZFS and XFS is very very stable these days - even btrfs functions as a decent ext4 replacement.

> I've ever had Linux become unbootable due to ext{2,3,4} corruption in probably 20 years.

systemd can put your booting in an infinite loop instead, true progress.

Or, at the other end, systemd causing an infinite loop preventing shutdown.

Not to mention the pain in between.

TIL there have never been rc bugs before.
Such wit, amazing!