From: Gene Czarcinski <gczarcinski@gmail.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: moving a subvol
Date: Sat, 14 Dec 2013 04:57:36 -0500 [thread overview]
Message-ID: <52AC2B90.909@czarc.net> (raw)
In-Reply-To: <1663965.RJ0nqNbRyM@quad>
On 12/14/2013 02:07 AM, Chris Samuel wrote:
> On Fri, 13 Dec 2013 02:25:34 PM Gene Czarcinski wrote:
>
>> Next it is to delete the old BTRFS volume, use fdisk to increase the
>> size of the partition and then attempt to increate the size of this new
>> volume. I hope I don't get bit in the rear end with this.
>
> Just make sure you have good (tested) backups..
>
Data subvolumes such as for /home have separate backups but the rootfs
subvolumes do not. If somethings gets screwed up, it is a matter of
reinstalling. Since I run Fedora with anaconda I use kickstart installs
and can easily repeat an install since it included almost everything I
want installed. And then I have a post-install script I run to pickup
additional stuff.
After successfully resizing, I then repeated with a two-device BTRFS
volume. Here the resize needs to be done for each device.
Question: What is did involved two BTRFS volumes on /dev/sdb1 and
/dev/sdb2. I deleted /dev/sdb2 and then expanded/resized /dev/sdb1.
This worked but I assume that doing the opposite would not work. That
is, deleteing the "lower" /dev/sdb1 and then expanding the "upper"
/dev/sdb2 because after rebooting the filesystem would not be at the
beginning of the partition.
Gene
next prev parent reply other threads:[~2013-12-14 9:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 16:07 moving a subvol Gene Czarcinski
2013-12-13 16:31 ` Gene Czarcinski
2013-12-13 17:25 ` Chris Murphy
[not found] ` <CAGvEgFHg-wO4BM9imQA9EpkMSLaEREchb9LBKXHkfFUPWwbfzQ@mail.gmail.com>
2013-12-13 18:02 ` Chris Murphy
2013-12-13 19:25 ` Gene Czarcinski
2013-12-14 7:07 ` Chris Samuel
2013-12-14 9:57 ` Gene Czarcinski [this message]
2013-12-14 18:43 ` Chris Murphy
2013-12-15 17:40 ` Gene Czarcinski
2013-12-15 20:42 ` Chris Murphy
2013-12-16 15:19 ` David Sterba
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=52AC2B90.909@czarc.net \
--to=gczarcinski@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).