linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: lkhelp@rekl.yi.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.69, IDE TCQ can't be enabled
Date: Mon, 12 May 2003 16:46:54 +0400	[thread overview]
Message-ID: <20030512124654.GA2699@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0305092018530.16627@rekl.yi.org>

Hello!

On Fri, May 09, 2003 at 08:38:51PM -0500, lkhelp@rekl.yi.org wrote:
> I started testing 2.5.69, and I can't seem to get TCQ enabled on my 
> drives.  The test-tcq.pl script indicates that both drives in this 
> computer support TCQ:
> # ./test-tcq.pl
> /proc/ide/ide0/hda (WDC WD1200JB-00CRA1) supports TCQ
> /proc/ide/ide3/hdg (Maxtor 6E030L0) supports TCQ
> found reiserfs format "3.6" with standard journal
> Reiserfs journal params: device ide/host2/bus1/target0/lun0/par, size 
> 8192, journal first block 18, max trans len 1024, max batch 900, max 
> commit age 30, max trans age 30
> reiserfs: checking transaction log (ide/host2/bus1/target0/lun0/par) for 
> (ide/host2/bus1/target0/lun0/par)

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.

Bye,
    Oleg

  parent reply	other threads:[~2003-05-12 12:34 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 ` Oleg Drokin [this message]
2003-05-12 12:55   ` 2.5.69, IDE TCQ can't be enabled 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
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
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=20030512124654.GA2699@namesys.com \
    --to=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkhelp@rekl.yi.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 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).