[ ... ] > Apr 24 06:55:22 nixos kernel: NILFS (dm-0): bad btree node (ino=1609, blocknr=13626216): level = 51, flags = 0x44, nchildren = 12298 > Apr 24 06:55:22 nixos kernel: NILFS error (device dm-0): nilfs_bmap_lookup_contig: broken bmap (inode number=1609) > Apr 24 06:55:22 nixos kernel: Remounting filesystem read-only The standard NILFS2 recovery is to mount an earlier checkpoint. This to be done quickly to ensure they don't get deleted by the cleaner, but then if the system does not start it should not start either. Usually corruption like this is because of the storage system not implementing correctly barriers, and that might related to the use of DM (some versions lack that implementation). If barriers do work the previous checkpoint to the faulty one should always be correct, because it has been checkpointed. Otherwise there is a a known bug that apparently is triggered easily only by very high concurrent load, as it involves a race condition: http://marc.info/?l=linux-nilfs&m=149992828611084&w=2 -- 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
