On Aug 15, 2013, at 2:40 PM, Anton Eliasson wrote: [snip] > Hi again. I was able to reproduce the crash on a fully updated system by starting the two virtual machines simultaneously as described in my e-mail from May 25. I made a new attempt to rebuild the kernel with your patches. I selected these options in make menuconfig [1], which resulted in this generated config.x86_64 [2] which has the following diff compared to the stock config.x86_64: > As I remember, you reported about remount file system in RO mode and many "broken bnode" error messages issue, initially. Unfortunately, as I can see, you can't reproduce this issue. I really had hope that you can reproduce this important issue. As I see, shared by you logs with crush contain details about the issue that it was reported also by Jérôme Poulin <jeromepoulin@xxxxxxxxx>. I mean this error message: [ 304.494448] BUG: unable to handle kernel paging request at 00000000000013f6 [ 304.494456] IP: [<ffffffffa1327232>] nilfs_end_page_io+0x12/0xc0 [nilfs2] I can reproduce this issue on my side and this issue is under investigation yet. But anyway... Could you try to reproduce the issue with remounting file system in RO mode? It is really important and annoying issue. > --- config.x86_64 2013-08-11 00:06:09.000000000 +0200 > +++ config.x86_64.last 2013-08-11 12:48:44.094979947 +0200 > @@ -1,6 +1,6 @@ > # > # Automatically generated file; DO NOT EDIT. > -# Linux/x86 3.10.0-1 Kernel Configuration > +# Linux/x86 3.10.5-1 Kernel Configuration > # > CONFIG_64BIT=y > CONFIG_X86_64=y > @@ -5450,6 +5450,11 @@ > # CONFIG_BTRFS_FS_RUN_SANITY_TESTS is not set > # CONFIG_BTRFS_DEBUG is not set > CONFIG_NILFS2_FS=m > +CONFIG_NILFS2_DEBUG=y > +# CONFIG_NILFS2_USE_PR_DEBUG is not set > +CONFIG_NILFS2_DEBUG_SHOW_ERRORS=y > +CONFIG_NILFS2_DEBUG_DUMP_STACK=y > +# CONFIG_NILFS2_DEBUG_SUBSYSTEMS is not set > CONFIG_FS_POSIX_ACL=y > CONFIG_EXPORTFS=y > CONFIG_FILE_LOCKING=y > As I remember, I asked you about enabling more configuration options. I mean such options: CONFIG_NILFS2_DEBUG_BASE_OPERATIONS, CONFIG_NILFS2_DEBUG_MDT_FILES, CONFIG_NILFS2_DEBUG_SEGMENTS_SUBSYSTEM, CONFIG_NILFS2_DEBUG_BLOCK_MAPPING. I suppose that you don't enable these options because it has dependence from "Enable output from subsystem" option. But, anyway, I am afraid that you don't reproduce the issue in the case of these options enabling. But maybe you will be more lucky in such trying. :) Anyway, thank you for your efforts. It will be really great if you will be lucky and will reproduce the issue with remount file system in RO mode and many "broken bnode" error messages. Could you try again? Thanks, Vyacheslav Dubeyko. -- 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
