touch-packages team mailing list archive

[gregrwm <1432030@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

all fscks are scheduled and run simultaneously.  for those on different
spindles, that would be great.  for those sharing a spindle, this is
terribly inefficient.  checking all filesystems on this box
simultaneously spends nearly a half hour.  when sorted out so that
simultaneity is only across different spindles, it's done within a few
minutes.  that's the way it used to be, and still is on other distros.

i can certainly imagine mountall might be intending to have an algorithm
that sorts simultaneity by spindles.  if it intends it, it doesn't work.

even if such an algorithm usually worked well, fstab should still be
interpreted such that if the fsck column specifies values greater than
2, then the simultaneity specified in fstab should be followed.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: mountall 2.54ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic i686
ApportVersion: 2.16.1-0ubuntu2
Architecture: i386
Date: Fri Mar 13 14:54:37 2015
InstallationDate: Installed on 2015-01-16 (56 days ago)
InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Alpha i386 (20150114)
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz ro root=UUID=5116dd42-c618-49a4-885e-84c697b53abd panic=30
SourcePackage: mountall
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mountall (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug i386 vivid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/1432030

Title:
  improper simultaneity of fscks

Status in mountall package in Ubuntu:
  New

Bug description:
  all fscks are scheduled and run simultaneously.  for those on
  different spindles, that would be great.  for those sharing a spindle,
  this is terribly inefficient.  checking all filesystems on this box
  simultaneously spends nearly a half hour.  when sorted out so that
  simultaneity is only across different spindles, it's done within a few
  minutes.  that's the way it used to be, and still is on other distros.

  i can certainly imagine mountall might be intending to have an
  algorithm that sorts simultaneity by spindles.  if it intends it, it
  doesn't work.

  even if such an algorithm usually worked well, fstab should still be
  interpreted such that if the fsck column specifies values greater than
  2, then the simultaneity specified in fstab should be followed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: mountall 2.54ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic i686
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  Date: Fri Mar 13 14:54:37 2015
  InstallationDate: Installed on 2015-01-16 (56 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Alpha i386 (20150114)
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz ro root=UUID=5116dd42-c618-49a4-885e-84c697b53abd panic=30
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1432030/+subscriptions