On Thu, Apr 1, 2010 at 4:04 PM, Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx> wrote: > Hi, > >> > but since it is not possible to correct those errors, >> > there is no point in doing it... :-) >> >> Well it can. It can try and rewrite the block based on the data from the >> other disks, and if the drive needs to, it can remap the bad block. > > you might be unaware of the repeated neverending > discussions about this topic. > > It is *possible* to do it, but, as of today, it > cannot do it. > > I mean, there is no functionality, in the RAID-6, to > detect and correct those errors using the available > double parity. > > Consider that the RAID check returns only how many > mismatch are present, not where they are, i.e. on > which disks. > > bye, > > -- > > piergiorgio > -- > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > You are correct in that /silent/ errors cannot be detected, however drives typically do not verify writes and if for whatever reason a sector that was written cannot be read back the drive will /eventually/ return an error. At this point a re-write is issued based on the data recovered from the other drives. Only if that fails is the drive kicked from the array. -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
