linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ram Ramesh <rramesh2400@gmail.com>
To: Phil Turmel <philip@turmel.org>, Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: How important is SCTERC?
Date: Fri, 28 Apr 2017 08:18:19 -0500	[thread overview]
Message-ID: <0c63781c-34e9-899a-8771-2c828a3a44f3@gmail.com> (raw)
In-Reply-To: <82b6880d-539b-81a9-08ef-1a5bc3d9752e@turmel.org>

On 04/28/2017 07:18 AM, Phil Turmel wrote:
> On 04/27/2017 11:35 PM, Ram Ramesh wrote:
>> Experts,
>>
>> I ordered a couple of 6TB drives from goHarddrive that claimed to be NAS
>> suitable, but SMART shows that they do not support
>> scterc. I want to replace two of my 3TB drives with these in mdadm
>> raid6. I can get a replacement or return, but want to avoid the hassle,
>> if I am not seious danger.
> Depends on "serious".  I would return for exchange with proper NAS
> drives.  And report the vendor for false advertising.
>
>> I do run tler.sh that sets 180s timeout for drives that do not have
>> scterc from /etc/rc.local. Am I putting my data in serious danger? I
>> only have videos and tv recordings in this md which can be replaced with
>> significant effort (about 12TB of movies and tv shows will take some
>> time to copy from my DVDs/BDs)
> The 180-second timeout is a band-aid, not a solution.  Keep in mind that
> your array will appear to be frozen for up to three minutes any time you
> have a URE.  That will have application side-effects and especially
> consequences from impatient users.
>
> Phil

I am quite unhappy with the vendor and wanted to make sure that I am not 
overreacting. Thanks. I have started the return process. Hopefully, that 
is all there is to it.

Ramesh


  reply	other threads:[~2017-04-28 13:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28  3:35 How important is SCTERC? Ram Ramesh
2017-04-28 12:18 ` Phil Turmel
2017-04-28 13:18   ` Ram Ramesh [this message]
2017-04-28 13:07 ` Peter Grandi
2017-04-29 23:45   ` Ram Ramesh

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=0c63781c-34e9-899a-8771-2c828a3a44f3@gmail.com \
    --to=rramesh2400@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).