, but I have Seagate drives!
Guy
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brad Campbell
Sent: Tuesday, March 01, 2005 11:57 PM
To: Robin Bowes
Cc: linux-raid@vger.kernel.org
Subject: Re: Joys of spare disks!
Robin Bowes wrote:
Thanks to some
[EMAIL PROTECTED] wrote:
I've been going through the MD driver source, and to tell the truth, can't
figure out where the read error is detected and how to hook that event and
force a re-write of the failing sector. I would very much appreciate it if
I did that for RAID1, or at least most of
Guy [EMAIL PROTECTED] wrote:
I generally agree with you, so I'm just gonna cite / reply to the
points where we don't :-).
This sounded like Neil's current plan. But if I understand the plan, the
drive would be kicked out of the array.
Yeah, sounds bad.
Although it should be marked as
On Wednesday March 2, [EMAIL PROTECTED] wrote:
Is there any sound reason why this is not feasible? Is it just that
someone needs to write the code to implement it?
Exactly (just needs to be implemented).
NeilBrown
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the
Robin Bowes wrote:
I envisage something like:
md attempts read
one disk/partition fails with a bad block
md re-calculates correct data from other disks
md writes correct data to bad disk
- disk will re-locate the bad block
Probably not that simple, since some times multiple blocks will
@vger.kernel.org
Subject: Re: Joys of spare disks!
Robin Bowes wrote:
I envisage something like:
md attempts read
one disk/partition fails with a bad block
md re-calculates correct data from other disks
md writes correct data to bad disk
- disk will re-locate the bad block
Probably not that simple
Hi,
I run a RAID5 array built from six 250GB Maxtor Maxline II SATA disks.
After having several problems with Maxtor disks I decided to use a spare
disk, i.e. 5+1 spare.
Well, *another* disk failed last week. The spare disk was brought into
play seamlessly:
[EMAIL PROTECTED] ~]# mdadm
