> I have a 8TG nilfs2 disk with started changing to read-only by itself. Highly unlikely. > My log files are full of the following error messages: > 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) These are typical of some IO error, even a transient one, or more simply the outcome of a crash with not well implemented barriers. I notice that the errors happen with a time offset of "1637" seconds, that is less than 30 minutes after a reboot. > I have already checked and there are not errors on the disk. How did you check? > 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. -- 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
