From: Michael Tokarev <mjt@tls.msk.ru>
To: Molle Bestefich <molle.bestefich@gmail.com>
Cc: "Raz Ben-Jehuda(caro)" <raziebe@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: when does it become faulty disk
Date: Mon, 20 Jun 2005 17:45:36 +0400 [thread overview]
Message-ID: <42B6C880.6020305@tls.msk.ru> (raw)
In-Reply-To: <62b0912f05061912103ad3c459@mail.gmail.com>
Molle Bestefich wrote:
> Raz Ben-Jehuda(caro) wrote:
>
>>I have managed to make the kernel remove a disk
>>from my raid even if this raid is "/" . I did it by adding a line
>>in ata_scsi_error that remove the ata disk from the raid array.
>>This means that when the first error ocurrs on a disk It is removed
>>from the array.
>>Well, this is not the best thing to do..
>>Question is :
>>When does a disk become faulty ?
>
>
> When trying to read sectors from a disk and the disk fails the read:
> 1.) Read the data from the other disks in the RAID and
> 2.) Overwrite the sectors where the read error occur.
Note: this is NOT how current linux softraid code works, it's
how it *supposed* to work. And right now, linux raid code
kicks a drive out of the array after *any* error (read or
write), without trying to "understand" what happened.
/mjt
next prev parent reply other threads:[~2005-06-20 13:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 11:47 when does it become faulty disk Raz Ben-Jehuda(caro)
2005-06-19 19:10 ` Molle Bestefich
2005-06-20 6:43 ` raz ben jehuda
2005-06-20 7:55 ` Molle Bestefich
2005-06-20 10:09 ` raz ben jehuda
2005-06-20 13:45 ` Michael Tokarev [this message]
2005-06-20 15:35 ` raz ben jehuda
2005-06-21 1:53 ` More tales of horror from the linux (HW) raid crypt Harry Mangalam
2005-06-22 19:33 ` Mike Hardy
2005-06-22 20:16 ` Harry Mangalam
2005-06-22 20:38 ` Jure Pecar
2005-06-22 21:33 ` Harry Mangalam
2005-06-22 23:15 ` SMART, was " Konstantin Olchanski
2005-06-22 23:32 ` Harry Mangalam
2005-06-22 23:35 ` Mike Hardy
2005-06-22 21:09 ` Brad Dameron
2005-06-22 21:43 ` Harry Mangalam
2005-06-22 22:00 ` Ming Zhang
2005-06-22 22:11 ` John Madden
2005-06-22 22:26 ` Ming Zhang
2005-06-23 0:20 ` bdameron
2005-06-22 22:45 ` Harry Mangalam
2005-06-22 23:05 ` Ming Zhang
2005-06-23 0:25 ` bdameron
2005-06-23 0:14 ` bdameron
2005-06-23 0:49 ` Ming Zhang
2005-06-23 3:05 ` Guy
2005-06-23 12:31 ` Ming Zhang
2005-06-23 13:03 ` Guy
2005-06-23 13:17 ` Andy Smith
2005-06-23 13:19 ` Ming Zhang
2005-06-22 23:54 ` Jon Lewis
2005-06-22 20:54 ` Dan Stromberg
2005-06-22 21:15 ` Brad Dameron
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=42B6C880.6020305@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-raid@vger.kernel.org \
--cc=molle.bestefich@gmail.com \
--cc=raziebe@gmail.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).