Whenever fsck is cancelled by user, this error message is given:
"fsck.ext4: Inode bitmap not loaded while setting block group checksum info"
And the exit status of fsck is 8
(This leads to plymouth/mountall reporting "Serious errors" on the filesystem in question when fsck is cancelled during boot, and acting accordingly.)
TEST CASE
$ sudo fsck -f /dev/sda1
[Ctrl+C]
*error is reported
!error should not be reported(?)
Binary package hint: e2fsprogs
"Parents": Bug #571707 and Bug #577331
PROBLEM
Whenever fsck is cancelled by user, this error message is given:
"fsck.ext4: Inode bitmap not loaded while setting block group checksum info"
And the exit status of fsck is 8
(This leads to plymouth/mountall reporting "Serious errors" on the filesystem in question when fsck is cancelled during boot, and acting accordingly.)
TEST CASE
$ sudo fsck -f /dev/sda1
[Ctrl+C]
*error is reported
!error should not be reported(?)
OBSERVATIONS
Seen on both lucid and maverick in virtualbox, and confirmed by Benjamin Kay on lucid non-virtual ( https:/ /bugs.edge. launchpad. net/ubuntu/ lucid/+ source/ mountall/ +bug/577331/ comments/ 21 )
ProblemType: Bug ature: Ubuntu 2.6.34-2.9-generic 2.6.34-rc7
DistroRelease: Ubuntu 10.10
Package: e2fsprogs 1.41.11-1ubuntu2
ProcVersionSign
Uname: Linux 2.6.34-2-generic i686
Architecture: i386
Date: Tue May 18 02:24:53 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
LANG=en_GB.utf8
SHELL=/bin/bash
SourcePackage: e2fsprogs