Date: Mon, 12 May 2003 15:30:08 +0200 (MET DST)
From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Oleg Drokin <green@namesys.com>
cc: <axboe@suse.de>, 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
In-Reply-To: <20030512132209.GB4165@namesys.com>
Message-ID: <Pine.SOL.4.30.0305121523550.18058-100000@mion.elka.pw.edu.pl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1380
Lines: 39


On Mon, 12 May 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?

I wanted to remove config option, just like it is for ide-tape.c
currently. But yes, its better to mark it DANGEROUS...

> 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.

many months ago :\

btw, some older disks have broken TCQ implementation...
--
Bartlomiej

> Bye,
>     Oleg

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/