On Sat, 22 Aug 2009 17:36:42 +0300, Yuri Chislov wrote:
> On Saturday 22 August 2009 15:34:38 Ryusuke Konishi wrote:
> > 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
> Hi, 
> 
> Attached file with dumpseg output.
> It's look, that root inode in  segnum=10938.
> 
> Thank you.
> Yuri.

The segment in the attached log did not include the root inode.
( The entry with ino = 6, did not include the block with blkoff = 2 )

What will happen if you run the attached script?

 $ chmod +x find-root.sh
 $ sudo ./find-root.sh <device> 10938 | tee -a segment-with-root-inode.log

Thanks,
Ryusuke Konishi
#!/bin/bash

cmd=`basename $0`

function die() { echo "$1" 1>&2; exit 1; }

test -n "$1" -a -n "$2" -a -b "$1" || die "usage: $cmd <device> <segnum>"

dev=$1

for (( i=$2; i >= 0; i-- )); do
    if dumpseg $dev $i | sed -ne '/ino = 6/,/finfo/{p}' | grep -q "blkoff = 
2,";  then
        echo "$cmd: root inode found in segnum=$i"
        dumpseg $dev $i
        exit 0
    fi
done

die "$cmd: root inode not found"

_______________________________________________
users mailing list
[email protected]
https://www.nilfs.org/mailman/listinfo/users

Reply via email to