All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Tripathy <jonnyt@abpni.co.uk>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Which Disks can fail?
Date: Tue, 21 Jun 2011 11:56:41 +0100	[thread overview]
Message-ID: <4E0078E9.7070208@abpni.co.uk> (raw)
In-Reply-To: <20110621204509.6309c38f@notabene.brown>


On 21/06/2011 11:45, NeilBrown wrote:
> On Tue, 21 Jun 2011 11:24:20 +0100 Jonathan Tripathy<jonnyt@abpni.co.uk>
> wrote:
>
>> Hi Everyone,
>>
>> Use md's "single process" RAID10 with the standard near layout (which is
>> apperently the same as RAID1+0 in industry), which 2 drives could fail
>> without loosing the array?
>>
>> This is what I have:
>>
>> Number   Major   Minor   RaidDevice State
>>          0       8        5        0      active sync   /dev/sda5
>>          1       8       21        1      active sync   /dev/sdb5
>>          2       8       37        2      active sync   /dev/sdc5
>>          3       8       53        3      active sync   /dev/sdd5
>>
>> Thanks
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Run
>
>     man 4 md
>
>   search for "RAID10"
>
>   read what you find, and if it doesn't make sense, ask again.
>   If it does make sense, post your answer and feel free to ask for
>   confirmation.
>
>
> NeilBrown
Sorry, it still doesn't make much sense to me I'm afraid.

In fact, it's confused me more - since I'm using "near", does that means 
that the "copy" (I'm using near=2) of a given trunk may lie on the same 
disk, leading to *no redundancy*??

Thanks

  reply	other threads:[~2011-06-21 10:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 10:24 Which Disks can fail? Jonathan Tripathy
2011-06-21 10:45 ` NeilBrown
2011-06-21 10:56   ` Jonathan Tripathy [this message]
2011-06-21 11:42     ` NeilBrown
2011-06-21 11:57       ` Jonathan Tripathy
2011-06-21 15:31       ` Jonathan Tripathy
2011-06-23  7:02         ` NeilBrown

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=4E0078E9.7070208@abpni.co.uk \
    --to=jonnyt@abpni.co.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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.