linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: waxhead@dirtcellar.net, Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS subvolume RAID level
Date: Fri, 29 Nov 2019 08:44:18 +0800	[thread overview]
Message-ID: <f355213c-cd11-a346-b945-74bffe0f5e41@gmx.com> (raw)
In-Reply-To: <494b0df1-2aab-5169-836d-e381498f64db@dirtcellar.net>


[-- Attachment #1.1: Type: text/plain, Size: 1108 bytes --]



On 2019/11/29 上午6:48, waxhead wrote:
> Just out of curiosity....
> 
> What are the (potential) show stoppers for implementing subvolume RAID
> levels in BTRFS? This is more and more interesting now that new RAID
> levels has been merged (RAID1c3/4) and RAID5/6 is slowly inching towards
> usable status.

My quick guesses are:
- Subvolume and RAID aware extent allocator
  Current extent allocator cares nothing about who is requesting the
  extent.
  It cares a little about the RAID profile (only for convert).
  We need some work here at least.

- Way to prevent false ENOSPC due to profile restriction
  If subvolume is using some exotic profile, while extent/csum tree is
  using regular profile, and subvolume eats too many space, making
  it impossible to fit extent in their desired profile.
  We will got ENOSPC and even goes RO.

Thanks,
Qu

> 
> I imagine that RAIDc4 for example could potentially give a grotesque
> speed increase for parallel read operations once BTRFS learns to
> distribute reads to the device with the least waitqueue / fastest devices.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-11-29  0:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28 22:48 BTRFS subvolume RAID level waxhead
2019-11-29  0:44 ` Qu Wenruo [this message]
2019-12-02 10:48 ` Anand Jain
2019-12-02 23:27   ` waxhead
2019-12-03  1:30     ` Anand Jain
2019-12-03 20:31       ` waxhead
2019-12-05 12:10         ` Anand Jain

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=f355213c-cd11-a346-b945-74bffe0f5e41@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=waxhead@dirtcellar.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).