Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Anthonys Lists <antlists@youngman.org.uk>
To: Hans Malissa <hmalissa@me.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID1 degraded
Date: Tue, 04 Aug 2015 15:38:39 +0100	[thread overview]
Message-ID: <55C0CE6F.20600@youngman.org.uk> (raw)
In-Reply-To: <14A646FC-54F8-4A2E-978D-49800FB534CF@me.com>

On 04/08/2015 06:55, Hans Malissa wrote:
> Thanks a lot for your help!
> Rebooting the system didn’t solve the problem, /dev/sdc is still nowhere to be found.
> So I will have to replace /dev/sdc.
> I tried to learn a bit about SRC/ERC from list archives, and it seems like my hard drives (1TB Seagate Barracuda’s) don’t support this option:
>
> # smartctl -l scterc /dev/sdb
> smartctl 6.0 2012-10-10 r3643 [x86_64-linux-3.7.10-1.45-desktop] (SUSE RPM)
> Copyright (C) 2002-12, Bruce Allen, Christian Franke,www.smartmontools.org
>
> SCT Error Recovery Control command not supported
I've got Seagate Barracudas (the 3TB version) and was a bit miffed to 
realise that they didn't support this. That said, with mirrored 1TB 
drives, you shouldn't have any real problems with SRC/ERC - the problem 
is that a drive that returns 1 error per 10TB read is within spec, if 
your array is over that size, then "good" drives could well cause a 
crashed array if you have any glitches. (It seems that most drives are 
well over spec, but why run the risk).

If you're price-conscious, WD Reds are not much more expensive than 
Barracudas, and are advertised as "good for RAID". I'm looking at them 
for my next hard drives.

Cheers,
Wol
--
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:[~2015-08-04 14:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 22:18 RAID1 degraded Hans Malissa
2015-08-03 23:48 ` Adam Goryachev
2015-08-04  4:16   ` Hans Malissa
2015-08-04  4:33     ` Adam Goryachev
2015-08-04  5:55       ` Hans Malissa
2015-08-04 14:38         ` Anthonys Lists [this message]
2015-08-04 15:56         ` Robert L Mathews
     [not found]       ` <A5793A94-EC9B-4221-A420-9E39EF0ABEEC@me.com>
2015-08-04  6:02         ` Adam Goryachev

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=55C0CE6F.20600@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=hmalissa@me.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