All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Guillaume Paumier <guillaume.paumier@gmail.com>,
	linux-raid@vger.kernel.org
Subject: Re: Offline array, events count mismatch
Date: Sun, 8 Nov 2015 22:35:13 -0500	[thread overview]
Message-ID: <56401471.2040605@turmel.org> (raw)
In-Reply-To: <1903758.3ih4aa4jR2@carbon.lepommierdujardin.fr>

Hi Guillaume,

On 11/08/2015 09:49 PM, Guillaume Paumier wrote:

[trim /]

> Looking at those event counts, my understanding is this:
> * Two of the disks (sde, sdf) were dropped from the array for some reason.
> * I didn't notice this immediately (an issue I'm addressing separately).
> * A third disk (sdj) encountered a small issue today.
> * The array went offline because it didn't have enough disks to function 
> cleanly any more.
> 
> If I understand the documentation [1] correctly, since the event count for sdj 
> is very close to the event count of sd[b,c,d,g,h,i], I should be able to re-
> assemble the array with these 7 disks using --force, leaving sde and sdf 
> aside. Once the array is assembled, I should be able to re-add sde and sdf, 
> and they will be re-sync'd.

Yes, that is the correct response.

Your situation is common.  Please see the thread this weekend started by
Franscisco Parada.

https://marc.info/?t=144691643300001&r=1&w=2&n=12

You should provide "smartctl -i -A -l scterc /dev/sdX" reports for your
drives.  If you can find an old syslog for when your two worst drives
fell out, it might help.

Phil

  reply	other threads:[~2015-11-09  3:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09  2:49 Offline array, events count mismatch Guillaume Paumier
2015-11-09  3:35 ` Phil Turmel [this message]
2015-11-10  3:05   ` Guillaume Paumier
2015-11-10 15:50     ` Phil Turmel

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=56401471.2040605@turmel.org \
    --to=philip@turmel.org \
    --cc=guillaume.paumier@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    /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.