EXT3-fs error (device md2): ext3_journal_start_sb: Detected aborted journal...
adilger at clusterfs.com
Tue Nov 8 17:31:50 UTC 2005
On Nov 08, 2005 16:14 +0100, Brice Figureau wrote:
> Restarting e2fsck from the beginning...
> Pass 1: Checking inodes, blocks, and sizes
> Inode 8 has illegal block(s). Clear<y>?
> and loops forever.
> I know inode 8 is the journal inode.
> What can I do to remotely repair this root filesystem (as the server is
> in a datacenter from which I'm far at the moment), and remount it rw ?
Running 'debugfs -w -R "feature ^has_journal,^needs_recovery" /dev/md2'
should remove the journal from the filesystem, and then your e2fsck
may work. Don't forget to add it back afterward "tune2fs -j /dev/md2".
Principal Software Engineer
Cluster File Systems, Inc.
More information about the Ext3-users