From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: how long should "btrfs device delete missing ..." take?
Date: Fri, 12 Sep 2014 05:41:29 +0000 (UTC) [thread overview]
Message-ID: <pan$a1fc7$e248134c$125bdde4$c4a4b75e@cox.net> (raw)
In-Reply-To: 6AE06E73-C89E-42F0-9A09-FA92C68DED69@colorremedies.com
Chris Murphy posted on Thu, 11 Sep 2014 20:10:26 -0600 as excerpted:
> And then when I think about just creating a new fs, using btrfs
> send/receive, the snapshots need to be ro first.
FWIW, at this point I'd forget about send/receive and create the backup
(assuming one doesn't exist already) using more normal methods. At least
if the original send/receive hasn't yet been done, so it'd be copying off
all the data anyway. Perhaps mount selected snapshots and back them up
too (after the current case is backed up), but throw away most of the
snapshots.
Of course if there's an existing relatively current sent/received base to
build on, and no indication that send/receive is broken, definitely try
that first as the amount of data to sync in that case should be MUCH
lower, but if not...
--
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
next prev parent reply other threads:[~2014-09-12 5:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 15:22 how long should "btrfs device delete missing ..." take? Tomasz Chmielewski
2014-09-11 19:31 ` Duncan
2014-09-11 21:25 ` Chris Murphy
2014-09-11 23:51 ` Duncan
2014-09-12 2:10 ` Chris Murphy
2014-09-12 5:19 ` Russell Coker
2014-09-12 5:33 ` Duncan
2014-09-12 6:27 ` Chris Murphy
2014-09-12 5:41 ` Duncan [this message]
2014-09-12 5:59 ` Duncan
2014-09-11 23:06 ` Tomasz Chmielewski
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$a1fc7$e248134c$125bdde4$c4a4b75e@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).