From: David Greaves <david@dgreaves.com>
To: Brad Campbell <brad@wasp.net.au>
Cc: Guy <bugzilla@watkins-home.com>,
"Måns Rullgård" <mru@inprovide.com>,
linux-raid@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: RAID5 - 2nd drive died whilst waiting for RMA
Date: Wed, 17 Nov 2004 11:21:25 +0000 [thread overview]
Message-ID: <419B3435.3080707@dgreaves.com> (raw)
In-Reply-To: <41999A9B.2000907@wasp.net.au>
Brad Campbell wrote:
> David Greaves wrote:
>
>> Now all I need is SMART through libata.
>
>
> If you are using a UP system, grab the patches from Jeff's libata-dev
> tree and have at it.
> I have been beating it hard on 14 drives here on a loaded working
> server for weeks and have not managed to toast anything yet. It's
> great being able to keep tabs on the remaining whirly bits and
> hopefully get an early warning before they expire.
>
> (Fingers crossed. 12 of them are Maxtor Maxline-II drives but all sit
> between 35 & 40 deg C)
>
> Brad
Thanks Brad
I've been tracking this on the ide list and I've been nervous of
applying anything since I don't have proper backups. I'm relying on
redundancy.
I also found this comment by Jeff on some patches:
As I noted in another email, be careful... that patch bypasses the
SCSI command synchronization, so you could potentially send a SMART
command to the hardware while another command is still in progress.
He follows up by saying this *will* result in corruption.
And although I *think* he was refering to an earlier incarnation...
I looked to see what I'd need to do and given I'm running 2.6.9 I take
it I'd have to apply:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.9-libata1-dev1.patch.bz2
which depends on
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.9-libata1.patch.bz2
That seems like quite a lot and I'm not clear on the level of stability
impact on my system.
Now although I track linux-ide I doubt I'm fully informed!!
So if anyone would like to inform me of a reasonable course of action
then I'm actually reasonably happy to apply the SMART patch.
David
next prev parent reply other threads:[~2004-11-17 11:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-12 10:07 RAID5 - 2nd drive died whilst waiting for RMA David Greaves
2004-11-12 12:17 ` David Greaves
2004-11-12 16:22 ` Dick Streefland
2004-11-12 17:31 ` David Greaves
2004-11-12 17:49 ` Guy
2004-11-12 18:13 ` David Greaves
2004-11-12 17:48 ` Guy
2004-11-12 18:09 ` Guy
2004-11-12 18:30 ` David Greaves
2004-11-12 18:47 ` Guy
2004-11-13 19:48 ` David Greaves
2004-11-13 20:01 ` Måns Rullgård
2004-11-13 20:28 ` David Greaves
2004-11-13 20:32 ` Måns Rullgård
2004-11-13 20:39 ` Guy
2004-11-13 21:54 ` David Greaves
2004-11-15 16:55 ` David Greaves
2004-11-16 6:13 ` Brad Campbell
2004-11-17 11:21 ` David Greaves [this message]
2004-11-17 11:24 ` Måns Rullgård
2004-11-17 11:44 ` Brad Campbell
2004-11-17 12:04 ` David Greaves
2004-11-15 20:56 ` Robin Bowes
2004-11-15 21:24 ` Guy
2004-11-15 21:30 ` Robin Bowes
2004-11-15 21:39 ` Gordon Henderson
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=419B3435.3080707@dgreaves.com \
--to=david@dgreaves.com \
--cc=brad@wasp.net.au \
--cc=bugzilla@watkins-home.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mru@inprovide.com \
/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).