From: Thomas Schlichter <schlicht@uni-mannheim.de>
To: Nick Piggin <piggin@cyberone.com.au>, Ivan Gyurdiev <ivg2@cornell.edu>
Cc: Andrew Morton <akpm@osdl.org>,
B.Zolnierkiewicz@elka.pw.edu.pl, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: Processes receive SIGSEGV if TCQ is enabled
Date: Fri, 31 Oct 2003 08:28:33 +0100 [thread overview]
Message-ID: <200310310828.41598.schlicht@uni-mannheim.de> (raw)
In-Reply-To: <3FA1A171.3040807@cyberone.com.au>
[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]
Hi,
On Friday 31 October 2003 00:40, Nick Piggin wrote:
> Hi,
> If you're testing IDE TCQ, please try the following patch and use the
> default io scheduler. It won't fix anything, but it poisons requests
> so we can sometimes tell if they are being used in the wrong places.
> I have seen warnings that lead me to believe this might be happening.
> Its against 2.6.0-test9-mm1. Report any stack traces you see. Thanks.
OK, I tested 2.6.0-test9-mm1 + your patch, but it seems not to print any
messages or stack traces, even if many processes are killed after setting TCQ
depth to 1.
Today, however, I got reiserfs corruption messages in the logs, but
fsck.reiserfs could not find any corruption on the next boot, so I think this
is not a real corruption but just reading the wrong data...
The messages are something like:
Oct 31 07:57:53 bigboss kernel: is_tree_node: node level 2120 does not match
to the expected one 1
Oct 31 07:57:53 bigboss kernel: vs-5150: search_by_key: invalid format found
in block 642544. Fsck?
Oct 31 07:57:53 bigboss kernel: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [4767268 4767269 0x0 SD]
Oct 31 07:57:53 bigboss kernel: is_tree_node: node level 2120 does not match
to the expected one 1
Oct 31 07:57:53 bigboss kernel: vs-5150: search_by_key: invalid format found
in block 642544. Fsck?
Oct 31 07:57:53 bigboss kernel: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [4767268 4767269 0x0 SD]
> Nick
Thomas
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-31 7:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 15:01 Processes receive SIGSEGV if TCQ is enabled Thomas Schlichter
2003-10-30 17:48 ` Bartlomiej Zolnierkiewicz
2003-10-31 13:00 ` Jens Axboe
2003-10-31 13:11 ` Thomas Schlichter
2003-10-31 14:44 ` Ivan Gyurdiev
2003-10-30 21:33 ` Andrew Morton
2003-10-30 22:10 ` Thomas Schlichter
2003-10-30 22:44 ` Ivan Gyurdiev
2003-10-30 23:40 ` Nick Piggin
2003-10-31 7:28 ` Thomas Schlichter [this message]
2003-10-31 7:37 ` Nick Piggin
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=200310310828.41598.schlicht@uni-mannheim.de \
--to=schlicht@uni-mannheim.de \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=ivg2@cornell.edu \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).