linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Schuerig <michael.lists@schuerig.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Copying a disk containing a btrfs filesystem
Date: Thu, 10 Apr 2014 17:51:26 +0200	[thread overview]
Message-ID: <3414746.Gera7uWrI1@fuchsia> (raw)
In-Reply-To: <pan$2aca0$96a1810f$3919e968$6678f073@cox.net>

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.

Michael

-- 
Michael Schuerig
mailto:michael@schuerig.de
http://www.schuerig.de/michael/


  reply	other threads:[~2014-04-10 15:51 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 [this message]
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
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=3414746.Gera7uWrI1@fuchsia \
    --to=michael.lists@schuerig.de \
    --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 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).