linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Copying a disk containing a btrfs filesystem
Date: Thu, 10 Apr 2014 15:15:02 +0000 (UTC)	[thread overview]
Message-ID: <pan$2aca0$96a1810f$3919e968$6678f073@cox.net> (raw)
In-Reply-To: CAPpBBdMCAFASLgGpbWo7-Pp74S_KQdZ2A7qrSNzo0rGrZAbqMw@mail.gmail.com

George Eleftheriou posted on Thu, 10 Apr 2014 16:00:06 +0200 as excerpted:

> Maybe there is another much more complicated solution:
> 
> Plug the old disk in a USB dock/case, do the same for the new disk in
> another dock/case, plug both docks/cases in another linux system running
> recent kernel and btrfs-progs and convert to a "-dconvert=raid1
> -mconvert=raid1" profile with a balance. Then degrade it by removing the
> old disk and rebalance-convert back to single or DUP profile (i am not
> quite sure this is even possible).
> 
> Just an idea. I wouldn't trust me.

Creative idea, actually, and one I've seen come up here before tho if you 
read my earlier response I didn't mention it myself, as I failed to 
recall it.

But yes, it is somewhat more complicated, and sort of an abuse of 
existing features for a purpose they weren't intended for.  It should 
still work and such unintended purpose uses are a good thing, but because 
it is unintended usage, it won't have been tested much if at all, and 
given that btrfs isn't itself fully stable yet, there's a fair likelihood 
that some unanticipated complexities would arise while doing it, as well.

Meanwhile, by the very fact that btrfs is /not/ yet entirely stable, 
there's even more reason than normal to have good, tested backups.  Given 
that, there should be no harm in trying this, since even if it somehow 
kills the working copy, one can still restore from those already tested 
backups.  And someone's gotta be the first to test this method and report 
on how it went, right?

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.  =:^)

(Actually, given my usual insistence on this key point, that btrfs isn't 
yet fully stable and that as a result by definition, you either have 
tested backups or you're demonstrating by practice that you simply don't 
care about losing the data anyway whatever your words might otherwise 
claim, I really should have thought of and mentioned the restoring from 
backups method first, instead of having it occur to me as an after-
thought.  I must be getting sloppy and careless in my thinking! =:^( )

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-04-10 15: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 [this message]
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
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='pan$2aca0$96a1810f$3919e968$6678f073@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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).