From: "Michał Sawicz" <michal@sawicz.net>
To: Phil Turmel <philip@turmel.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Help with data recovery - RAID6 with 2 failed drives and another with broken sectors
Date: Mon, 07 Oct 2013 00:56:25 +0200 [thread overview]
Message-ID: <5251EA99.60208@sawicz.net> (raw)
In-Reply-To: <5251E0FA.2030206@turmel.org>
On 07.10.2013 00:15, Phil Turmel wrote:
> No, just fix the timeouts. Otherwise, you'll be kicking drives out
> *way* more often than you think.
Ah! Now I've actually read through some of the finds (and found dozens
of instances where you recommend the same - you *should* have a dime for
every time you mention that to people), I'm happy to report that just
one of my drives (at least from what they claim) does not support scterc
- the rest just had it disabled... This is fixed now, and a brand new
udev rule should take care of the timeout for the other drive. This
should make my array way more stable - thank you so much!
> Do check your smartctl reports for actual relocations, though. In my
> experience, once you pass single digits, further failures are rapid.
Smartd is notifying me of all such - and since most of the drives are
still under warranty - I replace them as soon as possible when they
start to show up bad blocks.
Again, thank you Phil for your patience.
--
Michał (Saviq) Sawicz <michal@sawicz.net>
--
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
prev parent reply other threads:[~2013-10-06 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 23:23 Help with data recovery - RAID6 with 2 failed drives and another with broken sectors Michał Sawicz
2013-10-01 19:24 ` Michał Sawicz
2013-10-06 21:44 ` Phil Turmel
2013-10-06 22:11 ` Michał Sawicz
2013-10-06 22:15 ` Phil Turmel
2013-10-06 22:56 ` Michał Sawicz [this message]
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=5251EA99.60208@sawicz.net \
--to=michal@sawicz.net \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox