From: Graham Fleming <graham.fleming@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: RE: Scrubbing with BTRFS Raid 5
Date: Tue, 21 Jan 2014 10:03:26 -0800 [thread overview]
Message-ID: <DC8CDADE-5C7A-4DA3-8081-EB631136621B@gmail.com> (raw)
Thanks again for the added info; very helpful.
I want to keep playing around with BTRFSS RAID 5 and testing with it... assuming I have a drive with bad blocks, or let's say some inconsistent parity am I right in assuming that a) a btrfs scrub operation will not fix the stripes with bad parity and b) a balance operation will not be successful? Or would a balance operation work to re-write parity?
next reply other threads:[~2014-01-21 18:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 18:03 Graham Fleming [this message]
2014-01-22 15:39 ` Scrubbing with BTRFS Raid 5 Duncan
-- strict thread matches above, loose matches on Subject: below --
2014-01-21 9:06 Graham Fleming
2014-01-21 17:08 ` Duncan
2014-01-21 17:18 ` Jim Salter
2014-01-21 17:38 ` Chris Murphy
2014-01-21 18:25 ` Jim Salter
2014-01-22 16:02 ` Duncan
2014-01-22 20:45 ` Chris Mason
2014-01-22 21:06 ` ronnie sahlberg
2014-01-22 21:16 ` Chris Mason
2014-01-22 22:36 ` ronnie sahlberg
2014-01-20 0:53 Graham Fleming
2014-01-20 13:21 ` Duncan
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=DC8CDADE-5C7A-4DA3-8081-EB631136621B@gmail.com \
--to=graham.fleming@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