ext3fs problem

<[email protected]> Tue, 30 Sep 2003 23:57:41 +0100 (IST)
Newsgroups gmane.linux.userfs
Message-ID <[email protected]>
Hello,

I hope this is the correct list to post this. I was running a Gentoo
system until 3 days ago on a 2.6.0-test5-mm3 kernel without problems. The
file system was ext3 on a /dev/md0 raid0 partition. It froze without
leaving me a chance back then.
I then restarted the machine and /dev/md0 became unaccessible ... I tried
to recover it using : e2fsck, dumpe2fs and parted but none can fix this
error :
Pass 3 : root inode is not a directory
exiting (signal 11)

Below lies the beginning of the dumpe2fs command chowing the file system
info, i've tried everything to mount, fix this partition but cannot
believe it is just gone, i would be grateful if anyone could have a useful
suggestion about this.
dumpe2fs /dev/md0 :

Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          cd5ef7e6-78a7-495c-8ea3-bf1c4482543f
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      dir_index filetype sparse_super
Default mount options:    (none)
Filesystem state:         clean with errors
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              11534336
Block count:              23038480
Reserved block count:     1151924
Free blocks:              22676526
Free inodes:              11534336
First block:              0
Block size:               4096
Fragment size:            4096
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         16384
Inode blocks per group:   512

Thanks,
Steph
-- 
Sent from Linux Debian Woody 3.0 using a VIA C3
http://frlinux.net - [email protected]
http://www.gentoofr.org - Portail Francophone Gentoo


-
To unsubscribe from this list: send the line "unsubscribe linux-userfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html