What about modifying ext2_block_map():
* check the results from block_bmap() and inode_bmap() for sanity ( <
sb.s_blocks_count)
* if they are obviously wrong, then dump the inode number, perhaps the
complete data block which containes the bogous value, the file offset
etc.
Or: fsck could dump that.
-- Manfred- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/