Block corruption

["Andrew Snare" <asnare@allshare.nl>]

Hi,

After a few 2.6.6 oopsen and --rebuild-trees on some filesystems, we've
still got some bad-block errors that are proving troublesome. In
particular, we appear to have 3 bad blocks:

vs-5150: search_by_key: invalid format found in block 5963192. Fsck?
vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to
find stat data of [52570 52653 0x0 SD]
vs-5150: search_by_key: invalid format found in block 5946544. Fsck?
vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to
find stat data of [46770 46771 0x0 SD]
vs-5150: search_by_key: invalid format found in block 10058201. Fsck?
vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to
find stat data of [111684 111687 0x0 SD]

It's a hardware RAID-5 configuration that has no errors, so we know
it's not a hardware problem; this points to corruption in one or more of
our 11 reiserfs filesystems.

Is it possible to:

1) Work out which of the 11 filesystems these errors are referring to?
Preferably while the system is mounted. I see a block number, but
several of our filesystems are large enough to have a block number that
big.
2) Work out which directory/file is corrupted? In the past whenever we
did a --rebuild-tree we ended up with quite a lot of stuff in
lost+found, so we'd like to try and work out where it's coming from if
possible.

Thanks in advance,

 - Andrew Snare