[ ... ] >> Jun 28 15:57:08 c1-df kernel: [ 1637.138168] NILFS (sdd1): bad btree node (ino=6069196, blocknr=446552325): level = 69, flags = 0x24, nchildren = 8203 >> Jun 28 15:57:08 c1-df kernel: [ 1637.139363] NILFS error (device sdd1): nilfs_bmap_lookup_contig: broken bmap (inode number=6069196) [ ... ] >> How can I fix this? > Mount earlier checkpoints until you find a "clean" one, then > delete later "unclean" checkpoints. If there is no earlier > "clean" checkpoint, some IO error has damaged existing data. Further words of caution: the errors above can be merely inconsistencies in very recent metadata due to a crash, or they can be the result of some IO error damaging existing data. In the latter case we know for sure that some NILFS2 metadata has been corrupted, but we don't know whether some _data_ inside existing files has been corrupted too, as NILFS2 does not do consistency checks for data/payload. As the documentation says, it actually checksums each "block", but currently this is used only to detect incomplete metadata after a crash, and no verification of the checksum is made for data. -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
