I would like to be able to break our ext4 file system (specifically corrupt the journal) to be sure that we can automatically notice the problem and attempt an autonomous fix. dumpe2fs tells me the inode, but not, that I can see, the blocks where the journal exists (for "dd"ing junk to it). Is there any debug tool that would let me deliberately break the file system (at least, trash the journal)? If not, is there a hint for figuring out the block(s) of the journal so I can stomp it? The kernel is in an embedded machine, so it's a little old 2.6.32.11 and e2fsprogs/libs 1.41.12-2 (Lenny) Dan Taylor Sr. Staff Engineer WD Branded Products 949.672.7761 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
