linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Gene Czarcinski <gczarcinski@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: moving a subvol
Date: Mon, 16 Dec 2013 16:19:17 +0100	[thread overview]
Message-ID: <20131216151917.GH6498@twin.jikos.cz> (raw)
In-Reply-To: <52AB3673.1030607@czarc.net>

On Fri, Dec 13, 2013 at 11:31:47AM -0500, Gene Czarcinski wrote:
> On 12/13/2013 11:07 AM, Gene Czarcinski wrote:
> >I have hunted high and low for the information but, if it is out there,
> >it is well hidden.
> >
> >What I want to do:  I want to relocate (move) a subvolume from one BTRFS
> >volume to a different BTRFS volume.
> >
> >I have seen the writeup for incremental backup which takes a snapshot,
> >and then using btrfs-send and btrfs-receive to create a copy on a
> >different volume.  That works fine except the btrfs-receive set the new
> >copy to be readonly.
> >
> >What I want to do is to use that new subvolume read/write.  The only way
> >I have figured out to do this is to create another snapshot on the new
> >volume which is NOT readonly.  I believe that means I need to keep both
> >of these subvolumes around.
> 
> As soon as I sent this I believe I found the answer.
> 
> I was sort of right about creating the new read-write (NOT readonly)
> snapshot.  After it is created simply delete the one which was created by
> btrfs-receive.

ATM, this is the way to do it. There's an ioctl to toggle the RO/RW
status of a subvolume, so it could save you one snapshot, but there's
not tool support to do that. I hope this will be possible with the
upcomming 'per-object properties' feature.

david

      parent reply	other threads:[~2013-12-16 15:19 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
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 [this message]

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=20131216151917.GH6498@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=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).