Hi, There was three bad btree nodes: Dec 20 16:12:08 yf237 kernel: NILFS: bad btree node (blocknr=710153406): level = 0, flags = 0x2, nchildren = 25088 Dec 20 16:12:08 yf237 kernel: NILFS error (device sdb2): nilfs_bmap_last_key: broken bmap (inode number=321775) -- Dec 21 10:10:07 yf237 kernel: NILFS: bad btree node (blocknr=711343917): level = 199, flags = 0x60, nchildren = 16670 Dec 21 10:10:07 yf237 kernel: NILFS error (device sdb2): nilfs_bmap_last_key: broken bmap (inode number=324685) -- Dec 21 10:13:41 yf237 kernel: NILFS: bad btree node (blocknr=14167806): level = 0, flags = 0x0, nchildren = 0 Dec 21 10:13:41 yf237 kernel: NILFS error (device sdb2): nilfs_bmap_last_key: broken bmap (inode number=253710) I have not found new bad btree nodes in recent days. But the MyISAM tables still often be crashed and soon be ok without repairing. 在 2012-12-28，14:06，Vyacheslav Dubeyko <slava@xxxxxxxxxxx> 写道： > Hi, > > On Thu, 2012-12-27 at 17:47 +0800, Elmer Zhang wrote: >> Hi konishi ryusuke, >> >> I am trying to use NILFS2 to make MySQL cold backup, but the MySQL tables often be crashed. It seems there is some problems with nilfs filesystem. >> > > As I remember, you reported initially the error message about issue with > (inode number=321775) and (blocknr=710153406). If you have new MySQL > tables' crashes then it means that you have new NILFS error messages in > your syslog. Do you have error messages about new inode numbers and > block numbers or about the same? > > With the best regards, > Vyacheslav Dubeyko. > >> I have described how I use nilfs in this mail: http://www.mail-archive.com/linux-nilfs@xxxxxxxxxxxxxxx/msg01481.html >> >> Can I know which version of nilfs do you use, and what do you use nilfs for? >> >> Thanks, >> Elmer Zhang-- >> 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 > > -- 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
