hi, *
>>>>> "AS" == Alexander Schlensog <alex@xxxxxxxxx> writes:
AS> b) a second test machine also showing this error
AS> there is also a 3rd test box, but this one oopsed with a jbd error
AS> under heavy load (fsstress from the linux test project) - maybe i
AS> found a new (uncorrelated) fs error.
a few minutes ago the second test machine "b)" also showed an jbd
error. (fyi: this night i started using fsstress from ltp)
i do not know if this error is related to the error we are
hunting. maybe its only related to some other effect caused by
"fsstress"
Aug 25 20:13:00 localhost kernel: Assertion failure in journal_stop() at fs/jbd/transaction.c:1331: "journal_current_handle() == handle"
Aug 25 20:13:00 localhost kernel: ------------[ cut here ]------------
Aug 25 20:13:00 localhost kernel: kernel BUG at fs/jbd/transaction.c:1331!
Aug 25 20:13:00 localhost kernel: invalid operand: 0000 [#1]
Aug 25 20:13:00 localhost kernel: PREEMPT
Aug 25 20:13:00 localhost kernel: Modules linked in: nls_iso8859_1 loop ipv6
Aug 25 20:13:00 localhost kernel: CPU: 0
Aug 25 20:13:00 localhost kernel: EIP: 0060:[<c01a0dc0>] Not tainted
Aug 25 20:13:00 localhost kernel: EFLAGS: 00010286 (2.6.8-1.521as4)
Aug 25 20:13:00 localhost kernel: EIP is at journal_stop+0x60/0x2a0
Aug 25 20:13:00 localhost kernel: eax: 0000006a ebx: 00000004 ecx: ffffffff edx: d6753000
Aug 25 20:13:00 localhost kernel: esi: d872f7e0 edi: 00000000 ebp: d7c646bc esp: d6753d0c
Aug 25 20:13:00 localhost kernel: ds: 007b es: 007b ss: 0068
Aug 25 20:13:01 localhost kernel: Process fsstress (pid: 24943, threadinfo=d6753000 task=de5087e0)
Aug 25 20:13:01 localhost kernel: Stack: c036e2d4 c03588b6 c036c891 00000533 c036fb7c d6753d38 dfd7d4c0 c0194a50
Aug 25 20:13:01 localhost kernel: 00000000 defd3600 00000000 00000001 c0198ee4 d7c646bc 0001a000 0001a000
Aug 25 20:13:01 localhost kernel: 0001a000 d9ad4b54 c0192ab4 c0357d70 d7c646bc d9ad4b54 dffc4860 d6753ec0
Aug 25 20:13:01 localhost kernel: Call Trace:
Aug 25 20:13:01 localhost kernel: [<c0194a50>] ext3_mark_inode_dirty+0x50/0x60
Aug 25 20:13:01 localhost kernel: [<c0198ee4>] __ext3_journal_stop+0x24/0x50
Aug 25 20:13:01 localhost kernel: [<c0192ab4>] ext3_direct_IO+0xf4/0x230
Aug 25 20:13:01 localhost kernel: [<c0191990>] ext3_direct_io_get_blocks+0x0/0xf0
Aug 25 20:13:01 localhost kernel: [<c013974d>] generic_file_direct_IO+0x7d/0xa0
Aug 25 20:13:01 localhost kernel: [<c0139155>] generic_file_aio_write_nolock+0x7c5/0xaa0
Aug 25 20:13:01 localhost kernel: [<c01d15b5>] inode_has_perm+0x65/0xa0
Aug 25 20:13:01 localhost kernel: [<c0139538>] generic_file_aio_write+0x78/0xb0
Aug 25 20:13:01 localhost kernel: [<c018f624>] ext3_file_write+0x44/0xd0
Aug 25 20:13:01 localhost kernel: [<c0155030>] do_sync_write+0x80/0xb0
Aug 25 20:13:01 localhost kernel: [<c015514d>] vfs_write+0xed/0x160
Aug 25 20:13:01 localhost kernel: [<c0155291>] sys_write+0x51/0x80
Aug 25 20:13:01 localhost kernel: [<c03532c3>] syscall_call+0x7/0xb
Aug 25 20:13:01 localhost kernel: [<c035007b>] packet_setsockopt+0x10b/0x1d0
Aug 25 20:13:01 localhost kernel: Code: 0f 0b 33 05 91 c8 36 c0 0f b6 55 18 f6 c2 04 75 0e 8b 45 00
regards,
alex
-
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
