I gave a solution.  In my first reply:

If a particular filesystem is not always present, then you should
configure the disk so that the fsck pass number is 0, and that mount
option "noauto" is present so that the filesystem is not mounted at boot
time. Then it will not interrupt the boot process, and the system will
not try to mount the filesystem (and fail if it is not present).

Right now, we do have a solution where if someone hot-plugs a USB drive
after boot, it is automatically mounted.  I don't think the automount
code actually does an fsck by default, but that could be fixed.   So we
have one solution for disks that people just plug in, and that works;
maybe it needs to be fixed to better deal with automatically fscking
filesystems, but we have one solution.

We have another solution for permanently mounted disks that are always
there, and that is the traditional /etc/fstab solution.

We have yet ANOTHER solution for drives that users manually mount, where
the fsck pass number is set to 0, and the mount option "noauto" is set.

This is something which all other Linux distributions want, and what
upstream supports, and for most users, this seems to be enough.  It
seems that you are demanding a FOURTH way of mounting and fsck'ing
filesystems, where they mostly work automatically, but fail in a soft
manner.   Changes to do this would have be in both mount and fsck, and
its not clear to me it's really worth it.

Certainly, I'm not volunteering to add YET MORE COMPLEXITY to Linux.  If
a paid Ubuntu engineer wants to architect and design this additional
complexity, and work with the various packages that would need extending
to support this Request For Enhancement, they can feel free to do so.
But I'm still not convinced this is something that should be done, and
it's not going to be done out of my spare time as an upstream
maintainer.

-- 
Failed file system check, weird behaviour
https://bugs.launchpad.net/bugs/68589
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to