From: Ivan Shapovalov <intelfx100@gmail.com>
To: "Dušan Čolić" <dusanc@gmail.com>
Cc: reiserfs-devel <reiserfs-devel@vger.kernel.org>
Subject: Re: R4 problem started with 2.6.39 and still there with 3.6.6
Date: Sun, 09 Dec 2012 16:36:55 +0400 [thread overview]
Message-ID: <1617029.ijnoNpQuXu@intelfx-laptop> (raw)
In-Reply-To: <CADW=+3n+rKECWNSmzcMeTQaPZrtA3Sr04=yO1cqsd0j09Y43Ww@mail.gmail.com>
On 07 December 2012 18:56:26 Dušan Čolić wrote:
> Hello
>
> I'm using KVM for windows emulation and I have a ~3GB image file that
> I run it from.
> I started having problems with it lately on regular and ccreg40
> partitions (I tried same file on both) using 3.6.6.
> Spammed output with a lot of these:
>
> Dec 7 03:30:02 krshina3 kernel: [15135.133047] reiser4[find(5806)]:
> parse_node40 (fs/reiser4/plugin/node/node40.c:672)[nikita-494]:
> Dec 7 03:30:02 krshina3 kernel: [15135.133047] WARNING: Wrong level
> found in node: 2 != 1
> Dec 7 03:30:02 krshina3 kernel: [15135.133048] reiser4[find(5806)]:
> key_warning (fs/reiser4/plugin/file_plugin_common.c:512)[nikita-717]:
> Dec 7 03:30:02 krshina3 kernel: [15135.133048] WARNING: Error for
> inode 17802378 (-5)
> Dec 7 03:30:02 krshina3 kernel: [15135.133056] reiser4[find(5806)]:
> parse_node40 (fs/reiser4/plugin/node/node40.c:672)[nikita-494]:
> Dec 7 03:30:02 krshina3 kernel: [15135.133056] WARNING: Wrong level
> found in node: 2 != 1
>
>
> Dec 7 17:26:23 krshina3 kernel: [38539.089191] reiser4[gdm(2676)]:
> cbk_level_lookup (fs/reiser4/search.c:963)[vs-3533]:
> Dec 7 17:26:23 krshina3 kernel: [38539.089194] reiser4[gdm(2676)]:
> key_warning (fs/reiser4/plugin/file_plugin_common.c:512)[nikita-717]:
> Dec 7 17:26:23 krshina3 kernel: [38539.090837]
> reiser4[gnome-screensav(3503)]: cbk_level_lookup
> (fs/reiser4/search.c:963)[vs-3533]:
> Dec 7 17:26:23 krshina3 kernel: [38539.090840]
> reiser4[gnome-screensav(3503)]: key_warning
> (fs/reiser4/plugin/file_plugin_common.c:512)[nikita-717]:
>
>
> I fscked the FSes and had some errors that were corrected.
>
> Now I started geting these and I can't kill the offending process:
>
> Dec 7 18:43:29 krshina3 kernel: [ 720.274343] INFO: task
> qemu-system-x86:4156 blocked for more than 120 seconds.
> Dec 7 18:43:29 krshina3 kernel: [ 720.274347] "echo 0 >
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> Dec 7 18:43:29 krshina3 kernel: [ 720.274349] qemu-system-x86 D
> 0000000000000001 0 4156 3654 0x00000000
> Dec 7 18:43:29 krshina3 kernel: [ 720.274354] ffff880206dd7990
> 0000000000000086 ffff8801def2fc38 ffff88022ca38cf0
> Dec 7 18:43:29 krshina3 kernel: [ 720.274357] 0000000000011240
> ffff8801def2ffd8 0000000000004000 ffff8801def2ffd8
> Dec 7 18:43:29 krshina3 kernel: [ 720.274361] 0000000000011240
> ffff880206dd7990 0000000000011240 ffff8801def2e000
> Dec 7 18:43:29 krshina3 kernel: [ 720.274364] Call Trace:
> Dec 7 18:43:29 krshina3 kernel: [ 720.274372] [<ffffffff810aec97>]
> ? pagevec_lookup_tag+0x18/0x21
> Dec 7 18:43:29 krshina3 kernel: [ 720.274375] [<ffffffff810a528a>]
> ? filemap_fdatawait_range+0xff/0x144
> Dec 7 18:43:29 krshina3 kernel: [ 720.274380] [<ffffffff81146b09>]
> ? writepages_unix_file+0x36e/0x3ce
> Dec 7 18:43:29 krshina3 kernel: [ 720.274384] [<ffffffff810ab9f9>]
> ? global_dirtyable_memory+0xd/0x2c
> Dec 7 18:43:29 krshina3 kernel: [ 720.274389] [<ffffffff81489dac>]
> ? __mutex_lock_slowpath+0xd0/0x116
> Dec 7 18:43:29 krshina3 kernel: [ 720.274392] [<ffffffff8148a096>]
> ? mutex_lock+0x1a/0x2d
> Dec 7 18:43:29 krshina3 kernel: [ 720.274396] [<ffffffff81143b73>]
> ? reiser4_sync_file_common+0x58/0xcd
> Dec 7 18:43:29 krshina3 kernel: [ 720.274400] [<ffffffff81147a81>]
> ? write_unix_file+0x442/0x4b7
> Dec 7 18:43:29 krshina3 kernel: [ 720.274404] [<ffffffff811498b9>]
> ? reiser4_write_careful+0xb8/0x450
> Dec 7 18:43:29 krshina3 kernel: [ 720.274409] [<ffffffff810da90f>]
> ? vfs_write+0xaf/0x149
> Dec 7 18:43:29 krshina3 kernel: [ 720.274412] [<ffffffff810dab49>]
> ? sys_pwrite64+0x53/0x71
> Dec 7 18:43:29 krshina3 kernel: [ 720.274415] [<ffffffff8148c3e2>]
> ? system_call_fastpath+0x16/0x1b
> Dec 7 18:43:29 krshina3 kernel: [ 720.274418] INFO: task
> qemu-system-x86:4162 blocked for more than 120 seconds.
> Dec 7 18:43:29 krshina3 kernel: [ 720.274419] "echo 0 >
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> Dec 7 18:43:29 krshina3 kernel: [ 720.274420] qemu-system-x86 D
> 0000000000000000 0 4162 3654 0x00000000
> Dec 7 18:43:29 krshina3 kernel: [ 720.274423] ffff88020f7cacf0
> 0000000000000086 ffff8801e007fe18 ffffffff816ab3f0
> Dec 7 18:43:29 krshina3 kernel: [ 720.274426] 0000000000011240
> ffff8801e007ffd8 0000000000004000 ffff8801e007ffd8
> Dec 7 18:43:29 krshina3 kernel: [ 720.274429] 0000000000011240
> ffff88020f7cacf0 0000000000011240 ffff8801e007e000
> Dec 7 18:43:29 krshina3 kernel: [ 720.274432] Call Trace:
> Dec 7 18:43:29 krshina3 kernel: [ 720.274437] [<ffffffff810aec97>]
> ? pagevec_lookup_tag+0x18/0x21
> Dec 7 18:43:29 krshina3 kernel: [ 720.274439] [<ffffffff810a528a>]
> ? filemap_fdatawait_range+0xff/0x144
> Dec 7 18:43:29 krshina3 kernel: [ 720.274443] [<ffffffff81146b09>]
> ? writepages_unix_file+0x36e/0x3ce
> Dec 7 18:43:29 krshina3 kernel: [ 720.274447] [<ffffffff81489dac>]
> ? __mutex_lock_slowpath+0xd0/0x116
> Dec 7 18:43:29 krshina3 kernel: [ 720.274450] [<ffffffff8148a096>]
> ? mutex_lock+0x1a/0x2d
> Dec 7 18:43:29 krshina3 kernel: [ 720.274453] [<ffffffff81143b73>]
> ? reiser4_sync_file_common+0x58/0xcd
> Dec 7 18:43:29 krshina3 kernel: [ 720.274457] [<ffffffff810fa6d8>]
> ? do_fsync+0x29/0x47
> Dec 7 18:43:29 krshina3 kernel: [ 720.274460] [<ffffffff810fa716>]
> ? sys_fdatasync+0xe/0x15
> Dec 7 18:43:29 krshina3 kernel: [ 720.274462] [<ffffffff8148c3e2>]
> ? system_call_fastpath+0x16/0x1b
> tail: unrecognized file system type 0x52345362 for
> '/var/log/messages'. please report this to bug-coreutils@gnu.org.
> reverting to polling
> Dec 7 18:45:29 krshina3 kernel: [ 840.266595] INFO: task
> qemu-system-x86:4156 blocked for more than 120 seconds.
> Dec 7 18:45:29 krshina3 kernel: [ 840.266599] "echo 0 >
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> Dec 7 18:45:29 krshina3 kernel: [ 840.266601] qemu-system-x86 D
> 0000000000000001 0 4156 3654 0x00000000
> Dec 7 18:45:29 krshina3 kernel: [ 840.266605] ffff880206dd7990
> 0000000000000086 ffff8801def2fc38 ffff88022ca38cf0
> Dec 7 18:45:29 krshina3 kernel: [ 840.266609] 0000000000011240
> ffff8801def2ffd8 0000000000004000 ffff8801def2ffd8
> Dec 7 18:45:29 krshina3 kernel: [ 840.266613] 0000000000011240
> ffff880206dd7990 0000000000011240 ffff8801def2e000
> Dec 7 18:45:29 krshina3 kernel: [ 840.266616] Call Trace:
> Dec 7 18:45:29 krshina3 kernel: [ 840.266625] [<ffffffff810aec97>]
> ? pagevec_lookup_tag+0x18/0x21
> Dec 7 18:45:29 krshina3 kernel: [ 840.266629] [<ffffffff810a528a>]
> ? filemap_fdatawait_range+0xff/0x144
> Dec 7 18:45:29 krshina3 kernel: [ 840.266634] [<ffffffff81146b09>]
> ? writepages_unix_file+0x36e/0x3ce
> Dec 7 18:45:29 krshina3 kernel: [ 840.266638] [<ffffffff810ab9f9>]
> ? global_dirtyable_memory+0xd/0x2c
> Dec 7 18:45:29 krshina3 kernel: [ 840.266643] [<ffffffff81489dac>]
> ? __mutex_lock_slowpath+0xd0/0x116
> Dec 7 18:45:29 krshina3 kernel: [ 840.266646] [<ffffffff8148a096>]
> ? mutex_lock+0x1a/0x2d
> Dec 7 18:45:29 krshina3 kernel: [ 840.266650] [<ffffffff81143b73>]
> ? reiser4_sync_file_common+0x58/0xcd
> Dec 7 18:45:29 krshina3 kernel: [ 840.266654] [<ffffffff81147a81>]
> ? write_unix_file+0x442/0x4b7
> Dec 7 18:45:29 krshina3 kernel: [ 840.266658] [<ffffffff811498b9>]
> ? reiser4_write_careful+0xb8/0x450
> Dec 7 18:45:29 krshina3 kernel: [ 840.266664] [<ffffffff810da90f>]
> ? vfs_write+0xaf/0x149
> Dec 7 18:45:29 krshina3 kernel: [ 840.266666] [<ffffffff810dab49>]
> ? sys_pwrite64+0x53/0x71
> Dec 7 18:45:29 krshina3 kernel: [ 840.266670] [<ffffffff8148c3e2>]
> ? system_call_fastpath+0x16/0x1b
> Dec 7 18:45:29 krshina3 kernel: [ 840.266672] INFO: task
> qemu-system-x86:4162 blocked for more than 120 seconds.
> Dec 7 18:45:29 krshina3 kernel: [ 840.266674] "echo 0 >
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> Dec 7 18:45:29 krshina3 kernel: [ 840.266675] qemu-system-x86 D
> 0000000000000000 0 4162 3654 0x00000000
> Dec 7 18:45:29 krshina3 kernel: [ 840.266678] ffff88020f7cacf0
> 0000000000000086 ffff8801e007fe18 ffffffff816ab3f0
> Dec 7 18:45:29 krshina3 kernel: [ 840.266681] 0000000000011240
> ffff8801e007ffd8 0000000000004000 ffff8801e007ffd8
> Dec 7 18:45:29 krshina3 kernel: [ 840.266684] 0000000000011240
> ffff88020f7cacf0 0000000000011240 ffff8801e007e000
> Dec 7 18:45:29 krshina3 kernel: [ 840.266687] Call Trace:
> Dec 7 18:45:29 krshina3 kernel: [ 840.266691] [<ffffffff810aec97>]
> ? pagevec_lookup_tag+0x18/0x21
> Dec 7 18:45:29 krshina3 kernel: [ 840.266694] [<ffffffff810a528a>]
> ? filemap_fdatawait_range+0xff/0x144
> Dec 7 18:45:29 krshina3 kernel: [ 840.266698] [<ffffffff81146b09>]
> ? writepages_unix_file+0x36e/0x3ce
> Dec 7 18:45:29 krshina3 kernel: [ 840.266702] [<ffffffff81489dac>]
> ? __mutex_lock_slowpath+0xd0/0x116
> Dec 7 18:45:29 krshina3 kernel: [ 840.266705] [<ffffffff8148a096>]
> ? mutex_lock+0x1a/0x2d
> Dec 7 18:45:29 krshina3 kernel: [ 840.266708] [<ffffffff81143b73>]
> ? reiser4_sync_file_common+0x58/0xcd
> Dec 7 18:45:29 krshina3 kernel: [ 840.266712] [<ffffffff810fa6d8>]
> ? do_fsync+0x29/0x47
> Dec 7 18:45:29 krshina3 kernel: [ 840.266714] [<ffffffff810fa716>]
> ? sys_fdatasync+0xe/0x15
> Dec 7 18:45:29 krshina3 kernel: [ 840.266717] [<ffffffff8148c3e2>]
> ? system_call_fastpath+0x16/0x1b
>
>
> File runs fine from FAT32 partition
>
> If I can do something, or you need any info tell me please
>
> Thanks
> Dushan
Did it start precisely from 2.6.39?
Got the same, and if yes, then it definitily seems to be an effect of the
problem with in-kernel(?) dcache corruption - the one which also results in
BUGs at 000000000000000e, assertion "nikita-2050" in jnode.c and so on...
BTW (@Edward): none of the problems can be reproduced on my VM with exactly
same software configuration (copied root partition)...
Regards,
Ivan.
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-12-09 12:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 17:56 R4 problem started with 2.6.39 and still there with 3.6.6 Dušan Čolić
2012-12-07 18:34 ` Dušan Čolić
2012-12-09 15:17 ` Ivan Shapovalov
2012-12-09 16:19 ` Dušan Čolić
2012-12-09 16:29 ` Dušan Čolić
2012-12-09 16:38 ` Ivan Shapovalov
2012-12-09 17:12 ` Dušan Čolić
2012-12-09 17:54 ` Dušan Čolić
2012-12-10 20:08 ` Dušan Čolić
2012-12-11 15:08 ` Kernel config option which causes reiser4 to be instable Ivan Shapovalov
2012-12-11 18:33 ` Edward Shishkin
2012-12-11 18:49 ` Ivan Shapovalov
2012-12-12 3:23 ` Ivan Shapovalov
[not found] ` <21180603.IycRkMTJZZ@intelfx-laptop>
2012-12-13 20:51 ` Edward Shishkin
2012-12-11 20:54 ` Dušan Čolić
2012-12-13 22:47 ` Edward Shishkin
2012-12-14 3:14 ` Ivan Shapovalov
2012-12-14 11:07 ` Edward Shishkin
2012-12-14 18:20 ` Ivan Shapovalov
2012-12-16 15:36 ` Edward Shishkin
2012-12-26 16:22 ` Ivan Shapovalov
2012-12-29 0:24 ` Edward Shishkin
2012-12-29 18:47 ` Ivan Shapovalov
2013-01-07 0:06 ` Edward Shishkin
2013-01-07 1:33 ` Ivan Shapovalov
2012-12-09 12:36 ` Ivan Shapovalov [this message]
2012-12-09 14:47 ` R4 problem started with 2.6.39 and still there with 3.6.6 Dušan Čolić
2012-12-09 14:52 ` Dušan Čolić
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1617029.ijnoNpQuXu@intelfx-laptop \
--to=intelfx100@gmail.com \
--cc=dusanc@gmail.com \
--cc=reiserfs-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.