From: Jens Axboe <axboe@suse.de>
To: Oleg Drokin <green@namesys.com>
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Oliver Neukum <oliver@neukum.org>,
lkhelp@rekl.yi.org, linux-kernel@vger.kernel.org
Subject: Re: 2.5.69, IDE TCQ can't be enabled
Date: Mon, 12 May 2003 15:23:30 +0200 [thread overview]
Message-ID: <20030512132330.GB17033@suse.de> (raw)
In-Reply-To: <20030512132209.GB4165@namesys.com>
On Mon, May 12 2003, Oleg Drokin wrote:
> Hello!
>
> On Mon, May 12, 2003 at 03:16:17PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > > > Just a note that we have found TCQ unusable on our IBM drives and we had
> > > > some reports about TCQ unusable on some WD drives.
> > > > Unusable means severe FS corruptions starting from mount.
> > > > So if your FSs will suddenly start to break, start looking for cause with
> > > > disabling TCQ, please.
> > > I can confirm that. This drive Model=IBM-DTLA-307045, FwRev=TX6OA60A,
> > > SerialNo=YMCYMT3Y229 has eaten my filesystem with TCQ on 2.5.69
> > TCQ is marked EXPERIMENTAL and is known to be broken.
> > Probably it should be marked DANGEROUS or removed?
>
> How do you think people will test code that is removed?
> Or do you mean that nobody plans to look at this ever?
> I remember that Jens Axboe promised to take a look at it some
> months ago.
Yeah, that is correct. OTOH, it's not a great loss. The SATA tcq will be
much better, ide tcq is a really horrible beast.
--
Jens Axboe
next prev parent reply other threads:[~2003-05-12 13:11 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 1:38 2.5.69, IDE TCQ can't be enabled lkhelp
2003-05-10 16:53 ` 2.5.69, IDE TCQ can't be enabled *RESOLVED* lkhelp
2003-05-10 17:26 ` Rob Ekl
2003-05-12 12:46 ` 2.5.69, IDE TCQ can't be enabled Oleg Drokin
2003-05-12 12:55 ` Oliver Neukum
2003-05-12 13:16 ` Bartlomiej Zolnierkiewicz
2003-05-12 13:12 ` Alan Cox
2003-05-13 15:39 ` Jens Axboe
2003-05-12 13:22 ` Oleg Drokin
2003-05-12 13:23 ` Jens Axboe [this message]
2003-05-12 13:35 ` Jeff Garzik
2003-05-12 13:30 ` Bartlomiej Zolnierkiewicz
2003-05-12 13:22 ` Jens Axboe
2003-05-13 15:32 ` Jens Axboe
2003-05-13 17:25 ` Oliver Neukum
2003-05-13 17:28 ` Jens Axboe
2003-05-13 18:46 ` Oliver Neukum
2003-05-13 19:06 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 17:58 Mudama, Eric
2003-05-12 18:59 ` Jens Axboe
2003-05-12 19:42 ` Jeff Garzik
2003-05-12 19:19 Mudama, Eric
2003-05-12 19:35 ` Jeff Garzik
2003-05-12 19:42 ` Jens Axboe
2003-05-12 19:44 ` Jens Axboe
2003-05-12 19:53 ` Jeff Garzik
2003-05-13 6:40 ` Jens Axboe
2003-05-13 18:00 ` Dave Jones
2003-05-13 18:03 ` Jens Axboe
2003-05-13 18:05 ` Jeff Garzik
2003-05-13 18:06 ` Jens Axboe
2003-05-13 18:13 ` Jens Axboe
2003-05-13 18:42 ` Jeff Garzik
2003-05-13 20:29 ` Andre Hedrick
2003-05-14 7:04 ` Jens Axboe
2003-05-14 7:15 ` Jens Axboe
2003-05-13 20:03 ` Andre Hedrick
2003-05-13 22:55 ` Alan Cox
2003-05-13 18:03 ` Jeff Garzik
2003-05-14 13:30 ` Henning P. Schmiedehausen
2003-05-12 22:36 ` Christer Weinigel
2003-05-13 6:41 ` Jens Axboe
2003-05-13 20:04 ` Bill Davidsen
2003-05-13 20:28 Mudama, Eric
2003-05-13 20:31 Mudama, Eric
2003-05-13 20:34 ` Andre Hedrick
2003-05-13 20:43 Mudama, Eric
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=20030512132330.GB17033@suse.de \
--to=axboe@suse.de \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkhelp@rekl.yi.org \
--cc=oliver@neukum.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.