Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: waxhead <waxhead@dirtcellar.net>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Per. subvolume RAID levels removed from planned features?
Date: Thu, 3 Dec 2020 00:52:06 +0100	[thread overview]
Message-ID: <e1b4808c-c057-e879-ef6e-33cdedcd3df1@dirtcellar.net> (raw)

I noticed that object level mirroring and striping was removed from the 
wikis list of 'features currently in development or planned for future 
releases.'

Does this mean that per. subvolume RAID levels are a lost cause?

I earlier suggest that I think that it should be possible to assign 
storage device ID's to groups. For example group1=fast_hdd, 
group2=fast_ssd, group3=slow_hdd, etc.... etc....

While admittedly per. subvolume RAID levels would be mostly useful if 
you could assign weight to a subvolume to make it prefer to be stored on 
a certain group or groups I still think that for some setups per. 
subvolume RAID levels still serves a purpose and I would hate to see 
that feature go.

                 reply	other threads:[~2020-12-02 23:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=e1b4808c-c057-e879-ef6e-33cdedcd3df1@dirtcellar.net \
    --to=waxhead@dirtcellar.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox