On Sep 28, 2002 01:47 +1000, Martial Herbaut wrote: > Following a raid controller crash I am getting this error when attempting > to fsck > > ----------- > /sbin/fsck.ext3 -f /dev/customer_data_volume_group/customer_data_volume > e2fsck 1.26 (3-Feb-2002) > /sbin/fsck.ext3: Attempt to read block from filesystem resulted in short > read while checking ext3 journal > e2fsck: io manager magic bad! > ------------ The "io manager magic bad" message is just a symptom of the first error (which is an I/O error), and has been fixed in more recent e2fsck versions. > mounting the partition and doing an ls in the root of that partition > resulting in the following errors: > > --------------- > EXT3-fs error (device lvm(58,0)): ext3_readdir: directory #2 contains a > hole at offset 0 > I/O error: dev 08:21, sector 3211 > I/O error: dev 08:21, sector 9805371 > EXT3-fs error (device lvm(58,0)): ext3_readdir: directory #2 contains a > hole at offset 4096 > I/O error: dev 08:21, sector 3211 > I/O error: dev 08:21, sector 9805419 > EXT3-fs error (device lvm(58,0)): ext3_readdir: directory #2 contains a > hole at offset 8192 > I/O error: dev 08:21, sector 3211 > I/O error: dev 08:21, sector 9806083 This means your disk is dead, not much you can do about that, except get a new disk and restore from the backup. Directory #2 is the root directory, and none of it can be read. Cheers, Andreas -- Andreas Dilger http://www-mddsp.enel.ucalgary.ca/People/adilger/ http://sourceforge.net/projects/ext2resize/ _______________________________________________ Ext3-users@redhat.com https://listman.redhat.com/mailman/listinfo/ext3-users
