[JFS's regular fsck does nothing but, and is needed to, trigger journal replay. If the journal replay is skipped, dirty fs will fail the mount, resulting in a boot failure if / . Being on battery skips fsck.]
On Tue, Nov 13, 2018 at 08:22:09PM +0000, Dmitry Bogatov wrote: > > control: tags -1 confirmed > > [2018-11-12 02:03] Adam Borowski <kilob...@angband.pl> > > On Mon, Nov 12, 2018 at 01:20:25AM +0100, Adam Borowski wrote: > > > 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 > > > > Yes, it does. > > > > So we still need fsck to boot, no matter if the computer is on battery or > > not. So this bug is still valid. > > Am I correct, that fsck (checkroot.sh) is actually needed only in case > of ext2 or jfs root? No idea about some weird filesystems -- but at least for ext*, there's a guy who knows it a wee bit better than any of us. Might also offer advice wrt other filesystems as well. Ted: what would you say about getting rid of fsck at boot for most filesystems? For the few that actually need it, being on battery shouldn't skip it. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!? ⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din ⠈⠳⣄⠀⠀⠀⠀
