All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: "marc@merlins.org" <marc@merlins.org>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	"hugo@carfax.org.uk" <hugo@carfax.org.uk>,
	"lists@colorremedies.com" <lists@colorremedies.com>
Subject: Re: Is anyone using btrfs send/receive for backups instead of rsync?
Date: Fri, 3 Jan 2014 20:35:59 +0000	[thread overview]
Message-ID: <1388781398.23513.0.camel@ret.masoncoding.com> (raw)
In-Reply-To: <20140103201543.GF10021@merlins.org>

On Fri, 2014-01-03 at 12:15 -0800, Marc MERLIN wrote:
> On Mon, Dec 30, 2013 at 09:57:40AM -0800, Marc MERLIN wrote:
> > On Mon, Dec 30, 2013 at 10:48:10AM -0700, Chris Murphy wrote:
> > > 
> > > On Dec 30, 2013, at 10:10 AM, Marc MERLIN <marc@merlins.org> wrote:
> > > > 
> > > > If one day, it could at least work on a subvolume level (only sync a
> > > > subvolume), then it would be more useful to me. Maybe later…
> > > 
> > > Maybe I'm missing something, but btrfs send/receive only work on a subvolume level.
> > 
> > Never mind, I seem to be the one being dense. I mis-read that you needed
> > to create the filesystem with btrfs receive.
> > Indeed, it's on a subvolume level, so it's actually fine since it does
> > allow over provisionning afterall.
> 
> Mmmh, but I just realized that on my laptop, I do boot the btrfs copy
> (currently done with rsync) from time to time (i.e. emergency boot from
> the HD the SSD was copied to).
> If I do that, it'll change the filesystem that was created with btrfs
> receive and break it, preventing further updates, correct?
> 
> If so, can I get around that by making a boot snapshot after each copy
> and mount that snapshot for emergency boot instead of the main volume?

Yes that will work.

-chris


  reply	other threads:[~2014-01-03 20:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-28 17:19 Is anyone using btrfs send/receive for backups instead of rsync? Marc MERLIN
2013-12-28 17:37 ` Hugo Mills
2013-12-28 18:01   ` Emil Karlson
2013-12-28 19:34     ` Richard Michael
2013-12-28 19:52       ` Emil Karlson
2013-12-28 20:34         ` Richard Michael
2013-12-28 23:11           ` Chris Murphy
2013-12-28 23:55             ` Emil Karlson
2013-12-29  0:08               ` Chris Murphy
2013-12-29 12:39             ` Duncan
2013-12-30  0:38               ` systemd-journal, nodatacow, was: " Chris Murphy
2013-12-30  8:07                 ` Duncan
2013-12-30 16:00                 ` Chris Mason
2013-12-28 18:07   ` Marc MERLIN
2013-12-28 18:20     ` Marc MERLIN
2013-12-30 16:05       ` Chris Mason
2013-12-30 16:17         ` Marc MERLIN
2013-12-30 16:26           ` Chris Mason
2013-12-30 17:10             ` Marc MERLIN
2013-12-30 17:48               ` Chris Murphy
2013-12-30 17:57                 ` Marc MERLIN
2013-12-30 18:39                   ` Chris Murphy
2014-01-03 20:15                   ` Marc MERLIN
2014-01-03 20:35                     ` Chris Mason [this message]
2014-01-07 10:49     ` Is anyone using btrfs send/receive howto? Marc MERLIN
2014-01-07 10:53       ` Hugo Mills
2014-01-08  8:02         ` Marc MERLIN
2014-03-21 17:29           ` Send/Receive howto and script for others to use (was Re: Is anyone using btrfs send/receive) Marc MERLIN
2014-03-22 19:44             ` Brendan Hide
2014-03-22 19:53               ` Brendan Hide
2014-03-22 20:00               ` Marc MERLIN
2014-03-22 21:02                 ` Brendan Hide
2014-03-22 21:11                   ` Marc MERLIN
2014-03-23  7:12                     ` Brendan Hide

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=1388781398.23513.0.camel@ret.masoncoding.com \
    --to=clm@fb.com \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=marc@merlins.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.