From: Brian Candler <b.candler@pobox.com>
To: peter@steinhoff.se
Cc: linux-raid@vger.kernel.org
Subject: Re: Problem diagnosing rebuilding raid5 array
Date: Tue, 15 Oct 2013 15:20:30 +0100 [thread overview]
Message-ID: <525D4F2E.50604@pobox.com> (raw)
In-Reply-To: <20131015101442.19647jupyxo6848w@phobos.elinuxservers.com>
On 15/10/2013 15:14, peter@steinhoff.se wrote:
> Thanks Brian.
>
> Yes, I replaced sdh because it showed read errors in dmesg and was
> kicked out of the array.
>
> But has the new sdh been rebuilt completely? If that case there should
> be n-1 drives? Or does "spare" just means that it can be used but has
> no data yet?
>
That's what I'm not sure about. It is "clean" but it is also "spare".
I'm not sure what state would be seen while it is rebuilding.
When the old sdh had a problem, did you mdadm /dev/mdXXX --fail /dev/sdh?
And after you inserted the new drive, and presumably did mdadm
/dev/mdXXX --add /dev/sdh, did you see it start to rebuild in /proc/mdstat?
> Also I have my old sdh with data on it but I don't know how current
> that data is but perhaps I can use that somehow?
>
You could mdadm --examine it, but I suspect that the event count will be
way out of line by now.
next prev parent reply other threads:[~2013-10-15 14:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 16:31 Problem diagnosing rebuilding raid5 array peter
2013-10-14 17:28 ` Brian Candler
2013-10-15 12:40 ` peter
2013-10-15 12:50 ` Brian Candler
2013-10-15 14:20 ` peter
2013-10-15 13:15 ` Brian Candler
2013-10-15 14:14 ` peter
2013-10-15 14:20 ` Brian Candler [this message]
2013-10-15 15:01 ` peter
2013-10-15 15:04 ` Brian Candler
2013-10-16 6:11 ` NeilBrown
2013-10-17 2:27 ` peter
2013-10-17 2:39 ` NeilBrown
2013-10-18 2:41 ` peter
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=525D4F2E.50604@pobox.com \
--to=b.candler@pobox.com \
--cc=linux-raid@vger.kernel.org \
--cc=peter@steinhoff.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 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.