All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Cannot convert to raid1
Date: Mon, 30 Mar 2015 09:59:10 +0000 (UTC)	[thread overview]
Message-ID: <pan.2015.03.30.09.59.10@googlemail.com> (raw)
In-Reply-To: a713705efd7fb91a19f773253c34b426@miceliux.com

On Mon, 30 Mar 2015 08:16:44 +0200, Juan Orti Alcaine wrote:

> El 2015-03-29 22:04, Holger Hoffstätte escribió:
>> On Sun, 29 Mar 2015 13:40:56 -0600, Chris Murphy wrote:
>> 
>>> On Sun, Mar 29, 2015 at 1:15 PM, Juan Orti Alcaine
>>> <juan.orti@miceliux.com> wrote:
>>> 
>>>> The filesystem was created with one device, and I have added two more
>>>> devices afterwards. To convert it to raid1, I have used:
>>>> 
>>>> # btrfs balance start -dconvert=raid1 -mconvert=raid1 
>>>> /mnt/btrfs_raid1
>>> 
>>>> The balance process has finished, but if I check my filesystem, it
>>>> shows up as single
>>> 
>>> Yeah, I'm kinda stumped. The only thing I'm thinking is if you're
>>> absolutely sure it's mounted at /mnt/btrfs_raid1 – because I've made
>>> this mistake before. (Oops.)
>> 
>> Nope, known bug in 4.0-rc:
>> http://thread.gmane.org/gmane.comp.file-systems.btrfs/43117
> 
> 
> Do you know if the fix is going to do it for 4.0 final?
> Thank you.

No idea, sorry. So far I don't see anything in Chris' trees.
I maintain my own kernel (for btrfs and some other extensions) and
just skipped that particular commit for now.

-h


      reply	other threads:[~2015-03-30  9:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-29 19:15 Cannot convert to raid1 Juan Orti Alcaine
2015-03-29 19:40 ` Chris Murphy
2015-03-29 20:04   ` Holger Hoffstätte
2015-03-30  6:16     ` Juan Orti Alcaine
2015-03-30  9:59       ` Holger Hoffstätte [this message]

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=pan.2015.03.30.09.59.10@googlemail.com \
    --to=holger.hoffstaette@googlemail.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.