All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Priya Kamala <priya.kamala@perpetual-data.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Query regarding disk failure
Date: Wed, 10 Jul 2013 11:22:20 -0400	[thread overview]
Message-ID: <51DD7C2C.2080901@turmel.org> (raw)
In-Reply-To: <51DD79B4.3000102@perpetual-data.com>

On 07/10/2013 11:11 AM, Priya Kamala wrote:
> 
> On 10/07/2013 15:51, Phil Turmel wrote:
>> You haven't actually told us whether it is turned on.  Desktop drives
>> that support it don't have it enabled by default.  Please show "smartctl
>> -l scterc /dev/sdX" for each of your drives.
> I don't have access to the original system right now. This is the output
> from the another system with the same drive type. All the drives show
> the same output, so I'm including only one. The drives are Seagate
> Barracuda ES.2 Model ST31000340NS.

Ok, enterprise drives.  ERC is on by default.

> -bash-4.1# smartctl -l scterc /dev/sda
> smartctl 5.43 2012-06-30 r3573 [i686-linux-3.2.40] (local build)
> Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
> 
> SCT Error Recovery Control:
>            Read:    100 (10.0 seconds)
>           Write:    100 (10.0 seconds)

Did you have an idea of number of read error events?  "Pending" sector
counts on the problem drive might be a useful number to report.  (Or
just report complete output of "smartctl -x" for each drive.)

Meanwhile, what distro, kernel, and mdadm versions are involved here?

Phil


  reply	other threads:[~2013-07-10 15:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10 12:09 Query regarding disk failure Priya Kamala
2013-07-10 13:11 ` Robin Hill
2013-07-10 14:17   ` Priya Kamala
2013-07-10 14:51     ` Phil Turmel
2013-07-10 15:11       ` Priya Kamala
2013-07-10 15:22         ` Phil Turmel [this message]
2013-07-10 15:45           ` Priya Kamala
2013-07-10 17:30             ` Phil Turmel
2013-07-10 17:47 ` Mikael Abrahamsson

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=51DD7C2C.2080901@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=priya.kamala@perpetual-data.com \
    /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.