4 ms·

Really? As someone who has been using Linux since the 90s, for me the corruptions were extremely rare. Full fsck of course was happening regularly after unclean

• mpol 4y ago
  I had it happen many times as well. A power outage or a thrashing system were often accompanied with an fsck and file loss on ext2. This even included system files like libgtk.so because they were open at the moment of crashing. I never understood why reading/opening a file would corrupt it on a crash. I was happy to switch to Reiserfs.
• jmbwell 4y ago
  In my own experience, such situations were more likely when the system was already suffering some other issue or failure, like a failing array member or a volume out of space or something more routine, and in the course of troubleshooting, ah shit, now I have a corrupted root to deal with. Had one app that crashed inexplicably every year at midnight on Halloween. Or at least the two years I put up with it. Had to leave a party to rebuild a server from scratch when one failure turned into lots of failures. Not missing those days!
• jmclnx 4y ago
  Same here, but I think in those early days, after so many mounts (boots) on ext2, an fsck would execute. I think the number of times was 15.