From: Gene Czarcinski <gczarcinski@gmail.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: moving a subvol
Date: Fri, 13 Dec 2013 14:25:34 -0500 [thread overview]
Message-ID: <52AB5F2E.8020209@czarc.net> (raw)
In-Reply-To: <6EDC30B8-CF2C-42FA-9E30-D9F4B0804152@colorremedies.com>
On 12/13/2013 01:02 PM, Chris Murphy wrote:
>
> On Dec 13, 2013, at 10:37 AM, Cobin Bluth <cbluth@gmail.com> wrote:
>> That seems a little less intuitive than one would think. I wonder if there would an argument to specify read-write for btrfs-receive.
>
> I'm going to guess it's on purpose to prevent writes from happening in the subvolume while it's still being received. The send file is a stream so my interpretation of what's going on is that subvolume's file system isn't really in a state to be modified until it's completely done being written. And for that matter, it's the same thing with sending. The wiki says send requires subvolumes to be ro, and all of the examples there are ro subvolumes.
>
> I don't know that this is an apt analogy, but think of dd'ing a partition that contains a live mounted volume. Oops - not a good idea right? Because as you dd the first part, the uncopied portion is being modified and is now inconsistent.
>
>
Seems to have worked fine. What more could I ask for.
With Fedora 20 a go for gold, I decided to update to Fedora 20 on almost
all of my systems. At the same time I decided to do some consolidation
and restructuring of my disk layouts to put almost all of it under some
BTRFS volumes.
I really did not want to install Fedora 19 again and just want to move
the F19 rootfs from one volume to a newer other volume. It required
some editing of /etc/fstab to use the new UUIDs and also some manual
editing (ugh) of grub.cfg so that it had the correct UUIDs for the
volume with subvol=root4.
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.
Gene
next prev parent reply other threads:[~2013-12-13 19:26 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 [this message]
2013-12-14 7:07 ` Chris Samuel
2013-12-14 9:57 ` Gene Czarcinski
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=52AB5F2E.8020209@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).