From: Valentijn Sessink <v@lentijn.sess.ink>
To: Matt Callaghan <matt_callaghan@sympatico.ca>, linux-raid@vger.kernel.org
Subject: Re: mdadm RAID6 "active" with spares and failed disks; need help
Date: Mon, 12 Jan 2015 00:22:26 +0100 [thread overview]
Message-ID: <54B305B2.6000702@lentijn.sess.ink> (raw)
In-Reply-To: <BLU437-SMTP96782B2C74C634FDED13D681420@phx.gbl>
Hi Matt,
I'm by no means a specialist, but I have been saving a few arrays
lately, so here's my 2 cents. From what I see, I'd say you're almost
there, but you didn't use "--bitmap=none" in your create-statement and
as far as I can see, there is no bitmap specified in the original raid
blocks but there is one in the newly created one. I may be wrong
though!, please take my advice with a grain of salt and at your own risk.
Also, I would not have dared to run all these statements on "live" (or
dead, for that matter ;-) disks. See my posting (that is unfinished, but
I'll add info as I have time) at
http://valentijn.sessink.nl/?p=557 where I use "dmsetup" to create a few
virtual disks - all writes are redirected to another device. Fun thing
is, that after that, you can mess up all you want. You just remove the
virtual disk and poof, everything is as it was before (failed raid and
all, isn't that funny? :)
I hope this helps.
Best regards,
Valentijn
On 11-01-15 21:26, Matt Callaghan wrote:
> Updating this e-mail thread. I got the latest mdadm version that
> supports data offset variance per device and attempted to reconstruct
> RAID6 according to previous data, but so far no luck.
> As far as I a can tell (sadly), all of my data is lost. I've updated the
> forum thread with the final details and failures.
> http://www.linuxquestions.org/questions/linux-server-73/mdadm-raid6-active-with-spares-and-failed-disks%3B-need-help-4175530127/
--
✉ v@lentijn.sess.ink ☏ +31777777713 (31 7x7 13)
⌂ durgerdamstraat 29 zaandam
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-01-11 23:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54ABEE54.6020707@sympatico.ca>
2015-01-07 13:34 ` mdadm RAID6 "active" with spares and failed disks; need help Matt Callaghan
2015-01-11 20:26 ` Matt Callaghan
2015-01-11 23:22 ` Valentijn Sessink [this message]
2015-01-12 16:35 ` Wols Lists
2015-01-21 0:34 ` Matt Callaghan
2015-01-22 9:47 ` Valentijn
2015-03-27 23:48 ` Matt Callaghan
2015-03-28 1:59 ` Phil Turmel
2015-03-28 10:11 ` Roman Mamedov
2015-03-28 15:11 ` Read-only mounts (was mdadm RAID6 "active" with spares and failed disks; need help) Phil Turmel
[not found] ` <55161943.1090206@sympatico.ca>
[not found] ` <BLU436-SMTP135A84B36120ACD11B2783D81F70@phx.gbl>
2015-03-28 17:40 ` mdadm RAID6 "active" with spares and failed disks; need help Phil Turmel
2015-01-06 14:16 Matt Callaghan
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=54B305B2.6000702@lentijn.sess.ink \
--to=v@lentijn.sess.ink \
--cc=linux-raid@vger.kernel.org \
--cc=matt_callaghan@sympatico.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.