3 ms·
It wouldn't solve an actually corrupted filesystem. For network appliances, read-only root FS is probably the way to go anyway. (I'd say it's also worth doing
by rollcat 3y ago
It wouldn't solve an actually corrupted filesystem.
For network appliances, read-only root FS is probably the way to go anyway. (I'd say it's also worth doing it in general.)
(Disclaimer: avid fan of everything BSD, OpenBSD in particular.)
- ninkendo 3y agoOk say my root file system is read only, and say, /var/log is writable. The power goes out. Then what? Does /var/log just not mount until i type fsck? Aren’t i back to the same issue?
- accrual 3y agoIt's probably not a safe assumption to rely on for a device out in the field, but in my experience, OpenBSD's fsck typically works just fine unattended. I could pull the plug on my router right now and I would expect it to come back up on its own. However, yes, sometimes a badly timed power loss will break the filesystem in a way that requires a manual fsck.
- ninkendo 3y agoI’ve had 3 power outages this year since installing OpenBSD (which is a lot for my area, admittedly) and it has required manual intervention each time. My root FS is on an SSD, it that matters.