All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Elsayed <eternaleye@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: RAID device nomination (Feature request)
Date: Thu, 18 Apr 2013 12:48:10 -0700	[thread overview]
Message-ID: <kkpilp$kdd$1@ger.gmane.org> (raw)
In-Reply-To: 20130418140604.GL7639@carfax.org.uk

Hugo Mills wrote:

> On Thu, Apr 18, 2013 at 02:45:24PM +0100, Martin wrote:
>> Dear Devs,
<snip>
>> Note that esata shows just the disks as individual physical disks, 4 per
>> disk pack. Can physical disks be grouped together to force the RAID data
>> to be mirrored across all the nominated groups?
> 
>    Interesting you should ask this: I realised quite recently that
> this could probably be done fairly easily with a modification to the
> chunk allocator.
<snip>

One thing that might be an interesting approach:

Ceph is already in mainline, and uses CRUSH in a similar way to what's 
described (topology-aware placement+replication). Ceph does it by OSD nodes 
rather than disk, and the units are objects rather than chunks, but it could 
potentially be a rather good fit.

CRUSH does it by describing a topology hierarchy, and allocating the OSD ids 
to that hierarchy. It then uses that to map from a key to one-or-more 
locations. If we use chunk ID as the key, and use UUID_SUB in place of the 
OSD id, it could do the job.


  parent reply	other threads:[~2013-04-18 19:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-18 13:45 RAID device nomination (Feature request) Martin
2013-04-18 14:06 ` Hugo Mills
2013-04-18 16:29   ` Martin
2013-04-18 19:44     ` Hugo Mills
2013-04-19  0:31       ` Martin
2013-04-18 19:48   ` Alex Elsayed [this message]
2013-04-19  0:41     ` Martin
2013-04-19  3:05       ` Alex Elsayed

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='kkpilp$kdd$1@ger.gmane.org' \
    --to=eternaleye@gmail.com \
    --cc=linux-btrfs@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.