From: Phil Turmel <philip@turmel.org>
To: Mikael Abrahamsson <swmike@swm.pp.se>,
Nathan Peterson <nathan@uwgrads.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Ubuntu crashed during RAID6 grow
Date: Fri, 20 Nov 2015 09:22:15 -0500 [thread overview]
Message-ID: <564F2C97.3020500@turmel.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1511200745170.24520@uplift.swm.pp.se>
On 11/20/2015 01:48 AM, Mikael Abrahamsson wrote:
> On Thu, 19 Nov 2015, Nathan Peterson wrote:
>
>> Details after the grow:
>>
>> md126 : active (auto-read-only) raid6 sdj1[2] sdl1[3] sdf1[9] sdn1[11]
>> (S) sdi1[1] sdg1[10] sde1[8] sdh1[0] sdk1[4] sdo1[12]
>>
>> Delta Devices : 1, (8->9)
>
> Please post mdadm --examine from all component drives, but I'd say if
> you try to access your data everything should be there and the grow
> should continue once the array is not auto-read-only anymore (guess from
> my side though).
Concur. There's nothing wrong with your array, and yes, mdadm knows
that it was in the middle of a --grow operation. Mount it and carry on.
Phil
prev parent reply other threads:[~2015-11-20 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 21:37 Ubuntu crashed during RAID6 grow Nathan Peterson
2015-11-20 6:48 ` Mikael Abrahamsson
2015-11-20 14: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=564F2C97.3020500@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=nathan@uwgrads.com \
--cc=swmike@swm.pp.se \
/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