On Sat, 22 Aug 2009 20:43:16 +0900 (JST), Ryusuke Konishi wrote: > On Sat, 22 Aug 2009 13:36:13 +0300, Yuri Chislov wrote: > > I have update utils to 2.0.14 and kernel to 2.6.30.5 + your patch. > > Is it possible to add some printk to get additional information? > > > > Thank you. > > Yuri. > > Thanks. I will send you an additional patch for analysis later. > > Thanks, > Ryusuke Konishi
Yuri, I will attach a patch to log the latest segment.
If you apply this, you will see messages like:
segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
NILFS: looking segment (seg_start=1382400, seg_end=1384447, segnum=675,
seg_seq=675)
NILFS: found super root: segnum=675, seq=675, pseg_start=1382558,
pseg_offset=174
NILFS: latest checkpoint=26461
Then, you can dump summary of the segment with dumpseg command.
# dumpseg 675
~~~ specify the segnum reported in the log.
# dumpseg 674
# dumpseg 673
..
Could you send me the dump log around the segment?
If you find an entry like:
finfo
ino = 6, cno = xxxxx, nblocks = x, ndatblk = x
vblocknr = yyyyyy, blkoff = 2, blocknr = xxxxxx
~~~~~~~ ~~~~~~~~~~
ino = 6 indicates The root inode is included in this block.
inode metadata file
This writeback is suspicious.
Thanks,
Ryusuke Konishi
0001-nilfs2-insert-some-printks-in-recovery-logic.patch.bz2
Description: Binary data
_______________________________________________ users mailing list [email protected] https://www.nilfs.org/mailman/listinfo/users
