Public bug reported:
problem 1: fsck column in /etc/fstab is flatly ignored. if the sysadm
wants a particular order of events, she should be able to specify it and have
it heeded. failing that, as a last resort, at least the fstab manpage should
reflect reality.
problem 2: fscks for partitions on the same disc were run simultaneously.
is this efficient? bootup time took 2240 seconds. and when the sysadm went to
the trouble to specify in fstab how to do it properly, this is annoying.
problem 3: nobootwait was ignored. the root partition fsck had finished
far earlier than others, and yet the bootup completion waited for the other
fscks to complete.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: mountall 2.52
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
.run.mount.utab:
ApportVersion: 2.12.6-0ubuntu1
Architecture: i386
Date: Tue Nov 5 05:10:24 2013
MarkForUpload: True
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic
root=UUID=49ae3c19-e112-427c-8a68-4506e994071a ro noplymouth INIT_VERBOSE=yes
panic=30
SourcePackage: mountall
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: mountall (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248224
Title:
fsck scheduling problems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1248224/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
