From: Ilya Dryomov <idryomov@gmail.com>
To: David Sterba <dsterba@suse.cz>,
Austin S Hemmelgarn <ahferroin7@gmail.com>,
linux-btrfs@vger.kernel.org, Ilya Drymov <idryomov@gmail.com>
Subject: Re: [PATCH] btrfs: Allow forced conversion of metadata to dup profile on multiple devices
Date: Mon, 24 Feb 2014 15:37:05 +0200 [thread overview]
Message-ID: <CAOi1vP9hEqBcDgY-zthijx37+_cowhoMQaTZyWG9OUqOQvJR2A@mail.gmail.com> (raw)
In-Reply-To: <20140220165743.GT16073@twin.jikos.cz>
On Thu, Feb 20, 2014 at 6:57 PM, David Sterba <dsterba@suse.cz> wrote:
> On Wed, Feb 19, 2014 at 11:10:41AM -0500, Austin S Hemmelgarn wrote:
>> Currently, btrfs balance start fails when trying to convert metadata or
>> system chunks to dup profile on filesystems with multiple devices. This
>> requires that a conversion from a multi-device filesystem to a single
>> device filesystem use the following methodology:
>> 1. btrfs balance start -dconvert=single -mconvert=single \
>> -sconvert=single -f /
>> 2. btrfs device delete / /dev/sdx
>> 3. btrfs balance start -mconvert=dup -sconvert=dup /
>> This results in a period of time (possibly very long if the devices are
>> big) where you don't have the protection guarantees of multiple copies
>> of metadata chunks.
>>
>> After applying this patch, one can instead use the following methodology
>> for conversion from a multi-device filesystem to a single device
>> filesystem:
>> 1. btrfs balance start -dconvert=single -mconvert=dup \
>> -sconvert=dup -f /
>> 2. btrfs device delete / /dev/sdx
>> This greatly reduces the chances of the operation causing data loss due
>> to a read error during the device delete.
>>
>> Signed-off-by: Austin S. Hemmelgarn <ahferroin7@gmail.com>
> Reviewed-by: David Sterba <dsterba@suse.cz>
>
> Sounds useful. The muliple devices + DUP is allowed setup when the
> device is added, this patch only adds the 'delete' counterpart. The
> imroved data loss protection during the process is a good thing.
Hi,
Have you actually tried to queue it? Unless I'm missing something, it won't
compile, and on top of that, it seems to be corrupted too..
IIRC muliple devices + DUP is "allowed" only until the first balance, has that
changed?
Thanks,
Ilya
next prev parent reply other threads:[~2014-02-24 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 16:10 [PATCH] btrfs: Allow forced conversion of metadata to dup profile on multiple devices Austin S Hemmelgarn
2014-02-20 16:57 ` David Sterba
2014-02-24 13:37 ` Ilya Dryomov [this message]
2014-02-24 13:44 ` Austin S Hemmelgarn
2014-02-24 14:12 ` Ilya Dryomov
2014-02-24 14:40 ` Austin S Hemmelgarn
2014-02-26 14:23 [PATCH] btrfs: Allow forced conversion of metadata to dup profile on, " Austin S Hemmelgarn
2014-03-07 18:05 ` Josef Bacik
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=CAOi1vP9hEqBcDgY-zthijx37+_cowhoMQaTZyWG9OUqOQvJR2A@mail.gmail.com \
--to=idryomov@gmail.com \
--cc=ahferroin7@gmail.com \
--cc=dsterba@suse.cz \
--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.