From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Status: converting raid levels
Date: Fri, 6 Mar 2015 10:39:56 +0000 (UTC) [thread overview]
Message-ID: <pan.2015.03.06.10.39.56@googlemail.com> (raw)
In-Reply-To: CADurGxyF6g5Z+HNMry+q=b_oCKv1a6StDvp6pL20z=twK0BMHQ@mail.gmail.com
On Fri, 06 Mar 2015 11:22:09 +0100, Marcel Ritter wrote:
> please, can someone comment on the current status of raid level migration?
> (kernel 4.0.0-rc2, btrfs-progs 3.19-rc2)
>
> I just started testing this feature, and it doesn't seem to work:
You're very likely looking at something I found previously, see:
http://www.spinics.net/lists/linux-btrfs/msg42084.html & followups.
So far I haven't seen any fix appear anywhere; if you're daring
enough you can try to revert/undo the mentioned patch and see
what happens when you try to convert between RAID levels.
-h
next prev parent reply other threads:[~2015-03-06 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 10:22 Status: converting raid levels Marcel Ritter
2015-03-06 10:39 ` Holger Hoffstätte [this message]
2015-03-07 9:39 ` Filipe David Manana
2015-03-09 14:53 ` Marcel Ritter
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.06.10.39.56@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox