From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: Re: when does it become faulty disk Date: Mon, 20 Jun 2005 17:45:36 +0400 Message-ID: <42B6C880.6020305@tls.msk.ru> References: <5d96567b05061804477325d743@mail.gmail.com> <62b0912f05061912103ad3c459@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <62b0912f05061912103ad3c459@mail.gmail.com> Sender: linux-raid-owner@vger.kernel.org To: Molle Bestefich Cc: "Raz Ben-Jehuda(caro)" , linux-raid@vger.kernel.org List-Id: linux-raid.ids 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