From: Phil Turmel <philip@turmel.org>
To: "Peckins, Steven E" <speckins@illinois.edu>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: RAID6 recovery with 6/9 drives out-of-sync
Date: Wed, 1 Jun 2016 09:22:06 -0400 [thread overview]
Message-ID: <574EE17E.9060903@turmel.org> (raw)
In-Reply-To: <5BE0D8AF-C1BF-4DFB-BEAE-8C93898EAC87@illinois.edu>
On 06/01/2016 09:16 AM, Peckins, Steven E wrote:
> I activated the lvm volume and mounted the filesystem. Everything
> looks intact.
Yay!
> Thanks for your help recovering this array!
You're welcome.
> I had been avoiding updating mdadm while I was recovering this as I
> had read of potential issues while recovering arrays created with
> earlier versions.
Viewing bug reports and bug fix patches is the primary reason I'm
subscribed to this list. It lets me make my own stable upgrade decisions.
Phil
prev parent reply other threads:[~2016-06-01 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 2:43 RAID6 recovery with 6/9 drives out-of-sync Peckins, Steven E
2016-05-31 19:19 ` Phil Turmel
2016-06-01 11:32 ` Peckins, Steven E
2016-06-01 12:06 ` Phil Turmel
2016-06-01 13:16 ` Peckins, Steven E
2016-06-01 13:22 ` Phil Turmel [this message]
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=574EE17E.9060903@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=speckins@illinois.edu \
/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).