linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guillaume Betous <guillaume.betous@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: RAID 5 : recovery after failure
Date: Wed, 9 Oct 2013 10:54:09 +0200	[thread overview]
Message-ID: <CAPbD+Ret3-2M1ir=0G5YP9VdGBptMAPLzCZRFga0jjv0Y6aEhQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1310091022560.20065@uplift.swm.pp.se>

Here is the 2nd message I received.
For now my RAID has restarted with only sdc, sde and sdf.

I don't know if /dev/sdb is still usable, or if this was only a
desynchro failure.
How to know ?

------------------------------------------------------------------------------------------

This is an automatically generated mail message from mdadm
running on sam

A FailSpare event had been detected on md device /dev/md127.

It could be related to component device /dev/sdb1.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md127 : active raid5 sde1[2] sdb1[5](F) sdc1[0](F) sdd1[6] sdf1[4]
      5860535808 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/2] [__UU]
      [============>........]  recovery = 62.0%
(1212358192/1953511936) finish=854.7min speed=14451K/sec

2013/10/9 Mikael Abrahamsson <swmike@swm.pp.se>:
> On Wed, 9 Oct 2013, Guillaume Betous wrote:
>
>> Now, should I add the other drives ? How ?
>
>
> Depends on what the problem is.
>
> Is the initial drive that failed now totally unusable?
>
> In that case, just do mdadm --manage /dev/md0 --add /dev/sd<whatever> with a
> new drive.
>
> But you said you received a second error, was this a read error on one of
> good working drive (see other threads in archive) and so you don't have any
> read errors (the information on those bad sectors will now be lost), then
> you can resync properly.
>
> I strongly recommend going to RAID6 to solve this problem in the future.
>
> I recommend having
>
> for x in /sys/block/sd[a-z] ; do echo 180 > $x/device/timeout ; done
>
> in rc.local (or equivalent) to make sure you can handle timeouts properly
> even for consumer drives.
>
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se



-- 
Pour la santé de votre ordinateur, préférez les logiciels libres.
Lire son mail : http://www.mozilla-europe.org/fr/products/thunderbird/
Browser le web : http://www.mozilla-europe.org/fr/products/firefox/
Suite bureautique : http://www.libreoffice.org/download/
--
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:[~2013-10-09  8:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 19:19 RAID 5 : recovery after failure Guillaume Betous
2013-10-08 21:06 ` Robin Hill
2013-10-09  6:22   ` Guillaume Betous
2013-10-09  6:54     ` Mikael Abrahamsson
2013-10-09  8:20       ` Guillaume Betous
2013-10-09  8:28         ` Mikael Abrahamsson
2013-10-09  8:54           ` Guillaume Betous [this message]
2013-10-09  9:14             ` 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='CAPbD+Ret3-2M1ir=0G5YP9VdGBptMAPLzCZRFga0jjv0Y6aEhQ@mail.gmail.com' \
    --to=guillaume.betous@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=swmike@swm.pp.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 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).