All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Gert Menke <gert@menke.ac>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Switch raid mode without rebalance?
Date: Thu, 25 Aug 2016 13:50:30 -0600	[thread overview]
Message-ID: <CAJCQCtRuQvgTj-jj=k8Ehsnq0uEkbbzJJwRR6T16H+R4d6SeTw@mail.gmail.com> (raw)
In-Reply-To: <efe09b37f04cbc7754f6c6d84c9070f0@durkon.lan>

On Thu, Aug 25, 2016 at 12:16 PM, Gert Menke <gert@menke.ac> wrote:

> However, I know that btrfs can have different raid modes on the same
> filesystem at the same time.

It's incidental right now. It's not something controllable or intended
to have enduring mixed profile block groups.

>So I was hoping I could just tell it to "switch
> to single mode for all new data", but I don't have a clue how to do that.

Such a switch doesn't exist, there's no way to define what files,
directories, or subvolumes, have what profiles.


>I
> *could* rebalance, of course, but is that really necessary?

Yes.

> How does btrfs
> find out which raid mode to use when writing new data?

That's kindof an interesting question. If you were to do 'btrfs
balance start -dconvert=single -mconvert=raid1' and very soon after
that do 'btrfs balance cancel' you'll end up with one or a few new
chunks with those profiles. When data is allocated to those chunks,
they will have those profile characteristics. When data is allocated
to old chunks that are still raid0, it will be raid0. The thing is,
you can't really tell or control what data will be placed in what
chunk. So it's plausible that some new data goes in old raid0 chunk,
and some old data goes in new single/raid1 chunks.


-- 
Chris Murphy

  parent reply	other threads:[~2016-08-25 19:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25 18:16 Switch raid mode without rebalance? Gert Menke
2016-08-25 18:26 ` Justin Kilpatrick
2016-08-25 22:32   ` Gert Menke
2016-08-26 11:52     ` Austin S. Hemmelgarn
2016-08-26 19:53       ` Gert Menke
2016-08-25 19:50 ` Chris Murphy [this message]
2016-08-25 22:33   ` Gert Menke
2016-08-25 23:04     ` Chris Murphy
2016-08-26 19:18       ` Gert Menke
2016-08-26 20:31         ` Chris Murphy

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='CAJCQCtRuQvgTj-jj=k8Ehsnq0uEkbbzJJwRR6T16H+R4d6SeTw@mail.gmail.com' \
    --to=lists@colorremedies.com \
    --cc=gert@menke.ac \
    --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.