fsck scheduling problems

Bug #1248224 reported by gregrwm on 2013-11-05
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mountall (Ubuntu)

Bug Description

   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

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)

gregrwm (gregrwm) wrote :
gregrwm (gregrwm) wrote :
Steve Langasek (vorlon) on 2013-11-07
Changed in mountall (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
gregrwm (gregrwm) wrote :

2 fscks (on same disc) running simultaneously on precise.

gregrwm (gregrwm) wrote :
gregrwm (gregrwm) wrote :
To post a comment you must log in.