Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: Tim Bock <jtbock@daylight.com>
Cc: Goswin von Brederlow <goswin-v-b@web.de>, linux-raid@vger.kernel.org
Subject: Re: Question about raid robustness when disk fails
Date: Mon, 25 Jan 2010 18:51:25 +0100	[thread overview]
Message-ID: <87636qqdia.fsf@frosties.localdomain> (raw)
In-Reply-To: <1264436547.3015.24.camel@kije> (Tim Bock's message of "Mon, 25 Jan 2010 09:22:27 -0700")

Tim Bock <jtbock@daylight.com> writes:

> Thank you for the response.  Through the smartctl tests, I noticed that
> the "seek error rate" value for the misbehaving disk was at 42, with the
> threshold at 30.  For other disks in the same array, the "seek error
> rate" values were up around 75 (same threshold of 30).  As it seems the
> values decrement to the threshold, I took that as a further sign that
> the disk was in trouble and replaced it.  Any likely correlation between
> the described problem and the "seek error rate" value?

Always keep in mind that smart values are often random, fictional or
garbage. I have disks that have an airflow temperature (outside) of 80+
and temperature (inside) of 50+. Both going down as the disk heats up
from use.

The only values I would keep a close eye on is remapped sectors and
pending sectors. Anything else gives nice graphs but I always feel is
totaly useless. And even the pending sectors are != 0 on one drive while
badblocks reports no errors on repeated passes. The drive just doesn't
seem to reduce the count when it successfully remaps a sector.

MfG
        Goswin

  reply	other threads:[~2010-01-25 17:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08 17:39 Question about raid robustness when disk fails Tim Bock
2010-01-22 16:32 ` Goswin von Brederlow
2010-01-25 16:22   ` Tim Bock
2010-01-25 17:51     ` Goswin von Brederlow [this message]
2010-01-25 18:12       ` Michał Sawicz
2010-01-26  7:29         ` Goswin von Brederlow
2010-01-27  0:19   ` Ryan Wagoner
2010-01-27  4:22     ` Michael Evans
2010-01-27  9:04       ` Goswin von Brederlow
2010-01-27  9:22         ` Asdo
2010-01-27 10:25           ` Goswin von Brederlow
2010-01-27 10:43             ` Asdo
2010-01-27 15:34               ` Goswin von Brederlow
2010-01-28 11:52                 ` Michael Evans
2010-01-27 15:15     ` Tim Bock

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=87636qqdia.fsf@frosties.localdomain \
    --to=goswin-v-b@web.de \
    --cc=jtbock@daylight.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox