From: Phil Turmel <philip@turmel.org>
To: Jared Mauch <jared@puck.nether.net>, linux-raid@vger.kernel.org
Cc: NeilBrown <neilb@suse.de>
Subject: Re: (R) in mdstat output, clean && degraded
Date: Tue, 23 Jun 2015 16:12:58 -0400 [thread overview]
Message-ID: <5589BDCA.5050801@turmel.org> (raw)
In-Reply-To: <51364598-D6AA-43E7-B9A1-C3C09255D3D4@puck.nether.net>
Hi Jared,
On 06/23/2015 02:56 PM, Jared Mauch wrote:
> I’ve been searching high and low the past few days and have been unable to diagnose what this (R) is in my raid1 mdstat output indicates.
Replacement device.
> It seems something is ‘stuck’ somehow as I’m not sure how the array is both clean and degraded at the same time.
Role '0', currently sdd1, is being replaced with sdg1. Both appear to
be working as expected and are therefore individually 'clean'. Role '1'
is missing, and therefore the array as a whole is degraded.
Looks to me like you lost a device and should have used --add to put a
new device into service, but you used --replace instead. --replace is
for use when a functioning device shows signs of failing and is to be
replaced 'on-the-fly'.
[trim /]
> Device Role : Replacement device 0
> Array State : R. ('A' == active, '.' == missing, 'R' == replacing)
However, the array doesn't seem to be making progress on the replacement
(didn't even start ?), so this pathological situation might have
triggered a bug in the resync code.
Neil?
Phil
--
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-06-23 20:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 18:56 (R) in mdstat output, clean && degraded Jared Mauch
2015-06-23 20:12 ` Phil Turmel [this message]
2015-06-23 21:21 ` Jared Mauch
2015-06-23 22:09 ` Phil Turmel
2015-06-23 22:23 ` Jared Mauch
2015-06-24 22:52 ` NeilBrown
2015-06-25 11:47 ` Jared Mauch
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=5589BDCA.5050801@turmel.org \
--to=philip@turmel.org \
--cc=jared@puck.nether.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).