Hi, On Thu, 2012-12-20 at 10:46 +0800, 张 磊 wrote: > Hello. > My nilfs suddenly become read-only. I saw these logs in /var/log/messages: > > Dec 19 11:20:05 localhost kernel: NILFS: bad btree node (blocknr=710153406): level = 0, flags = 0x2, nchildren = 25088 > Dec 19 11:20:05 localhost kernel: NILFS error (device sdb2): nilfs_bmap_lookup_contig: broken bmap (inode number=321775) > Dec 19 11:20:05 localhost kernel: > Dec 19 11:20:05 localhost kernel: Remounting filesystem read-only > Dec 19 11:20:05 localhost kernel: NILFS: bad btree node (blocknr=710153406): level = 0, flags = 0x2, nchildren = 25088 > Dec 19 11:20:05 localhost kernel: NILFS error (device sdb2): nilfs_bmap_lookup_contig: broken bmap (inode number=321775) > Dec 19 11:20:05 localhost kernel: > Dec 19 11:20:05 localhost kernel: NILFS: bad btree node (blocknr=710153406): level = 0, flags = 0x2, nchildren = 25088 > Dec 19 11:20:05 localhost kernel: NILFS error (device sdb2): nilfs_bmap_lookup_contig: broken bmap (inode number=321775) > Dec 19 11:20:05 localhost kernel: > Dec 19 11:20:05 localhost kernel: NILFS: bad btree node (blocknr=710153406): level = 0, flags = 0x2, nchildren = 25088 > Dec 19 11:20:05 localhost kernel: NILFS error (device sdb2): nilfs_bmap_lookup_contig: broken bmap (inode number=321775) > Dec 19 11:20:05 localhost kernel: > …………………………………………………… > > How can I fix this? There is 6TiB data on my disk, I don't want to format the disk. > I found that a lot of people have encountered the same problem. Is this a bug of nilfs? How can I avoid this problem? When it happens, I was running multiple MySQL and rsync, and nilfs_cleanerd was cleaning segments. > Yes, this issue was reported earlier. As I understand, you can simply remount your filesystem in read-write mode and to continue using your NILFS2 filesystem. If you will encounter any troubles with remounting, please, report about it. With the best regards, Vyacheslav Dubeyko. > 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
