Re: Kernel Bug after corrupted filesystem

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

Hi,
On Wed, 31 Dec 2008 12:17:07 +0100, "Dennis Peiler" wrote:
> > Again, it seems that a btree corruption happened.
> > Sorry, but it's hard to track the cause directly from the stack dump.
> > 
> Is there anything else I could provide? That might help to track
> down problems

Thanks.
Well, could you try to get some information with a debug build module?

First, pull the latest code from our git repository.

The debug build module can be built by commenting out the following
line of the fs/Makefile.

   #CONFIG_NILFS_DEBUG=y

Then, set debug levels before mounting as follows:

  # modprobe nilfs2
  # echo "-vvv fs -vvv recovery -vvv mdt -vvv btnode -vv dat" > /proc/fs/nilfs2/debug_option
  # mount -t nilfs2 /dev/xxx /test

This will log some more information in syslog including
block addresses.
What I'd like to see next is content of key disk blocks, but first
we need to know rough situation.

Regards,
Ryusuke