From: Vojtech Pavlik <vojtech@suse.cz>
To: Erik Slagter <erik@slagter.name>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Promise ATA/133 Errors With 2.6.10+
Date: Mon, 27 Jun 2005 13:33:01 +0200 [thread overview]
Message-ID: <20050627113301.GA8476@ucw.cz> (raw)
In-Reply-To: <1119867096.4020.59.camel@localhost.localdomain>
On Mon, Jun 27, 2005 at 12:11:36PM +0200, Erik Slagter wrote:
> On Sun, 2005-06-26 at 18:59 +0100, Alan Cox wrote:
> > On Sad, 2005-06-25 at 09:35, Justin Piszcz wrote:
> > > > BTW2 could it be that somewhere a timeout has been lowered in recent
> > > > kernels? That must have been pre-2.6.11 then.
> >
> > Timeouts have not changed or have increased in fact.
>
> Never mind, the offending harddisk has ceased to be yesterday, it is no
> more.
>
> What really bothers me, though, is that until the very last moment it
> was alive, it didn't report any smart error, nor did any self test fail.
> I guess IBM is to blame here :-(
Most drives report no SMART problems until they die. I've seen several
drives who weren't able to read/write or at least remap bad sectors, and
still their SMART statistics were almost perfect. The SMART event log
included the errors, though.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2005-06-27 11:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 20:55 Justin Piszcz
2005-06-25 8:29 ` Erik Slagter
2005-06-25 8:35 ` Justin Piszcz
2005-06-26 17:59 ` Alan Cox
2005-06-27 10:11 ` Erik Slagter
2005-06-27 11:33 ` Vojtech Pavlik [this message]
2005-06-27 11:46 ` Erik Slagter
[not found] ` <20050728223221.7f18a5a4.akpm@osdl.org>
2005-08-27 0:02 ` Justin Piszcz
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=20050627113301.GA8476@ucw.cz \
--to=vojtech@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=erik@slagter.name \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®