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 18:24 +0200 [thread overview]
Message-ID: <1924982.LHpDrRg8EQ@fuchsia> (raw)
In-Reply-To: <CAPpBBdNo0ar8+2Kt9O_mNyQsmmOvFNfVJ=a_EA1HW=TnS4uTXQ@mail.gmail.com>
On Thursday 10 April 2014 18:01:31 George Eleftheriou wrote:
> > 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.
>
> You can always rsync (incrementally with --link-dest) to "another
> place" the sequence of snapshots, provided of course there is enough
> space in this "other place". However I understand this may not be the
> coolest thing to do especially taking into account the SMART warnings
> for imminent deterioration.
In the case at hand, I'll go with ddrescue. As far as backups are
concerned, rsync --link-dest may be an option, however even at best it
would only give file-granularity COW as opposed to block-granularity.
I'm not sure if this would work for me in terms of disk space
consumption.
I *think* send/receive with clone sources might be the key to a
solution. I'm still hoping that someone with a far better understanding
of btrfs than me gives it a try first...
Michael
--
Michael Schuerig
mailto:michael@schuerig.de
http://www.schuerig.de/michael/
next prev parent reply other threads:[~2014-04-10 16:24 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 [this message]
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=1924982.LHpDrRg8EQ@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 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.