Yay! It happened again! [397113.459309] EXT4-fs error (device md0): ext4_iget:3821: inode #100691970: comm updatedb.mlocat: checksum invalid [397113.459315] Aborting journal on device md0-8. [397113.496222] EXT4-fs (md0): Remounting filesystem read-only However, trying to preserve the evidence runs into a problem: /root# e2image -Q /dev/md0 md0.qcow2 e2image 1.43-WIP (1-Aug-2012) e2image: Inode checksum does not match inode while getting next inode /root# ls -l md0.qcow2 -rw------- 1 root root 0 Aug 8 18:30 md0.qcow2 e2image aborts on the checksum error, preventing me from capturing a useful image. Can someone find a workaround QUICKLY? I can't keep this FS read-only for long. Thanks! -- 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
