From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Jens Axboe <axboe@suse.de>, Jeff Garzik <jgarzik@pobox.com>,
Dave Jones <davej@codemonkey.org.uk>,
"Mudama, Eric" <eric_mudama@maxtor.com>,
Oleg Drokin <green@namesys.com>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Oliver Neukum <oliver@neukum.org>,
lkhelp@rekl.yi.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.69, IDE TCQ can't be enabled
Date: 13 May 2003 23:55:52 +0100 [thread overview]
Message-ID: <1052866550.1205.13.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.10.10305131256240.2718-100000@master.linux-ide.org>
On Maw, 2003-05-13 at 21:03, Andre Hedrick wrote:
> Not a single OS (linux included) can deal with a error in flush cache,
> much less an error from a previous tagged request.
To be reasonable its not clear what you can do when a flush cache fails. The
only cases I can see you can handle anything intelligently are drive side but
even those are not clear. If the drive flushes all the blocks it can get
to disk its really the same as a fatal write error except we have less idea how
to recover and have already lost the data.
For the cases it matters you turn off write cache and we (maybe SATA time mostly)
get tcq working properly.
This is the same issue as with SCSI. SCSI has a whole rats nest of things that
seem to exist solely to screw up error recovery 8)
next prev parent reply other threads:[~2003-05-13 23:42 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 19:19 2.5.69, IDE TCQ can't be enabled 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 20:43 Mudama, Eric
2003-05-13 20:31 Mudama, Eric
2003-05-13 20:34 ` Andre Hedrick
2003-05-13 20:28 Mudama, Eric
2003-05-12 17:58 Mudama, Eric
2003-05-12 18:59 ` Jens Axboe
2003-05-12 19:42 ` Jeff Garzik
2003-05-10 1:38 lkhelp
2003-05-12 12:46 ` 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
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
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=1052866550.1205.13.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=andre@linux-ide.org \
--cc=axboe@suse.de \
--cc=davej@codemonkey.org.uk \
--cc=eric_mudama@maxtor.com \
--cc=green@namesys.com \
--cc=jgarzik@pobox.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 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).