From: Phil Turmel <philip@turmel.org>
To: Gimpbully <gimpbully@gmail.com>
Cc: Sam Bingner <sam@bingner.com>,
"<linux-raid@vger.kernel.org>" <linux-raid@vger.kernel.org>
Subject: Re: array went wonky
Date: Fri, 03 May 2013 10:24:06 -0400 [thread overview]
Message-ID: <5183C886.5000607@turmel.org> (raw)
In-Reply-To: <91F4D0DD-926D-4337-B79C-08BA1141EF78@gmail.com>
On 05/03/2013 02:47 AM, Gimpbully wrote:
> Anyone? I'm so close I can taste it. It looks like the superblocks
> on the other disks think that sdf1 is still defined as a spare, but
> it's a ddrescue of what used to be /dev/sdc. Is there a way to
> update the superblocks?
Sorry, been busy.
Unfortunately, once a member is marked "spare", it simply doesn't know
any more what role it used to have. So "--assemble" won't get you there.
You will need to use "--create --assume-clean" or directly edit the
offending superblock.
> *Complete* output of "mdadm -E" for the array members is needed before
> any "--create" operation is attempted. Plus the distro info, kernel
> version, and mdadm version .
I would also like to see "smartctl -x" output for each underlying disk.
It would be good if we understood *why* your array "went wonky" so that
it doesn't happen again after reassembling your array. Your situation
"smells" like a timeout mismatch and/or lack of scrubbing.
Finally, in the interest of helping others help you, please don't
top-post, and *do* trim your quotes. It greatly helps when coming back
to a thread after a few days.
Phil
next prev parent reply other threads:[~2013-05-03 14:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 5:41 array went wonky Gimpbully
2013-04-13 14:20 ` Sam Bingner
2013-04-13 15:46 ` Robin Hill
2013-04-13 16:09 ` John White
2013-04-30 2:33 ` Gimpbully
2013-04-30 6:20 ` Sam Bingner
2013-04-30 14:45 ` Phil Turmel
2013-04-30 14:48 ` Gimpbully
2013-05-01 18:59 ` Gimpbully
2013-05-02 14:18 ` Gimpbully
2013-05-02 14:29 ` Gimpbully
2013-05-03 6:47 ` Gimpbully
2013-05-03 14:24 ` Phil Turmel [this message]
2013-05-03 7:40 ` Robin Hill
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=5183C886.5000607@turmel.org \
--to=philip@turmel.org \
--cc=gimpbully@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=sam@bingner.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).