From: Hannes Reinecke <hare@suse.de>
To: Chris Murphy <lists@colorremedies.com>, linux-raid@vger.kernel.org
Subject: Re: URE, link resets, user hostile defaults
Date: Tue, 28 Jun 2016 08:33:43 +0200 [thread overview]
Message-ID: <57721A47.8070203@suse.de> (raw)
In-Reply-To: <CAJCQCtT1qi1yLjE3Lor3ScVJx7aX4A_S_iM_=VhDtDCD_C9uqw@mail.gmail.com>
On 06/27/2016 06:42 PM, Chris Murphy wrote:
> Hi,
>
> Drives with SCT ERC not supported or unset, result in potentially long
> error recoveries for marginal or bad sectors: upwards of 180 second
> recovers are suggested.
>
> The kernel's SCSI command timer default of 30 seconds, i.e.
>
> cat /sys/block/<dev>/device/timeout
>
> conspires to undermine the deep recovery of most drives now on the
> market. This by default misconfiguration results in problems list
> regulars are very well aware of. It affects all raid configurations,
> and even affects the non-RAID single drive use case. And it does so in
> a way that doesn't happen on either Windows or macOS. Basically it is
> linux kernel induced data loss, the drive very possibly could present
> the requested data upon deep recovery being permitted, but the
> kernel's command timer is reached before recovery completes, and
> obliterates any possibility of recovering that data. By default.
>
> This now seems to affect the majority of use cases. At one time 30
> seconds might have been sane for a world with drives that had less
> than 30 second recoveries for bad sectors. But that's no longer the
> case.
>
'Majority of use cases'.
Hardly. I'm not aware of any issues here.
The problem with SCT ERC (or TLER or whatever the currrent acronym of
the day is called) is that it's a non-standard setting, where every
vendor basically does its own thing.
Plus you can only influence this on higher end-disks; on others you are
at the mercy of the drive firmware, hoping you got the timeout right.
Can you post a message log detailing this problem?
We surely have ways of influencing the timeout, but first we need to
understand what actually is happening.
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
--
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
next prev parent reply other threads:[~2016-06-28 6:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 16:42 URE, link resets, user hostile defaults Chris Murphy
2016-06-28 6:33 ` Hannes Reinecke [this message]
2016-06-28 17:33 ` Chris Murphy
2016-06-28 18:28 ` Phil Turmel
2016-06-28 20:46 ` Wols Lists
2016-06-28 22:17 ` Chris Murphy
2016-06-29 6:01 ` Hannes Reinecke
2016-06-29 10:48 ` Pasi Kärkkäinen
2016-06-29 12:17 ` Zygo Blaxell
2016-06-29 18:16 ` Edward Kuns
2016-07-01 20:43 ` Chris Murphy
2016-07-04 6:00 ` Hannes Reinecke
2016-07-04 21:43 ` Pasi Kärkkäinen
2016-08-19 10:00 ` Pasi Kärkkäinen
2016-08-19 12:36 ` Phil Turmel
2016-08-19 15:30 ` Chris Murphy
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=57721A47.8070203@suse.de \
--to=hare@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.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 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).