Hi,
hoping that someone on this list can help me here is the Problem.
After a crash it seems the journal could not be recovered.
This is what mount gives:
root@wuehlkiste:# mount -t ext3 /dev/hdb2 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/hdb2,
or too many mounted file systems
and this is the corresponding logfile-entry:
Nov 27 11:16:13 wuehlkiste kernel: attempt to access beyond end of device
Nov 27 11:16:13 wuehlkiste kernel: 03:42: rw=0, want=66849792, limit=2498107
Nov 27 11:16:13 wuehlkiste kernel: JBD: IO error reading journal superblock
Nov 27 11:16:13 wuehlkiste kernel: EXT3-fs: error loading journal.
fsck failed as well:
root@wuehlkiste:# fsck -f /dev/hdb2
fsck 1.27 (8-Mar-2002)
e2fsck 1.27 (8-Mar-2002)
/dev/hdb2: Invalid argument while reading block 16712447
/dev/hdb2: Invalid argument reading journal superblock
fsck.ext2: Invalid argument while checking ext3 journal for /dev/hdb2
AT last here's what tune2fs -l gives:
root@wuehlkiste:# tune2fs -l /dev/hdb2
tune2fs 1.27 (8-Mar-2002)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 60ae4fae-f11b-4156-ade8-1aa1b63d3bc5
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype needs_recovery sparse_super
Filesystem state: clean with errors
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 262144
Block count: 524112
Reserved block count: 26205
Free blocks: 185025
Free inodes: 242316
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
Last mount time: Mon Nov 25 12:40:35 2002
Last write time: Mon Nov 25 13:49:25 2002
Mount count: 16
Maximum mount count: -1
Last checked: Sun Nov 17 18:40:27 2002
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal UUID: <none>
Journal inode: 8
Journal device: 0x0000
First orphan inode: 0
Even clearing the has_journal and needs_recovery flags produced the same
output using fsck as above.
Running e2salvage on this backup-partition (/dev/hdb1 is the 'real'
partition, /dev/hdb2 was written using dd) didn't help much as well.
Hoping for some suggestions how to safe my data, since last backup was two
month old :-(
Regards
--
Stephan Wiehr
http://www.asta.uni-sb.de/~lynx/
"Always remember: You're unique,
just like everyone else."
_______________________________________________
Ext3-users@redhat.com
https://listman.redhat.com/mailman/listinfo/ext3-users
