On 12/13/2013 01:02 PM, Chris Murphy wrote:
On Dec 13, 2013, at 10:37 AM, Cobin Bluth <cbl...@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
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
