Help - need to fix blorked up ext3 filesystem

[batavus]

I have a pair of IDE disks that I've combined with Linux volume manager into a single logical volume. On top of that I had an ext2 filesystem under Fedora Core 2. After I was hacked by a script kiddie (dumb me didn't patch sshd), I installed Fedora Core 4 and it brought in the volume group, logical volumes, and ext2 filesystem. All was hunky doory. I added an ext3 journal to it later, again hunky doory for many months. Now all of a sudden it starts blowing chunks. Here's what I have from 'dmesg'

EXT3-fs warning (device dm-2): ext3_clear_journal_err: Filesystem error recorded
from previous mount: IO failure
EXT3-fs warning (device dm-2): ext3_clear_journal_err: Marking fs in need of fil
esystem check.
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
EXT3 FS on dm-2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev dm-2, type ext3), uses xattr
kjournald starting. Commit interval 5 seconds
EXT3-fs warning (device dm-2): ext3_clear_journal_err: Filesystem error recorded
from previous mount: IO failure
EXT3-fs warning (device dm-2): ext3_clear_journal_err: Marking fs in need of fil
esystem check.
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
EXT3 FS on dm-2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev dm-2, type ext3), uses xattr
usb 1-2: USB disconnect, address 3
EXT3-fs error (device dm-2): ext3_free_blocks_sb: bit already cleared for block
3334151
Aborting journal on device dm-2.
ext3_abort called.
EXT3-fs error (device dm-2): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device dm-2) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device dm-2) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device dm-2) in ext3_orphan_del: Journal has aborted
EXT3-fs: unsupported inode size: 0


Here's fsck results:

[root@dalan ~]# fsck -V /dev/mapper/bigvg-biglv
fsck 1.37 (21-Mar-2005)
[/sbin/fsck.ext3 (1) -- /dev/mapper/bigvg-biglv] fsck.ext3 /dev/mapper/bigvg-biglv
e2fsck 1.37 (21-Mar-2005)
Warning... fsck.ext3 for device /dev/mapper/bigvg-biglv exited with signal 8.


Trying an ext2 against it:

[root@dalan ~]# e2fsck /dev/mapper/bigvg-biglv
e2fsck 1.37 (21-Mar-2005)
Floating point exception


Anyone have any suggestions? I have most of the data backed up, but there are several files that I'd rather not lose, so if it is possible to extract them, performing the (risky) work to attempt it would be worth it.

Thanks!

---
Batavus