From: Martin Steigerwald <Martin@lichtvoll.de>
To: Michael Schuerig <michael.lists@schuerig.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Copying a disk containing a btrfs filesystem
Date: Thu, 10 Apr 2014 20:15:18 +0200 [thread overview]
Message-ID: <13063586.OmM7xhbOG8@merkaba> (raw)
In-Reply-To: <3414746.Gera7uWrI1@fuchsia>
Am Donnerstag, 10. April 2014, 17:51:26 schrieb Michael Schuerig:
> On Thursday 10 April 2014 15:15:02 Duncan wrote:
> > Meanwhile (2), given the existence of those tested backups, there's
> > yet another way to accomplish things. Simply restore from the
> > backups the same way you would if the working copy went down and you
> > had to restore it, only restore to the new device instead of the old
> > one. =:^)
>
> As the OP, let me insist that I have multiple backups. However and
> unfortunately, those backups do not contain the snapshots that I'd like
> to preserve when exchanging the disk. What makes the case complicate is
> not the question how to preserve and copy the current data; it's how to
> retain the historic data embodied in snapshots.
Well I think this is scriptable – although this would be some work.
Like this – pseudo shell code without verifying exact argument order:
- for each subvolume create according subvolume in destination
- for each snapshot – from oldest to newest:
- rsync / btrfs send snapshot
- snapshot with same name
- rsync next newer snapshot
I have snapshots on backup drive… so I´d probably ditch snapshots on
production side… but if you want them… thats another idea.
Although I like the balance idea as well. I used it to RAID-1 my /home to dual
SSD setup. But I didn´t to the degrading step.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2014-04-10 18:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 13:21 Copying a disk containing a btrfs filesystem Michael Schuerig
2014-04-10 13:58 ` Duncan
2014-04-10 14:53 ` Michael Schuerig
2014-04-10 14:00 ` George Eleftheriou
2014-04-10 15:15 ` Duncan
2014-04-10 15:51 ` Michael Schuerig
2014-04-10 16:01 ` George Eleftheriou
2014-04-10 16:24 ` Michael Schuerig
2014-04-11 0:35 ` Duncan
2014-04-10 18:15 ` Martin Steigerwald [this message]
2014-04-10 17:17 ` Jan Kouba
2014-04-10 18:36 ` Michael Schuerig
2014-04-10 22:25 ` Jan Kouba
2014-04-11 10:39 ` Brendan Hide
2014-04-16 11:12 ` Michael Schuerig
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=13063586.OmM7xhbOG8@merkaba \
--to=martin@lichtvoll.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=michael.lists@schuerig.de \
/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).