Package: initscripts Version: 2.86-ds1-34 The check (fsck) of OCFS2 file systems fails during startup messages (the complete "checkfs" file is enclosed in this mail) : -------------------------------------------------------------------- Log of fsck -C -V -R -A -a Wed Nov 8 19:49:15 2006
fsck 1.40-WIP (02-Oct-2006) Checking all file systems. [/sbin/fsck.ext2 (1) -- /boot] fsck.ext2 -a -C0 /dev/sda1 /boot was not cleanly unmounted, check forced. /boot: 59/48192 files (25.4% non-contiguous), 37746/96358 blocks [/sbin/fsck.ext3 (1) -- /disk2] fsck.ext3 -a -C0 /dev/sdb3 /dev/sdb3: recovering journal /dev/sdb3: clean, 60069/4235328 files, 6076932/8454144 blocks [/sbin/fsck.ocfs2 (1) -- /ext/d5] fsck.ocfs2 -a /dev/sdc1 [/sbin/fsck.ocfs2 (2) -- /ext/d3] fsck.ocfs2 -a /dev/sdd1 [/sbin/fsck.ocfs2 (3) -- /ext/d4] fsck.ocfs2 -a /dev/sde1 fsck.ocfs2: invalid option -- a Usage: fsck.ocfs2 [ -fGnuvVy ] [ -b superblock block ] [ -B block size ] device Critical flags for emergency repair: -n Check but don't change the file system -y Answer 'yes' to all repair questions -f Force checking even if file system is clean -F Ignore cluster locking (dangerous!) Less critical flags: -b superblock Treat given block as the super block -B blocksize Force the given block size -G Ask to fix mismatched inode generations -u Access the device with buffering -V Output fsck.ocfs2's version -v Provide verbose debugging output -------------------------------------------------------------------------- After a "Ctrl+d" all is OK and the machine starts ... gracefully. Regards JP Pozzi
Log of fsck -C -V -R -A -a Wed Nov 8 19:49:15 2006 fsck 1.40-WIP (02-Oct-2006) Checking all file systems. [/sbin/fsck.ext2 (1) -- /boot] fsck.ext2 -a -C0 /dev/sda1 /boot was not cleanly unmounted, check forced. /boot: 59/48192 files (25.4% non-contiguous), 37746/96358 blocks [/sbin/fsck.ext3 (1) -- /disk2] fsck.ext3 -a -C0 /dev/sdb3 /dev/sdb3: recovering journal /dev/sdb3: clean, 60069/4235328 files, 6076932/8454144 blocks [/sbin/fsck.ocfs2 (1) -- /ext/d5] fsck.ocfs2 -a /dev/sdc1 [/sbin/fsck.ocfs2 (2) -- /ext/d3] fsck.ocfs2 -a /dev/sdd1 [/sbin/fsck.ocfs2 (3) -- /ext/d4] fsck.ocfs2 -a /dev/sde1 fsck.ocfs2: invalid option -- a Usage: fsck.ocfs2 [ -fGnuvVy ] [ -b superblock block ] [ -B block size ] device Critical flags for emergency repair: -n Check but don't change the file system -y Answer 'yes' to all repair questions -f Force checking even if file system is clean -F Ignore cluster locking (dangerous!) Less critical flags: -b superblock Treat given block as the super block -B blocksize Force the given block size -G Ask to fix mismatched inode generations -u Access the device with buffering -V Output fsck.ocfs2's version -v Provide verbose debugging output fsck.ocfs2: invalid option -- a Usage: fsck.ocfs2 [ -fGnuvVy ] [ -b superblock block ] [ -B block size ] device Critical flags for emergency repair: -n Check but don't change the file system -y Answer 'yes' to all repair questions -f Force checking even if file system is clean -F Ignore cluster locking (dangerous!) Less critical flags: -b superblock Treat given block as the super block -B blocksize Force the given block size -G Ask to fix mismatched inode generations -u Access the device with buffering -V Output fsck.ocfs2's version -v Provide verbose debugging output fsck.ocfs2: invalid option -- a Usage: fsck.ocfs2 [ -fGnuvVy ] [ -b superblock block ] [ -B block size ] device Critical flags for emergency repair: -n Check but don't change the file system -y Answer 'yes' to all repair questions -f Force checking even if file system is clean -F Ignore cluster locking (dangerous!) Less critical flags: -b superblock Treat given block as the super block -B blocksize Force the given block size -G Ask to fix mismatched inode generations -u Access the device with buffering -V Output fsck.ocfs2's version -v Provide verbose debugging output fsck died with exit status 17 Wed Nov 8 19:49:17 2006 ----------------