All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Smith <andy@strugglers.net>
To: linux-raid@vger.kernel.org
Subject: Re: SSD based sw RAID: is ERC/TLER really important?
Date: Sat, 24 Jul 2021 20:21:52 +0000	[thread overview]
Message-ID: <20210724202151.4dbct2qeyua4g55d@bitfolk.com> (raw)
In-Reply-To: <2232919.g0K5C1TF2C@chirone>

Hi Gianluca,

On Sat, Jul 24, 2021 at 08:41:06PM +0200, Gianluca Frustagli wrote:
> But in the case of SSD drives (where, possibly, the error recovery activities 
> performed by the drive firmware are very fast) does the presence of the 
> ERC/TLER capability really matter?

If the setting is there, why wouldn't you use it? If the error
recovery is always very fast, as you hypothesise, then the low
timeout you set with smartctl -l scterc will never be reached
anyway.

> Is the same scenario from the spinning 
> drives case actually even probable or only theorical? 

I don't know what the typical error recovery behaviour of an SSD is
because in years and years I haven't seen such problems with SSDs,
but where they offer the scterc setting I do use it anyway on the
basis of it's not going to hurt anything.

I see it available on enterprise SSD like Samsung SM883, Intel
D3-S4610. I don't see it on Supermicro DOM modules.

I also don't see it on NVMe drives at all (e.g. Samsung PM983), and
NVMe seems to be the future of flash so maybe this setting dies
soon…

Cheers,
Andy

      parent reply	other threads:[~2021-07-24 20:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-24 18:41 SSD based sw RAID: is ERC/TLER really important? Gianluca Frustagli
2021-07-24 20:19 ` Peter Grandi
2021-07-24 21:45   ` Phil Turmel
2021-07-25  7:00     ` Wols Lists
2021-07-25 10:28     ` Peter Grandi
2021-07-26  1:06       ` Phil Turmel
2021-07-26  7:57         ` Peter Grandi
2021-07-26 16:12           ` Peter Grandi
2021-07-25 11:04     ` Peter Grandi
2021-07-24 20:21 ` Andy Smith [this message]

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=20210724202151.4dbct2qeyua4g55d@bitfolk.com \
    --to=andy@strugglers.net \
    --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.