On Wed, 27 Apr 2011 09:27:59 +0000 (UTC), Ivan Telichko wrote: > > Is there dumpseg data of the segment 1718 and 1719 ? > > I put them here: http://pastebin.com/8aHrkv7V Thanks, Ivan. > > If the duplicated block exists, it will look like: > > > > finfo > > ino = 97606, cno = 281, nblocks = xx, ndatblk = xx > > ... > > vblocknr = xxxxxxx, blkoff = 14, blocknr = xxxxxxxx > > ... > > > > The first block in segment 1718 looks exactly like this. Is it wrong, > even if segments are different? Yes, it's wrong. Although garbage collection makes such situation transiently during migration of live blocks, one of these segments must be marked invalid on sufile (segment usage file). I'm guessing a retry of writeback or garbage collection failure causes this inconsistent situation. How was the output of lssu command ? > Also, I tried to change mc_nsegments_per_clean to 3 in > nilfs_cleanerd.conf. After that, cleanerd started and worked for > some time, but then died again. Now duplicate blocks were found > in segments 1363 and 1364. No free space was created in the > process. Yes, decreasing mc_nsegments_per_clean may hide the error, but it won't resolve the inconsistency. Thanks, Ryusuke Konishi > --- > > Regards, > Ivan Telichko > > > -- > 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
