Re: Fail to mount NILFS.

[Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>]

[-- Attachment #1: Type: Text/Plain, Size: 1375 bytes --]

Hi,
On Sun, 23 Aug 2009 07:55:02 +0300, Yuri Chislov wrote:
> On Sunday 23 August 2009 06:23:22 Ryusuke Konishi wrote:
> > If the new script find the blocks storing the root inode, it will also
> > dump them to files like:
> >
> > ifile-2-seg649-1329203
> > ifile-2-seg649-1329259
> > ifile-2-seg649-1329315
> > ifile-2-seg649-1329372
> > ifile-2-seg649-1329428
> > ifile-2-seg649-1329455
> >
> > Then, we can see if the root inode is actually broken or not.
> Hi,
> 
>  There is output from script.
> sudo ./find_root.sh /dev/cciss/c0d1p1 10938 | tee -a segment-with-root-
> inode.log
> find_root.sh: root inode not found
> 
> Thanks.
> Yuri.

Thank you for following this analysis.

It reached the beginning of the partition.

What will happen if you start the script from the last segment number?

The last segment number is calculated from the block count which
appears in /proc/partitions:

 $ cat /proc/partitions
major minor  #blocks  name

   8       16   71687325 sdb
   8       17   35840983 sdb1
   8       18   35841015 sdb2

 $ expr 35840983 / 4 / 2048 - 1
 4374
 $ sudo ./find-root.sh /dev/sdb1 4374


And, the attached patch will output some information about how disk
block numbers are converted with DAT file.

I think this will give another hint on which metadata broke in nilfs.

Could you apply it and try mount again?

Thanks in advance,
Ryusuke Konishi

[-- Attachment #2: 0001-nilfs2-add-debug-messages-on-bmap-lookup-and-dat-tra.patch.bz2 --]
[-- Type: Application/Octet-Stream, Size: 1143 bytes --]

[-- Attachment #3: Type: text/plain, Size: 158 bytes --]

_______________________________________________
users mailing list
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
https://www.nilfs.org/mailman/listinfo/users