karmic e2fsprogs ever going beyond 1.41.9?

Johnny Walker johnnyjboss at gmail.com
Wed Jun 2 21:54:07 UTC 2010


I'm seeing this when I check my ext4 fs:

johnny at mythserver:/% sudo fsck.ext4 -nfv /dev/sda1
e2fsck 1.41.9 (22-Aug-2009)
Warning!  /dev/sda1 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 125 has zero dtime.  Fix? no

Inodes that were part of a corrupted orphan linked list found.  Fix? no

Inode 128 was part of the orphaned inode list.  IGNORED.
Inode 275 was part of the orphaned inode list.  IGNORED.
Inode 284 was part of the orphaned inode list.  IGNORED.
Inode 513 was part of the orphaned inode list.  IGNORED.
Inode 1347 was part of the orphaned inode list.  IGNORED.
Inode 1348 was part of the orphaned inode list.  IGNORED.
Inode 1375 was part of the orphaned inode list.  IGNORED.
Inode 788280 was part of the orphaned inode list.  IGNORED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -(2842670--2842672) -(2842701--2842702)
-(2858558--2858559) -(2858561--285856 -(3219456--3219967)
Fix? no

Free blocks count wrong (25472962, counted=25497576).
Fix? no

Inode bitmap differences:  -125 -128 -275 -284 -513 -(1347--1348) -1375 -788280
Fix? no

Free inodes count wrong (6791568, counted=6798938).
Fix? no


/dev/sda1: ********** WARNING: Filesystem still has errors **********


  237168 inodes used (3.37%)
     362 non-contiguous files (0.2%)
     157 non-contiguous directories (0.1%)
         # of inodes with ind/dind/tind blocks: 0/0/0
         Extent depth histogram: 210629/82/1
 2630739 blocks used (9.36%)
       0 bad blocks
       1 large file

  184947 regular files
   24054 directories
      60 character device files
      26 block device files
       2 fifos
     484 links
   20648 symbolic links (18936 fast symbolic links)
      43 sockets
--------
  230264 files

When I reboot to a Lucid ISO on a thumbdrive to fix this file system
it uses a later version of e2fsprogs and finds no errors. When I use a
Karmic ISO on thumbdrive it uses an earlier version and reports no
errors.

Is this simply a bad revision of e2fsprogs to be using? I see the
release notes show many many bug fixes after this version at
http://e2fsprogs.sourceforge.net/e2fsprogs-release.html

Will a newer version be made available through the main or universe
repository or is there a safe way to compile my own?

-Johnny




More information about the Ubuntu-devel-discuss mailing list