Re: drive failure during rebuild causes page fault

From: asym (asym_at_rfnj.org)
Date: 12/16/04

  • Next message: Gianluca: "Re: drive failure during rebuild causes page fault" 
    Date: Wed, 15 Dec 2004 18:48:52 -0500
To: ghost@kzsu.org, freebsd-stable@freebsd.org

    At 18:16 12/15/2004, Gianluca wrote:
    >barracudas and at this point I wonder if it's best to go w/ a small hw
    >raid controller like the 3ware 7506-4LP or use sw raid. I don't really
    >care about speed (I know RAID5 is not the best for that) nor hot
    >swapping, my main concern is data integrity. I tried to look online
    >but I couldn't find anything w/ practical suggestions except for
    >tutorials on how to configure vinum.

    If you don't care about hot-swapping, then you don't really care about (or
    need) RAID-5. It doesn't offer any additional "data integrity", but no
    RAID level does. What RAID does for you is allow you to survive an
    outright drive failure without losing any data. No RAID level can save you
    from buggy software writing garbage to the disk, transient disk errors, or
    the myriad other events that are far more common than a single drive just
    dying on you.

    Using RAID-5 as an example, during normal operations, a chunk is written to
    the "disk" and the controller (or software) calculates the bitwise XOR of
    all the blocks involved and writes that value into the parity
    stripe. During read operations, this parity data is not read or verified
    -- doing so would be pointless because there is no way to tell if it's the
    parity-stripe or the data-stripe that's "lying" if the two don't jive.

    So, during "normal" operations (all drives up and functioning) RAID-5
    functions readwise as a RAID-0 with one less disk than you really have, and
    as a somewhat slower array during writes.

    If a drive completely fails, then the parity stripe is always read up, and
    the missing data stripe is reconstructed from the parity data -- unless the
    parity stripe happens to fall on the missing drive for the stripe set
    you're currently accessing, in which case it is ignored and for that single
    access the array functions just as it would if a drive hadnot failed.

    If you're thinking of using RAID instead of good timely backups, you need
    to go back to the drawing board, because that is not what RAID is intended
    to replace -- and is something it cannot replace.

    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

  • Next message: Gianluca: "Re: drive failure during rebuild causes page fault"

    Relevant Pages

    • Re: AIX V5.3 & FASTT500 PERFORMANCE TUNING
      ... calculate the parity data every time a write is done, there is a decrease on performance when compared with reads, which doesn’t require the parity calculation. ... On a RAID_10, there is no parity calculation on either read or write, but there’s almost always a small slowdown in the write performance, due to the disk internals. ... commonly used implementation of RAID, Level 4 provides block-level striping with a parity disk. ... the information contained in this communication ...
      (AIX-L)
    • Re: Best Raid Level for Streaming?
      ... RAID 3: Striping and Parity ... In RAID level 3, data is striped across a set of disks. ... is generated and stored on a dedicated disk. ... In RAID level 5, both parity and data are striped across a set of disks. ...
      (microsoft.public.windowsmedia.server)
    • RE: Gvinum RAID5 performance
      ... > parity to data ratio, and the less benefit you would get from ... reading every disk in the stripe makes sense. ... random non-conflicting) data can be pulled from different drives, ...
      (freebsd-current)
    • Re: Gvinum RAID5 performance
      ... > periodically to verify the parity. ... disk storage subsystem that was configured for RAID-5 and then found ... > subsequent reads from the same stripe will be fed from memory, ...
      (freebsd-current)
    • Re: Wondering about raid5
      ... >> raid is started and the whole thing is checked over. ... is it going to computer every single parity block ... > If the lost disk was not one of the two being written ... Silent corruption, silent data creep - those are all ...
      (comp.os.linux.development.system)