Hi, On Wed, 2012-10-10 at 09:39 +0200, Piotr Szymaniak wrote: > On Wed, Oct 10, 2012 at 01:24:40AM +0900, Ryusuke Konishi wrote: > > > (the card is in a card reader) > > > > > > > Maybe, you will have some troubles with getting of outputs. So, I need in your segment #0 (first 8 MB) raw output for issue analysis beginning, anyway. > > > > > > maszyn ~ # dumpseg /dev/sdf3 0 > /tmp/dumpseg-0.out > > > > > > Attached. > > > > The segment zero may not include any useful information. > > Please try nilfs-tune command to know which segment should be investigated. > > > > # nilfs-tune -l /dev/sdf3 > > ... > > Last checkpoint #: 160345 > > Last block address: 131015 > > Last sequence #: 7675 > > .. > Last checkpoint #: 1873 > Last block address: 734128 > Last sequence #: 358 > > So it seems to be segment #358. > > dump attached. > I need in superblock's content anyway. Currently, I need in raw dumps from two blocks after dump preliminary analysis. Because you have message about root inode corruption then it needs to check the root inode raw representation in ifile (ino = 6). As I can see from your dump that the third block of ifile is located in 734205 block (blkoff = 2, blocknr = 734205). Also I can see that root inode content (ino = 2) is located in 734158 block ( blkoff = 0, blocknr = 734158). Could you share these 2 blocks content? Or you can check that these blocks contains expected metadata info. I expect that some of these blocks doesn't contains valid metadata info. With the best regards, Vyacheslav Dubeyko. > > Piotr Szymaniak. -- 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
