linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Is it possible to have metadata-only device with no data?
Date: Mon, 6 Feb 2017 07:37:30 -0500	[thread overview]
Message-ID: <f9011015-ff3d-7ea0-3f0b-4831dc83a2db@gmail.com> (raw)
In-Reply-To: <pan$76944$e15dabff$cb6ce271$3ab68bb5@cox.net>

On 2017-02-05 23:26, Duncan wrote:
> Hans van Kranenburg posted on Sun, 05 Feb 2017 22:55:42 +0100 as
> excerpted:
>
>> On 02/05/2017 10:42 PM, Alexander Tomokhov wrote:
>>> Is it possible, having two drives to do raid1 for metadata but keep
>>> data on a single drive only?
>>
>> Nope.
>>
>> Would be a really nice feature though... Putting metadata on SSD and
>> bulk data on HDD...
>
> FWIW, it's on the list to be implemented in the future, but there's a lot
> more things on that list than devs working on btrfs, and the feature
> development and stabilization trend is that features often take much
> longer than anticipated, particularly to properly stabilize (to the level
> of the rest of btrfs, which is in general stabilizing but not yet fully
> stable, so stabilization is relative, here), which has slowed down the
> pipeline of new features due to the devs having their hands full
> stabilizing currently done but not yet properly stabilized features.
There are also a number of higher priority features than this.  While it 
would be a wonderful feature to have, it doesn't exactly have a 
particularly significant impact on broad usability.  Most of the 
features being actively worked on are trying to gain parity (no pun 
intended) with other multi-device storage stacks.  Working quotas, 
parity-RAID, hot-spares, and n-way replication are all pretty 
significant to the usability of BTRFS in a pretty large number of 
situations, which is a large part of why they (other than n-way 
replication) are the primary focus right now for development.

  reply	other threads:[~2017-02-06 12:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-05 21:42 Is it possible to have metadata-only device with no data? Alexander Tomokhov
2017-02-05 21:55 ` Hans van Kranenburg
2017-02-05 23:54   ` Roman Mamedov
2017-02-14  1:20     ` Alexander Tomokhov
2017-02-06  4:26   ` Duncan
2017-02-06 12:37     ` Austin S. Hemmelgarn [this message]
2017-02-05 22:27 ` Kai Krakow
2017-02-14  1:22   ` Alexander Tomokhov
2017-02-06 18:39 ` Omar Sandoval

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=f9011015-ff3d-7ea0-3f0b-4831dc83a2db@gmail.com \
    --to=ahferroin7@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 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).