All of lore.kernel.org
 help / color / mirror / Atom feed
From: PFC <lists@peufeu.com>
To: Valdis.Kletnieks@vt.edu
Cc: rvalles <rvalles@es.gnu.org>,
	reiserfs-list@namesys.com, boricua@despiertapr.com
Subject: Re: bad bread
Date: Tue, 09 May 2006 00:18:32 +0200	[thread overview]
Message-ID: <op.s886w6tlcigqcu@apollo13> (raw)
In-Reply-To: <200605081947.k48JldJd029006@turing-police.cc.vt.edu>


> Remember to take backups *anyhow*.  That way, if the RAID controller  
> dumps cow manure on all the sectors, you won't be saying "Oh, SH*T".

	Linux software RAID doesn't need a controller ;)
	But yes, backups should be done anyways.

	IMHO, RAID is good, harddisks are less reliable than the linux kernel,  
the linux RAID layer, and reiserfs.

> Also, note that there exist buggy RAID controllers, where if you are  
> doing
> mirroring to 2 disks, and they develop bad blocks at different locations,
> you can trash the mirror by resynchronizing (basically, you swap out one  
> of
> the bad disks, re-sync, it progresses as far as the bad block on the  
> source
> for the mirror, and dies).

	Linux RAID has a special option for that : you can trigger a check, which  
will re-read the entire disks and, if a read error occurs, re-write the  
failing sector with good data from the other drives in the RAID. The drive  
with the bad sector will then remap it to another sector.


  parent reply	other threads:[~2006-05-08 22:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-05 10:28 bad bread boricua
2006-05-07  0:56 ` rvalles
     [not found] ` <20060507005618.GA21557@rvalles.homedns.org.>
2006-05-07  8:35   ` PFC
2006-05-08 19:47     ` Valdis.Kletnieks
2006-05-08 20:32       ` Sander
2006-05-08 22:18       ` PFC [this message]
2006-05-09 18:46         ` Valdis.Kletnieks

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=op.s886w6tlcigqcu@apollo13 \
    --to=lists@peufeu.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=boricua@despiertapr.com \
    --cc=reiserfs-list@namesys.com \
    --cc=rvalles@es.gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.