All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gene Czarcinski <gczarcinski@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: moving a subvol
Date: Fri, 13 Dec 2013 11:31:47 -0500	[thread overview]
Message-ID: <52AB3673.1030607@czarc.net> (raw)
In-Reply-To: <52AB30D4.7050408@czarc.net>

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.

I also found out that if you want to rename a subvolume, siple do it 
with "mv" like you would for a directory or a file.

OK folks, do I have it correct?

Gene


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

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=52AB3673.1030607@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 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.