From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Richard Heck <rgheck@bobjweil.com>,
Gene Heskett <gene.heskett@gmail.com>, Zan Lynx <zlynx@acm.org>,
Calvin Walton <calvin.walton@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ide Mailing list <linux-ide@vger.kernel.org>
Subject: Re: Problem with ata layer in 2.6.24
Date: Tue, 29 Jan 2008 19:34:03 +0000 [thread overview]
Message-ID: <20080129193403.62fe95e8@core> (raw)
In-Reply-To: <alpine.LNX.1.00.0801291354240.13593@iabervon.org>
> I've seen a lot of verbosity out of SCSI messages, but I haven't seen a
> straightforward interpretation of the problem in there. It's all
> information useful for debugging, not information useful for system
> administration.
It tells you what is going on. Unfortunately that frequently requires
some basic knowledge of how to interpret the error report. Drive
interface behaviour simply doesn't boil down to a fault light on the
dashboard or a "tighten the cable". For most common fault types you'll
get errors most administrators should find meaningful - like "Media error"
> On the other hand, bringing the system down because a device is
> misbehaving is a poor idea. I've personally recovered most of the data off
Hence we have RAID and SATA hotplug.
Alan
next prev parent reply other threads:[~2008-01-29 19:38 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200801272122.21823.gene.heskett@gmail.com>
[not found] ` <18333.36746.819935.641383@harpo.it.uu.se>
[not found] ` <1201521783.6149.33.camel@lappy>
2008-01-28 12:54 ` Problem with ata layer in 2.6.24 Gene Heskett
2008-01-28 13:19 ` Gene Heskett
2008-01-28 13:57 ` Mikael Pettersson
2008-01-28 16:35 ` Gene Heskett
2008-01-28 16:50 ` Calvin Walton
2008-01-28 17:20 ` Zan Lynx
2008-01-28 17:30 ` Gene Heskett
2008-01-28 17:44 ` Gene Heskett
2008-01-28 17:59 ` Daniel Barkalow
2008-01-28 18:23 ` Richard Heck
2008-01-28 20:01 ` Daniel Barkalow
2008-01-29 0:05 ` Gene Heskett
2008-01-29 0:34 ` Daniel Barkalow
2008-01-29 1:31 ` Gene Heskett
2008-01-29 1:51 ` Daniel Barkalow
2008-01-29 4:48 ` Michal Jaegermann
2008-01-29 12:12 ` Alan Cox
2008-01-29 14:30 ` Gene Heskett
2008-01-29 14:51 ` Gene Heskett
2008-01-29 15:47 ` Alan Cox
2008-01-29 16:32 ` Gene Heskett
2008-01-29 16:48 ` Mikael Pettersson
2008-01-29 17:04 ` Gene Heskett
2008-01-29 17:38 ` Daniel Barkalow
2008-01-29 17:44 ` Alan Cox
2008-01-29 18:12 ` Daniel Barkalow
2008-01-29 17:59 ` Gene Heskett
2008-01-29 18:54 ` Alan Cox
2008-01-29 22:41 ` Gene Heskett
2008-01-29 22:48 ` Alan Cox
2008-01-30 0:19 ` rgheck
2008-01-30 0:19 ` Mark Lord
2008-01-29 17:06 ` rgheck
2008-01-29 17:12 ` Alan Cox
2008-01-29 17:24 ` rgheck
2008-01-29 17:40 ` Alan Cox
2008-01-29 18:11 ` Mark Lord
2008-01-29 18:28 ` rgheck
2008-01-29 18:32 ` Mark Lord
2008-01-29 18:14 ` Daniel Barkalow
2008-01-29 18:46 ` Alan Cox
2008-01-29 19:14 ` Daniel Barkalow
2008-01-29 19:34 ` Alan Cox [this message]
2008-01-28 16:56 ` Gene Heskett
2008-01-28 18:20 ` Mark Lord
2008-01-28 18:59 ` Gene Heskett
2008-01-28 20:43 ` Mark Lord
2008-01-29 0:06 ` Gene Heskett
2008-01-29 3:16 ` Mark Lord
2008-01-29 4:07 ` Gene Heskett
2008-01-28 17:06 ` Dave Neuer
2008-01-29 4:23 ` Kasper Sandberg
2008-01-29 4:49 ` Gene Heskett
2008-01-29 5:01 ` Kasper Sandberg
2008-02-02 7:13 ` Tejun Heo
2008-01-28 14:44 ` Richard Heck
2008-01-28 17:01 ` Gene Heskett
2008-01-28 18:38 ` Mark Lord
2008-01-28 20:01 ` Alan Cox
2008-01-28 20:29 ` Mark Lord
[not found] ` <479E24F7.4090502@rtr.ca>
2008-01-28 19:01 ` Mark Lord
[not found] ` <200801281404.12937.gene.heskett@gmail.com>
[not found] ` <479E399C.1030409@rtr.ca>
2008-01-28 20:32 ` Mark Lord
2008-01-28 19:08 ` Jeff Garzik
2008-01-28 19:13 ` Gene Heskett
2008-01-29 6:41 ` Florian Attenberger
2008-01-29 15:04 ` Gene Heskett
2008-01-29 16:12 ` Mark Lord
2008-01-29 16:36 ` Gene Heskett
2008-01-29 18:09 ` Mark Lord
2008-01-29 16:50 ` rgheck
2008-01-29 16:58 ` Jeff Garzik
2008-01-29 17:12 ` Gene Heskett
2008-01-29 17:32 ` Jeff Garzik
2008-01-29 17:53 ` Gene Heskett
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=20080129193403.62fe95e8@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=barkalow@iabervon.org \
--cc=calvin.walton@gmail.com \
--cc=gene.heskett@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rgheck@bobjweil.com \
--cc=zlynx@acm.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).