All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: "Guilherme G. Piccoli" <gpiccoli@canonical.com>
Cc: linux-block@vger.kernel.org, Song Liu <songliubraving@fb.com>,
	NeilBrown <neilb@suse.com>,
	linux-raid@vger.kernel.org, dm-devel@redhat.com,
	jay.vosburgh@canonical.com
Subject: Re: [PATCH] md/raid0: Fail BIOs if their underlying block device is gone
Date: Tue, 30 Jul 2019 01:36:55 +0500	[thread overview]
Message-ID: <20190730013655.229020ea@natsu> (raw)
In-Reply-To: <053c88e1-06ec-0db1-de8f-68f63a3a1305@canonical.com>

On Mon, 29 Jul 2019 17:27:15 -0300
"Guilherme G. Piccoli" <gpiccoli@canonical.com> wrote:

> Hi Roman, I don't think this is usual setup. I understand that there are
> RAID10 (also known as RAID 0+1) in which we can have like 4 devices, and
> they pair in 2 sets of two disks using stripping, then these sets are
> paired using mirroring. This is handled by raid10 driver however, so it
> won't suffer for this issue.
> 
> I don't think it's common or even makes sense to back a raid1 with 2
> pure raid0 devices.

It might be not a usual setup, but it is a nice possibility that you get with
MD. If for the moment you don't have drives of the needed size, but have
smaller drives. E.g.:

- had a 2x1TB RAID1;
- one disk fails;
- no 1TB disks at hand;
- but lots of 500GB disks;
- let's make a 2x500GB RAID0 and have that stand in for the missing 1TB
member for the time being;

Or here's for a detailed rationale of a more permanent scenario:
https://louwrentius.com/building-a-raid-6-array-of-mixed-drives.html

-- 
With respect,
Roman

WARNING: multiple messages have this Message-ID (diff)
From: Roman Mamedov <rm@romanrm.net>
To: "Guilherme G. Piccoli" <gpiccoli@canonical.com>
Cc: linux-raid@vger.kernel.org, linux-block@vger.kernel.org,
	dm-devel@redhat.com, jay.vosburgh@canonical.com,
	NeilBrown <neilb@suse.com>, Song Liu <songliubraving@fb.com>
Subject: Re: [PATCH] md/raid0: Fail BIOs if their underlying block device is gone
Date: Tue, 30 Jul 2019 01:36:55 +0500	[thread overview]
Message-ID: <20190730013655.229020ea@natsu> (raw)
In-Reply-To: <053c88e1-06ec-0db1-de8f-68f63a3a1305@canonical.com>

On Mon, 29 Jul 2019 17:27:15 -0300
"Guilherme G. Piccoli" <gpiccoli@canonical.com> wrote:

> Hi Roman, I don't think this is usual setup. I understand that there are
> RAID10 (also known as RAID 0+1) in which we can have like 4 devices, and
> they pair in 2 sets of two disks using stripping, then these sets are
> paired using mirroring. This is handled by raid10 driver however, so it
> won't suffer for this issue.
> 
> I don't think it's common or even makes sense to back a raid1 with 2
> pure raid0 devices.

It might be not a usual setup, but it is a nice possibility that you get with
MD. If for the moment you don't have drives of the needed size, but have
smaller drives. E.g.:

- had a 2x1TB RAID1;
- one disk fails;
- no 1TB disks at hand;
- but lots of 500GB disks;
- let's make a 2x500GB RAID0 and have that stand in for the missing 1TB
member for the time being;

Or here's for a detailed rationale of a more permanent scenario:
https://louwrentius.com/building-a-raid-6-array-of-mixed-drives.html

-- 
With respect,
Roman

  reply	other threads:[~2019-07-29 20:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-29 19:33 [PATCH] md/raid0: Fail BIOs if their underlying block device is gone Guilherme G. Piccoli
2019-07-29 19:33 ` Guilherme G. Piccoli
2019-07-29 20:18 ` Roman Mamedov
2019-07-29 20:18   ` Roman Mamedov
2019-07-29 20:27   ` Guilherme G. Piccoli
2019-07-29 20:27     ` Guilherme G. Piccoli
2019-07-29 20:36     ` Roman Mamedov [this message]
2019-07-29 20:36       ` Roman Mamedov
2019-07-29 20:49       ` Guilherme G. Piccoli
2019-07-29 20:49         ` Guilherme G. Piccoli
2019-07-29 21:14     ` Reindl Harald
2019-07-29 21:14       ` Reindl Harald
2019-07-30  0:08 ` NeilBrown
2019-07-30  0:08   ` NeilBrown
2019-07-30 12:30   ` Guilherme G. Piccoli
2019-07-30 12:30     ` Guilherme G. Piccoli
2019-07-31 19:54     ` Song Liu
2019-07-31 19:54       ` Song Liu
2019-07-31 19:56       ` Song Liu
2019-07-31 19:56         ` Song Liu
2019-08-01 20:28         ` Guilherme G. Piccoli
2019-08-01 20:28           ` Guilherme G. Piccoli
2019-08-01 22:43           ` Song Liu
2019-08-01 22:43             ` Song Liu
2019-08-16 13:45             ` Guilherme G. Piccoli
2019-08-16 13:45               ` Guilherme G. Piccoli

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=20190730013655.229020ea@natsu \
    --to=rm@romanrm.net \
    --cc=dm-devel@redhat.com \
    --cc=gpiccoli@canonical.com \
    --cc=jay.vosburgh@canonical.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.com \
    --cc=songliubraving@fb.com \
    /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.