Re: ext3 filesystem not working with raid5

From: Mario Thomas (mario_at_alamar.net)
Date: 12/30/03 

Date: 30 Dec 2003 04:00:03 -0800

Further information. I've run debugfs /dev/sdb1 which provided me with
full stats on the filesystem. I was able to navigate around the
filesystem and see the files that i thought i'd lost - good start i
thought. I also noticed that the needs_recovery flag was set.

When I ran e2fsck /dev/sdb1 the output was as follows:

e2fsck 1.32 (09-Nov-2002)
/dev/sdb1: recovering journal
/dev/sdb1: Attempt to read block from filesystem resulted in short
read while re
ading block 2072

JBD: Failed to read block at offset 1505
e2fsck: No such device or address while trying to re-open /dev/sdb1
e2fsck: io manager magic bad!

Could the problem be that the journal is corrupt? If so, how do i
remove it - bearing in mind the needs_recovery flag is set.

In the end there are about 20 files i need off the filesystem - is
there any way of copying them off using debugfs - if that can see the
filesystem why can't other things like mount?

Thanks again in advance,

Mario

Relevant Pages

  • Re: EXT3-fs error
    ... You can run debugfs on the mounted filesystem and give the command: ... the *only* filesystem corruption, it's not likely that it will cause ... perfectly good airplane --- but there is risk involved. ...
    (Linux-Kernel)
  • Re: unable to recover ext3 - please help
    ... >>backup superblock, so running journal anyway. ... particular tool: debugfs. ... whether filesystem is marked 'clean' or 'not clean'. ...
    (comp.os.linux.misc)
  • Re: Extremely large file on small disk
    ... since e2fsck may not recover everything. ... Another option is to read the man page for debugfs about 3 or 4 times, ... then run debugfs on the filesystem and see what you can recover. ...
    (comp.os.linux.hardware)
  • recovering deleted files on ext3fs
    ... disk and started debugfs on the filesystem with the missing files (ext3) ...
    (comp.os.linux.misc)
  • Re: Change filesystem from read-only mode read-write mode
    ... After exiting ... > from debugfs, the filesystem is still in read-only mode. ...
    (Fedora)