[Bug 941813] [NEW] allow verbose fsck via friendly-recovery

[James Hunt]

Public bug reported:

One of the options in the friendly-recovery menu is "Check all file
systems" (aka fsck). However, selecting this option runs fsck via
mountall which produces no output. This could give users the impression
that their system has actually frozen (this feeling is compounded by the
fact that when fsck runs, you cannot for example toggle the caps-lock
light).

Either friendly-recovery or mountall need to be modified to pass '-VC'
to fsck such that the user is provided with feedback on progress.

I have made a change to mountall to allow for verbose fsck:

lp:~jamesodhunt/ubuntu/precise/mountall/add-verbose-fsck-option

This tests fine on ext3/ext4, but since mountall is passing '-C' to
/sbin/fsck and /sbin/fsck then invokes the relevant FS-specific fsck
(such as /sbin/fsck.ext4), care should be taken in testing this as the
fsck(8) states...

       -C [  fd  ]
              Display completion/progress bars for those filesystem checkers (currently only for ext2 and ext3) which support them.

What is *not* clear is what happens if you pass '-C' to an FS-specific
fsck that does not support '-C'. So, we need to test all fscks:

$  apt-file search /sbin/fsck\.
btrfs-tools: /sbin/fsck.btrfs
dosfstools: /sbin/fsck.msdos
dosfstools: /sbin/fsck.vfat
e2fsprogs: /sbin/fsck.ext2
e2fsprogs: /sbin/fsck.ext3
e2fsprogs: /sbin/fsck.ext4
e2fsprogs: /sbin/fsck.ext4dev
gfs2-utils: /sbin/fsck.gfs2
hfsprogs: /sbin/fsck.hfs
hfsprogs: /sbin/fsck.hfsplus
initscripts: /sbin/fsck.nfs
jfsutils: /sbin/fsck.jfs
ocfs2-tools: /sbin/fsck.ocfs2
reiser4progs: /sbin/fsck.reiser4
reiserfsprogs: /sbin/fsck.reiserfs
ufsutils: /sbin/fsck.ufs
util-linux: /sbin/fsck.cramfs
util-linux: /sbin/fsck.minix
vmfs-tools: /usr/sbin/fsck.vmfs
xfsprogs: /sbin/fsck.xfs

Easiest way to do this would be to install all the packages above, dd a
file, format it for each FS in turn, then run 'fsck.<FS> -VC" on each
file/disk.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: friendly-recovery 0.2.24
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6
Uname: Linux 3.2.0-16-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.93-0ubuntu2
Architecture: i386
Date: Mon Feb 27 08:51:45 2012
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: friendly-recovery
UpgradeStatus: Upgraded to precise on 2012-01-12 (45 days ago)

** Affects: friendly-recovery (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug i386 precise

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to friendly-recovery in Ubuntu.
https://bugs.launchpad.net/bugs/941813

Title:
  allow verbose fsck via friendly-recovery

Status in “friendly-recovery” package in Ubuntu:
  New

Bug description:
  One of the options in the friendly-recovery menu is "Check all file
  systems" (aka fsck). However, selecting this option runs fsck via
  mountall which produces no output. This could give users the
  impression that their system has actually frozen (this feeling is
  compounded by the fact that when fsck runs, you cannot for example
  toggle the caps-lock light).

  Either friendly-recovery or mountall need to be modified to pass '-VC'
  to fsck such that the user is provided with feedback on progress.

  I have made a change to mountall to allow for verbose fsck:

  lp:~jamesodhunt/ubuntu/precise/mountall/add-verbose-fsck-option

  This tests fine on ext3/ext4, but since mountall is passing '-C' to
  /sbin/fsck and /sbin/fsck then invokes the relevant FS-specific fsck
  (such as /sbin/fsck.ext4), care should be taken in testing this as the
  fsck(8) states...

         -C [  fd  ]
                Display completion/progress bars for those filesystem checkers (currently only for ext2 and ext3) which support them.

  What is *not* clear is what happens if you pass '-C' to an FS-specific
  fsck that does not support '-C'. So, we need to test all fscks:

  $  apt-file search /sbin/fsck\.
  btrfs-tools: /sbin/fsck.btrfs
  dosfstools: /sbin/fsck.msdos
  dosfstools: /sbin/fsck.vfat
  e2fsprogs: /sbin/fsck.ext2
  e2fsprogs: /sbin/fsck.ext3
  e2fsprogs: /sbin/fsck.ext4
  e2fsprogs: /sbin/fsck.ext4dev
  gfs2-utils: /sbin/fsck.gfs2
  hfsprogs: /sbin/fsck.hfs
  hfsprogs: /sbin/fsck.hfsplus
  initscripts: /sbin/fsck.nfs
  jfsutils: /sbin/fsck.jfs
  ocfs2-tools: /sbin/fsck.ocfs2
  reiser4progs: /sbin/fsck.reiser4
  reiserfsprogs: /sbin/fsck.reiserfs
  ufsutils: /sbin/fsck.ufs
  util-linux: /sbin/fsck.cramfs
  util-linux: /sbin/fsck.minix
  vmfs-tools: /usr/sbin/fsck.vmfs
  xfsprogs: /sbin/fsck.xfs

  Easiest way to do this would be to install all the packages above, dd
  a file, format it for each FS in turn, then run 'fsck.<FS> -VC" on
  each file/disk.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: friendly-recovery 0.2.24
  ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6
  Uname: Linux 3.2.0-16-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.93-0ubuntu2
  Architecture: i386
  Date: Mon Feb 27 08:51:45 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: friendly-recovery
  UpgradeStatus: Upgraded to precise on 2012-01-12 (45 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/941813/+subscriptions