From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: Patrick Tschackert <Killing-Time@gmx.de>
Cc: lists@colorremedies.com, linux-raid@vger.kernel.org
Subject: Re: problems with dm-raid 6
Date: Tue, 22 Mar 2016 00:04:56 +0100 [thread overview]
Message-ID: <20160321230456.GA16913@EIS> (raw)
In-Reply-To: <trinity-226526b2-6058-40bf-a276-9c1b47a80b3b-1458600120646@3capp-gmx-bs35>
On Mon, Mar 21, 2016 at 11:42:00PM +0100, Patrick Tschackert wrote:
> Based on your advice, I'll use an overlay on the array
Below the array. Assemble an array of overlay disks with two missing.
One of the missing disks should be that spare you synced in, because
that's one of the prime suspects... actually if it was synced to it
should not be the cause of mismatches, but if there are mismatches
then it's likely the data that was synced to it is not good.
Although RAID is able to detect mismatches, it can not tell
which is the valid data and which is the invalid data so ...
Definitely assemble without that disk and without each other
disk in turn; so for each attempt two disks missing from
your RAID-6, hopefully one of them is a bad egg and with it
gone, things will look better to btrfs than they do now.
The ultimate cause of those many mismatches remains a mystery.
Of course you can also attempt to repair btrfs directly but
if btrfs redundancy is not equal to RAID-6 then it won't be
able to fix. (I think you already cleared that point on
the btrfs mailing list and would not be asking here if
btrfs had the magic ability to recover)
Regards,
Andreas
next prev parent reply other threads:[~2016-03-21 23:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <trinity-235b76ed-571d-4615-b6f7-b4d5ed6a116d-1458509365312@3capp-gmx-bs09>
2016-03-20 21:44 ` problems with dm-raid 6 Patrick Tschackert
2016-03-20 22:37 ` Andreas Klauer
2016-03-21 12:42 ` Phil Turmel
2016-03-21 13:27 ` Andreas Klauer
2016-03-21 21:26 ` Chris Murphy
2016-03-21 21:38 ` Andreas Klauer
2016-03-21 21:46 ` Chris Murphy
2016-03-21 22:42 ` Patrick Tschackert
2016-03-21 22:54 ` Adam Goryachev
2016-03-21 23:15 ` Andreas Klauer
2016-03-21 23:48 ` Adam Goryachev
2016-03-21 23:04 ` Andreas Klauer [this message]
2016-03-22 3:53 ` Chris Murphy
2016-03-22 4:22 ` Chris Murphy
2016-03-21 22:06 Patrick Tschackert
-- strict thread matches above, loose matches on Subject: below --
2016-03-21 22:19 Patrick Tschackert
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=20160321230456.GA16913@EIS \
--to=andreas.klauer@metamorpher.de \
--cc=Killing-Time@gmx.de \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).