All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Copying related snapshots to another server with btrfs send/receive?
Date: Wed, 7 May 2014 00:51:26 -0700	[thread overview]
Message-ID: <20140507075126.GA19238@merlins.org> (raw)
In-Reply-To: <pan$10f8$1751c450$6f6d3a98$57d04ce1@cox.net>

On Mon, May 05, 2014 at 03:24:45AM +0000, Duncan wrote:
> *However*: snapshotting a read-only snapshot and making the new one 
> writable is easy enough[1].  Just keep the originals read-only so they 
> can be used as parents/clones, and make a second, writable snapshot of 
> the first, to do your writable stuff in.
> 
> ---
> [1]  Snapshotting a snapshot: I'm getting a metaphorical flashing light 

I already snapshot ro snapshots as rw snapshots and that works fine.
It's actually rely on this in my script:
http://marc.merlins.org/perso/btrfs/post_2014-03-22_Btrfs-Tips_-Doing-Fast-Incremental-Backups-With-Btrfs-Send-and-Receive.html
(skip to the bottom)
# We make a read-write snapshot in case you want to use it for a chroot
# and some testing with a writeable filesystem or want to boot from a
# last good known snapshot.
btrfs subvolume snapshot "$src_newsnap" "$src_newsnaprw"
$ssh btrfs subvolume snapshot "$dest_pool/$src_newsnap" "$dest_pool/$src_newsnaprw"

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

      reply	other threads:[~2014-05-07  7:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-04  3:12 Copying related snapshots to another server with btrfs send/receive? Marc MERLIN
2014-05-04  7:16 ` Brendan Hide
2014-05-04  7:28   ` Marc MERLIN
2014-05-04  7:54     ` Brendan Hide
2014-05-05  1:04       ` Marc MERLIN
2014-05-05  3:24       ` Duncan
2014-05-07  7:51         ` Marc MERLIN [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=20140507075126.GA19238@merlins.org \
    --to=marc@merlins.org \
    --cc=1i5t5.duncan@cox.net \
    --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.