linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: Paul Harvey <csirac2@gmail.com>
Cc: Christoph Anton Mitterer <calestyo@scientia.net>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	russell@coker.com.au
Subject: Re: how to clone a btrfs filesystem
Date: Thu, 07 May 2015 20:57:21 +0200	[thread overview]
Message-ID: <1540375.q8H4Tysm3j@merkaba> (raw)
In-Reply-To: <CAB3_QuKK44Vy8Suu9xFap9m8ef+pLvOwd+=1_y3XA5YZwXpY+A@mail.gmail.com>

Am Donnerstag, 7. Mai 2015, 15:14:11 schrieb Paul Harvey:
> Sorry I'm late to this conversation...
> 
> On 18 April 2015 at 18:10, Martin Steigerwald <martin@lichtvoll.de> wrote:
> > That said, I think it can be scripted. But I am not aware of anyone
> > having done this. I may be missing something, so maybe someone on the
> > list has a recommendation.
> 
> I thought I'd mention that I have developed a script [1] which is a
> part of snazzer [2] which at least transports all snapshots of all
> subvolumes on all mounted btrfs filesystems (or a subset thereof),
> using send -p where possible between two local filesystems or a remote
> host via ssh. That is, of course, assuming your snapshots are named
> and located according to the idiomatic convention expected by
> snazzer-receive [1] - which is unlikely, I admit. Everybody uses btrfs
> slightly differently.

Thank you for the hint to your tool, sounds interesting. I am not sure 
whether it would work with my setup of having snapshots in root subvol, but 
then setting another subvol as default to hide snapshots behind a mount of 
the root subvol like this:

LABEL=home              /home                   btrfs           
noatime,space_cache,compress=lzo        0       0

LABEL=home              /mnt/home-snaps          btrfs           
noatime,space_cache,compress=lzo,subvolid=5     0       0

I know that space_cache is not needed after first mount with that option 
(thats why I think it does not make much sense to have this as a mount 
option in the first place, but rather as a property of the filesystem).

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

  reply	other threads:[~2015-05-07 18:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 23:08 how to clone a btrfs filesystem Christoph Anton Mitterer
2015-04-18  4:24 ` Russell Coker
2015-04-18  5:17   ` Christoph Anton Mitterer
2015-04-18 15:02     ` Russell Coker
2015-04-19  3:56       ` Duncan
2015-04-19 20:00       ` Christoph Anton Mitterer
2015-04-20  5:23         ` Duncan
2015-04-20 16:32           ` Christoph Anton Mitterer
2015-04-18  8:10 ` Martin Steigerwald
2015-05-07  5:14   ` Paul Harvey
2015-05-07 18:57     ` Martin Steigerwald [this message]
2015-05-08  3:22       ` Paul Harvey
2015-04-18 16:09 ` Kai Krakow
2015-04-18 16:23   ` Kai Krakow
2015-04-18 16:23   ` Chris Murphy
2015-04-18 16:36     ` Kai Krakow
2015-04-19 20:33       ` Chris Murphy
2015-04-18 16:20 ` Chris Murphy
2015-04-18 17:23   ` Christoph Anton Mitterer

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=1540375.q8H4Tysm3j@merkaba \
    --to=martin@lichtvoll.de \
    --cc=calestyo@scientia.net \
    --cc=csirac2@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=russell@coker.com.au \
    /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).