On Sun, Nov 11, 2018 at 09:08:55PM +0000, Dmitry Bogatov wrote: > [2007-01-29 17:37] Ari Sovijärvi <[email protected]> > > The JFS filesystem replays its journal when FSCK is run. Without > > journal replay the filesystem will not allow mount as RW. When running > > on batteries and the root filesystem is JFS, after a crash the system is > > left in unusable state since FSCK is skipped and as a result the remount > > to read/write attempt fails. > > > > Maybe we need a check if we're using JFS and then unconditionally run > > FSCK. > > While adding yet another special check into `checkroot.sh' would > definitely solve problem at hand, probably there is something better, > less ad-hoc? Any ideas?
Running fsck at boot is useless and harmful for any modern filesystem. Sure, for ext2 it was needed to at least somewhat reduce data loss you just suffered, but anything newer is crash safe. Thus, what about removing fsck in the general case? Filesystems like btrfs or XFS had stubs since forever, for ext4 all it gives you is an annoying check if the machine's clock is unpowered or missing. And JFS doesn't do the full check either, it merely apparently needs (or more likely needed -- this report is 11¾ years old) only a trigger for the journal replay. So I propose: 1. checking if JFS still needs this 2. talking with any filesystem maintainer like TyT'so if fsck-on-boot can be dropped for their filesystem 3. making fsck no longer conditional (for that poor ext2 user) Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢰⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ I was born a dumb, ugly and work-loving kid, then I got swapped on ⠈⠳⣄⠀⠀⠀⠀ the maternity ward.
