retitle 566072 fsck now failing hard for unavailable filesystems thanks I was recently bit by this bug as well. Filesystems marked 'noauto' that are not available at boot, and were previously not being checked or at most experiencing non-fatal errors, are now experiencing fatal errors that interupt the boot process.
This means that fsck's behavior has changed for either of the following: * skipping checks on 'noauto' filesystems, or * failing for unavailable filesystems My opinion is that fsck should *not* skip checking filesystems that are marked 'noauto'. 'noauto' refers only to whether or not the filesystem should be mounted at boot. I see no reason why fsck should not check available filesystems at boot time just because they will not be mounted. I therefore believe that fsck should just not fail hard if a filesystem is not available. This seems pretty straighforward. jamie.
pgpVZ4TvNAyx8.pgp
Description: PGP signature
