Re: NILFS: corrupt root inode after Turbo Mode?

[Piotr Szymaniak <szarpaj-TbOm9Ca2r9GrDJvtcaxF/A@public.gmane.org>]

[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]

On Thu, Oct 11, 2012 at 10:50:58AM +0400, Vyacheslav Dubeyko wrote:
> On Thu, 2012-10-11 at 00:03 +0200, Piotr Szymaniak wrote:
> > On Wed, Oct 10, 2012 at 04:03:13PM +0400, Vyacheslav Dubeyko wrote:
> > > 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.
> > 
> > How should i make the dump?
> > 
> 
> You can use dd for dumping (dd if=/dev/<device> of=<file> bs=<block size> skip=<offset to the block> count=<blocks count>).

So I should dump block 743205 and 734158? Ok, but I'm not familiar with
blkoff.

ie. blkoff = 2, blocknr = 734205 it means the dump should be block
734205 and (blkoff = 2) next two blocks? If this is correct then this
should work, right?
dd if=/dev/<device> of=<dump> bs=2048 skip=734205 count=3 (not sure if
dd counts skip= and count= from 0 or 1)
And similar with block 734158 but only one block (blkoff = 0)?


Piotr Szymaniak.
-- 
Oczywiscie wiedzial,  ze byla wojna - nie ta obecna,  glupia,  w ktorej
Amerykanie  dostawali  lomot od bandy zoltkow w czarnych pizamach - ale
druga wojna swiatowa.
  -- Stephen King, "Apt Pupil"

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]