All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Jared Mauch <jared@puck.nether.net>
Cc: linux-raid@vger.kernel.org, NeilBrown <neilb@suse.de>
Subject: Re: (R) in mdstat output, clean && degraded
Date: Tue, 23 Jun 2015 18:09:28 -0400	[thread overview]
Message-ID: <5589D918.9000401@turmel.org> (raw)
In-Reply-To: <F30009F6-7BF5-4786-A3A6-04C5C49B8E0C@puck.nether.net>

On 06/23/2015 05:21 PM, Jared Mauch wrote:
> Let me know what debugging/details might be interesting to collect.  

A good sequence of events (from bash history perhaps) with corresponding
log messages is always helpful.  Your initial report was pretty good.

> Based on the Events# being in-sync, I am going to assume that the drives
> may be operating in a protected-type mode even if the output doesn’t
> concur.

I think that's unlikely.  In replace, one drive responds for sectors
below the progress mark, and the other drive responds for sectors above it.

> I can say this state seems to survive reboots.

That suggests you give a vanilla (or near-vanilla) kernel a try with one
of the various liveCDs that have them.  I personally find the one from
sysrescuecd.org to be most convenient, but I'm a gentoo guy :-)

Otherwise, consider adding a third drive to see if it will rebuild and
break the deadlock.

I should have to say, but I hope you have a backup :-)

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

  reply	other threads:[~2015-06-23 22:09 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
2015-06-23 21:21   ` Jared Mauch
2015-06-23 22:09     ` Phil Turmel [this message]
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=5589D918.9000401@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 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.