From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: Chris Murphy <lists@colorremedies.com>
Cc: Phil Turmel <philip@turmel.org>,
Patrick Tschackert <Killing-Time@gmx.de>,
linux-raid@vger.kernel.org
Subject: Re: problems with dm-raid 6
Date: Mon, 21 Mar 2016 22:38:29 +0100 [thread overview]
Message-ID: <20160321213829.GA16677@EIS> (raw)
In-Reply-To: <CAJCQCtQDWdZPBvB1Q2Mh_AOBZpWSPoqK42meWvARhQi3hE5uzw@mail.gmail.com>
On Mon, Mar 21, 2016 at 03:26:30PM -0600, Chris Murphy wrote:
> At this point I'm skeptical this will work. Also, I'm not familiar
> with this overlay technique. I did look at the URL provided by
> Andreas, my concern is whether it's possible for the volume UUID to
> appear more than once to the kernel?
Thanks for pointing out this issue, I'm not familiar with btrfs at all.
Normally this would be a problem and you'd have to find some way
to change the UUID in the overlay or whatever, but if it's LUKS
encrypted that should solve the problem nicely, you just have to
stop the original RAID and close the original LUKS container
and then only open the one of the overlay.
You should not assemble the original RAID anymore anyhow, anything
you write to the array at this point will likely only increase
damages. The overlay allows you to experiment in read-"write"
mode without actually changing anything on your disks.
> The issue is raid6 assembly somehow being wonky.
> But at this point we need to hear back from Patrick.
Yes, it's quite a mystery, I hope the OP can shed some light on
what might have caused this.
Regards
Andreas Klauer
next prev parent reply other threads:[~2016-03-21 21:38 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 [this message]
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
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=20160321213829.GA16677@EIS \
--to=andreas.klauer@metamorpher.de \
--cc=Killing-Time@gmx.de \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=philip@turmel.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).