From: Kai Krakow <hurikhan77+btrfs@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Recovery advice
Date: Mon, 05 Aug 2013 01:05:21 +0200 [thread overview]
Message-ID: <ha33da-ecm.ln1@hurikhan77.spdns.de> (raw)
In-Reply-To: pan$b7e2c$bf7f3666$af6e4a6$909b9d97@cox.net
Duncan <1i5t5.duncan@cox.net> schrieb:
>> It is a RAID-1 so why bother with the faulty drive? Just wipe it, put it
>> back in, then run a btrfs balance... There should be no data loss
>> because all data is stored twice (two-way mirroring).
>
> The caveat would be if it didn't start as btrfs raid1, and there's still
> some data (or possibly metadata if it was the single drive at one point
> or they're ssds, as btrfs defaults to metadata single in ssd mode) that
> hasn't been duped elsewhere.
Oh... That's actually a pitfall... :-\
Note to myself: Ensure balance has been run successfully and completely.
next prev parent reply other threads:[~2013-08-04 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 20:31 Recovery advice Sandy McArthur
2013-08-04 12:41 ` Kai Krakow
2013-08-04 22:19 ` Duncan
2013-08-04 23:05 ` Kai Krakow [this message]
2013-08-05 15:44 ` Sandy McArthur
2013-08-04 23:13 ` Chris Murphy
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=ha33da-ecm.ln1@hurikhan77.spdns.de \
--to=hurikhan77+btrfs@gmail.com \
--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).