From: Jason L Tibbitts III <tibbs@math.uh.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: ide drive dying?
Date: 06 Sep 2002 20:02:43 -0500 [thread overview]
Message-ID: <ufaadmuzk5o.fsf@epithumia.math.uh.edu> (raw)
In-Reply-To: Alan Cox's message of "06 Sep 2002 22:01:29 +0100"
>>>>> "AC" == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
AC> Thats up to the owner. There are lots of uses for such drives -
AC> /tmp, swap, in a raid array, etc
Be careful of these even in a RAID array; they will go bad silently.
I had one array (software RAID5, 8 75GXP drives on a 3w6800 in JBOD
mode, one hot spare) that was going fine until one drive died hard,
wouldn't spin up, etc. I replaced it, but during the RAID resync
three other drives were found to have errors. The array was trash,
but luckily all drives were dead just at the tail end, so I could copy
the data out during the RAID resync. Some of the failed drives had
the updated firmware.
3ware has background integrity scans now; I don't know if software
RAID has any equivalent besides an occasional 'dd', but even that's a
good idea.
- J<
next prev parent reply other threads:[~2002-09-07 0:58 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-06 20:40 Hell.Surfers
2002-09-06 21:01 ` Alan Cox
2002-09-06 21:45 ` jbradford
2002-09-07 1:02 ` Jason L Tibbitts III [this message]
2002-09-07 12:03 ` Daniel Egger
2002-09-06 21:07 ` DevilKin
-- strict thread matches above, loose matches on Subject: below --
2002-09-08 0:02 Dieter Nützel
2002-09-08 17:42 ` jbradford
2002-09-09 1:31 ` Nuitari
2002-09-08 19:27 ` Ed Sweetman
2002-09-08 20:11 ` jbradford
2002-09-09 2:37 ` Nuitari
2002-09-09 12:26 ` Joachim Breuer
2002-09-09 18:17 ` Thunder from the hill
2002-09-09 18:55 ` Mike Dresser
2002-09-10 12:48 ` Ookhoi
2002-09-10 13:59 ` Mike Dresser
2002-09-10 14:56 ` jbradford
2002-09-10 15:21 ` Mike Dresser
2002-09-10 15:29 ` Larry McVoy
2002-09-10 20:21 ` Andre Hedrick
[not found] <Pine.LNX.4.33.0209062017230.14523-100000@coffee.psychology.mcmaster.ca>
2002-09-07 6:09 ` jbradford
2002-09-06 15:13 DevilKin
2002-09-06 15:26 ` Mike Dresser
2002-09-06 15:39 ` Alan Cox
2002-09-06 15:42 ` Mike Dresser
2002-09-06 16:14 ` Billy Harvey
2002-09-06 16:41 ` Mike Dresser
2002-09-06 18:00 ` jbradford
2002-09-06 17:58 ` Mike Dresser
2002-09-06 15:44 ` Richard B. Johnson
2002-09-06 16:19 ` Craig Ruff
2002-09-06 17:28 ` Daniel Egger
2002-09-06 15:36 ` jbradford
2002-09-06 15:55 ` DevilKin
2002-09-06 17:22 ` jbradford
2002-09-06 19:22 ` DevilKin
2002-09-07 9:30 ` Anders Fugmann
2002-09-07 9:37 ` Udo A. Steinberg
2002-09-07 15:54 ` Holger Lubitz
2002-09-07 16:31 ` jbradford
2002-09-07 12:31 ` Daniel Egger
2002-09-07 13:08 ` jbradford
2002-09-07 13:50 ` Daniel Egger
2002-09-07 15:02 ` jbradford
2002-09-07 20:19 ` Daniel Egger
2002-09-07 20:41 ` jbradford
2002-09-07 21:41 ` Alan Cox
2002-09-07 21:41 ` Alan Cox
2002-09-07 22:00 ` jbradford
2002-09-07 23:19 ` David Forrest
2002-09-08 10:56 ` Henning P. Schmiedehausen
2002-09-08 14:14 ` jbradford
2002-09-09 21:59 ` Alan Cox
2002-09-07 22:05 ` Andre Hedrick
2002-09-07 7:08 ` Andre Hedrick
2002-09-06 15:37 ` mbs
2002-09-06 15:54 ` Alan Cox
2002-09-06 15:38 ` Alan Cox
2002-09-06 17:33 ` Daniel Egger
2002-09-06 20:31 ` Alan Cox
2002-09-06 15:44 ` mbs
2002-09-06 17:46 ` mbs
2002-09-06 20:32 ` Alan Cox
2002-09-07 12:34 ` Daniel Egger
2002-09-07 7:02 ` Andre Hedrick
2002-09-07 7:42 ` jbradford
2002-09-07 7:50 ` Andre Hedrick
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=ufaadmuzk5o.fsf@epithumia.math.uh.edu \
--to=tibbs@math.uh.edu \
--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®