All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin ESTRABAUD <be@mpstor.com>
To: linux-raid@vger.kernel.org
Subject: Disk link failure impact on Disks and RAID superblock in MD.
Date: Wed, 18 Apr 2012 12:52:58 +0100	[thread overview]
Message-ID: <4F8EAB1A.6000800@mpstor.com> (raw)

Hi,

I was wondering about the following:

Superblocks, and all RAID metadata, are stored on disks (to assemble the 
RAID), and also on the RAID (while assembled), and are necessary to run 
a RAID correctly, so long as at least <parity reached> of superblocks on 
disks are available, as <parity reached> number of disks are required 
for a specific RAID level to run (this excludes RAID 0 obviously).

This means that so long as less than 1 disk fails in RAID5, no more than 
one superblock will be lost and therefore the RAID can still assemble, 
and the metadata be read.

However, in modern RAID systems, the disks are all connected through a 
single path, being a SAS cable connected to a JBOD or a single SATA 
controller that can fail/crash.

Also, the RAID is not protected against power failure, which in my head 
are a bit equivalent to a complete disk link failure (SAS cable pulled).

In these cases where all the disks are lost at once, what is the 
probability of superblock corruption (both on the RAID superblock and 
the individual disks)?

If the superblock was being written during the failure, would it be 
incompletely written and therefore corrupted?

How reliably is it to keep a RAID alive (being able to re-assemble it) 
after continuously pulling and pushing the SAS cable?

Regards,
Ben.

             reply	other threads:[~2012-04-18 11:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18 11:52 Benjamin ESTRABAUD [this message]
2012-04-18 12:39 ` Disk link failure impact on Disks and RAID superblock in MD David Brown
2012-04-24 10:55   ` Benjamin ESTRABAUD

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=4F8EAB1A.6000800@mpstor.com \
    --to=be@mpstor.com \
    --cc=linux-raid@vger.kernel.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.