Hi Kenneth. On Fri, May 25, 2012 at 10:30:40PM +0800, Kenneth Langga wrote: > NILFS: bad btree node (blocknr=111560943): level = 242, flags = 0x3f, > nchildren = 23369 > NILFS error (device sdc2): nilfs_bmap_lookup_contig: broken bmap > (inode number=19696) > > What is the correct course of action for this type of error? And what > would have caused this?
What struck me is the very high level and the absurt number of number of children. That can't be good. AFAIR NiLFS only has say upto 3 (or 4?) levels in its B-tree. It *could* be failing in rebalancing or more likely pointing to garbage? Cheers, Reinoud -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
