From: Wols Lists <antlists@youngman.org.uk>
To: bishop@latech.edu, linux-raid@vger.kernel.org
Subject: Re: raid5 messed up
Date: Thu, 7 Sep 2017 16:29:49 +0100 [thread overview]
Message-ID: <59B165ED.406@youngman.org.uk> (raw)
In-Reply-To: <6e5083a4-609b-daba-3326-0dbd9dda6c34@email.latech.edu>
On 07/09/17 14:33, Thomas C. Bishop wrote:
> I see what you mean... seems it would be simple enough to find this
> spec. but not clear if supported or not.
> Seagate claims this is a "best fit applications" drive for High-Capacity
> RAID storage but never lists ERC as feature.
> http://www.seagate.com/files/www-content/partners/my%20spp%20dashboard/learn/en-us/docs/storage-solutions-guide-jul-2013-ssg1351-13-1307us.pdf
>
> pg 30 of the brochure.
>
> elsewhere@seagate I read ERC is a subset of the smart control commands
> which are supported on this drive so one _might_ think it's supported.
>
> FYI: smartctl --xall doesn't provide an answer either.
> closest it comes is
> SMART support is: Available - device has SMART capability.
My Barracudas explicitly say SMART is available (disabled by default on
power-up :-(, and ERC is not available. Yours mentions neither ERC, nor
the error timeout, so something's weird somewhere ... quite possibly the
drive can do it, but it's badly documented and the smartctl authors
don't know the magic incantation ... :-)
Or, like the Barracudas have a long timeout hard encoded, possibly the
Constellations have a short timeout hard encoded.
Cheers,
Wol
next prev parent reply other threads:[~2017-09-07 15:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 20:15 raid5 messed up Thomas C. Bishop
2017-09-01 22:47 ` Anthony Youngman
2017-09-02 0:24 ` Andreas Klauer
2017-09-06 23:00 ` Thomas C. Bishop
2017-09-05 3:55 ` Phil Turmel
2017-09-06 23:47 ` Thomas C. Bishop
2017-09-07 0:17 ` Wols Lists
2017-09-07 13:33 ` Thomas C. Bishop
2017-09-07 15:29 ` Wols Lists [this message]
2017-09-07 15:40 ` Thomas C. Bishop
2017-09-08 20:10 ` Weedy
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=59B165ED.406@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=bishop@latech.edu \
--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 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.