From: Ivan Gyurdiev <ivg2@cornell.edu>
To: <lista1@telia.com>, <axboe@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.75 does not boot - TCQ oops
Date: Sat, 12 Jul 2003 06:46:01 -0400 [thread overview]
Message-ID: <200307120646.01060.ivg2@cornell.edu> (raw)
Okay, I figured out some more things.
I split my root fs in half and made two identical copies - one on reiser and
one on xfs. I compiled a bunch of kernels, and tested some more.
A TCQ enabled kernel with AS, queue depth of 32 works fine on both reiser and
xfs. A TCQ enabled kernel with deadline, queue depth of 32 works fine on both
reiser and xfs. Note the depth of 32. I had TCQ enabled on previous <74
kernels and it worked fine, everywhere with depth 32.
However, the kernel that crashed was using the default
(The default is 8, even though the comment says 32).
I tested that kernel again with reiserfs, TCQ, the two elevators, and queue
depth 8 - on-boot fsck detects corruption every time, marks the system
unclean, and requires --rebuild-tree or --fix-fixable on any further mounts.
I now get "Wrong amount of used blocks." message.
Have not tested depth 8 TCQ kernel with xfs, since that's my surviving root
fs, and I'd like to avoid corruption there.
Have not tested queue depths other than 8 and 32.
I could test some more on reiser now that I have a backup root fs.
next reply other threads:[~2003-07-12 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 10:46 Ivan Gyurdiev [this message]
2003-07-12 13:07 ` 2.5.75 does not boot - TCQ oops Voluspa
-- strict thread matches above, loose matches on Subject: below --
2003-07-12 7:51 Ivan Gyurdiev
2003-07-12 4:05 Voluspa
2003-07-11 8:35 Voluspa
2003-07-11 2:51 Ivan Gyurdiev
2003-07-11 8:03 ` Jens Axboe
2003-07-11 8:28 ` Jens Axboe
2003-07-11 8:34 ` Jens Axboe
2003-07-11 10:54 ` Bartlomiej Zolnierkiewicz
2003-07-11 10:55 ` Jens Axboe
2003-07-11 20:58 ` Ivan Gyurdiev
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=200307120646.01060.ivg2@cornell.edu \
--to=ivg2@cornell.edu \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lista1@telia.com \
/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).