All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: bobzer <bobzer@gmail.com>, Anthonys Lists <antlists@youngman.org.uk>
Cc: linux-raid <linux-raid@vger.kernel.org>,
	Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: raid 5 crashed
Date: Tue, 31 May 2016 09:45:51 -0400	[thread overview]
Message-ID: <574D958F.8060209@turmel.org> (raw)
In-Reply-To: <CADzS=arbwpZg=VRcaiLaMJrLzr8pOjFTC-EwUtSpC1A3SmaTcQ@mail.gmail.com>

On 05/30/2016 06:00 PM, bobzer wrote:
> I did follow his advice for the smartctl i can't right now but i will
> post the output
> my drives are desktop grade normal seagate, not NAS nor entreprise so
> i will retry but i will limit the speed of reconstruction with :
> echo 40000 > /proc/sys/dev/raid/speed_limit_max
> echo 1000 > /proc/sys/dev/raid/speed_limit_min
> I hope that it will permit to finish the rebuilding

No, that is unlikely to help.  You need to read about "timeout mismatch"
as you clearly have a bad case of it.  This is not a new issue, as you
can see from the dates of the following:

http://marc.info/?l=linux-raid&m=139050322510249&w=2
http://marc.info/?l=linux-raid&m=135863964624202&w=2
http://marc.info/?l=linux-raid&m=135811522817345&w=1
http://marc.info/?l=linux-raid&m=133761065622164&w=2
http://marc.info/?l=linux-raid&m=132477199207506
http://marc.info/?l=linux-raid&m=133665797115876&w=2
http://marc.info/?l=linux-raid&m=142487508806844&w=3
http://marc.info/?l=linux-raid&m=144535576302583&w=2

  reply	other threads:[~2016-05-31 13:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 21:28 raid 5 crashed bobzer
2016-05-11 12:09 ` Mikael Abrahamsson
2016-05-11 13:15 ` Robin Hill
2016-05-26  3:06   ` bobzer
2016-05-27 19:19     ` bobzer
2016-05-30 15:01       ` bobzer
2016-05-30 19:04         ` Anthonys Lists
2016-05-30 22:00           ` bobzer
2016-05-31 13:45             ` Phil Turmel [this message]
2016-05-31 18:49               ` Wols Lists
2016-06-01  1:48                 ` Brad Campbell
2016-06-01  3:46                   ` Edward Kuns
2016-06-01  4:07                     ` Brad Campbell
2016-06-01  5:23                       ` Edward Kuns
2016-06-01  5:28                         ` Brad Campbell
2016-06-01 15:36                       ` Wols Lists
2016-06-01 23:15                         ` Brad Campbell
2016-06-02  5:52                           ` Mikael Abrahamsson
2016-06-02 14:01                           ` Wols Lists
2016-06-02 15:27                             ` Andreas Klauer
2016-06-03  1:05                             ` Brad Campbell
2016-06-03  7:52                               ` Mikael Abrahamsson
2016-06-03 15:27                                 ` bobzer
2016-06-03 16:31                                   ` Sarah Newman
2016-06-04  2:56                                     ` bobzer
2016-06-01 15:42                   ` Wols Lists
2016-06-01 17:28                     ` 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=574D958F.8060209@turmel.org \
    --to=philip@turmel.org \
    --cc=antlists@youngman.org.uk \
    --cc=bobzer@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 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.