All of lore.kernel.org
 help / color / mirror / Atom feed
From: joystick <joystick@shiftmail.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: 3TB drives failure rate
Date: Sun, 28 Oct 2012 22:59:47 +0100	[thread overview]
Message-ID: <508DAAD3.4050209@shiftmail.org> (raw)
In-Reply-To: <46B8932A-58A5-4C1A-9C8C-DCCD5D3A1CD9@colorremedies.com>

On 10/28/12 21:34, Chris Murphy wrote:
> Anyway, the idea mdadm users can't benefit from shorter ERC is untrue. 
> They certainly can. But the open question is why would they be getting 
> such long error recovery times in the first place? 7 seconds is a long 
> time. 2 minutes is a WTF moment. 

Totally agreed that 7 seconds is a way way too long time already.
Suppose the user is reading a 5MB file in a 5 disks array, that's 
(approximately) 1MB from each disk.
Suppose that in one disk you are hitting a bad area where all sectors 
are unreadable: that's a 256-sectors sequence of 7 seconds waits, that 
means HALF AN HOUR wait!
it's total nonsense

I have tried to set ERC to lower values than 7 on Hitachi drives, and 
maybe AFAIR also on WD RE, but none of the two allowed values lower 
than, IIRC, 6.0 seconds . Which is strange because the smart command 
wants 2 digits, expressed in deciseconds, so I would expect to be able 
to set the ERC to 0.1 seconds which is definitely not possible.

Any comments would be appreciated.

What Linux needs to address this feature imho is the ability to 
configure the failure actions. If the drive does not respond within 1 
second, I want the SCSI command to be aborted, device RESET, bus RESET 
or whatever (without the drive dropping out of the controller if 
possible), then an error to be returned to MD so that it starts the 
sector rewrite and goes on immediately. Do you think this would be 
possible or it would puzzle the drive?

  parent reply	other threads:[~2012-10-28 21:59 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-28 12:15 3TB drives failure rate Rainer Fügenstein
2012-10-28 12:19 ` Mathias Burén
2012-10-28 12:49   ` John Robinson
2012-10-28 12:54 ` Michael Tokarev
2012-10-28 16:47 ` Ed W
2012-10-28 17:05   ` Joe Landman
2012-10-28 22:12     ` joystick
2012-10-28 22:24       ` Miles Fidelman
2012-10-28 23:59         ` joystick
2012-10-29  0:09           ` Miles Fidelman
2012-10-29  4:29             ` Roman Mamedov
2012-10-29  7:54               ` David Brown
2012-10-29 13:02                 ` Phil Turmel
2012-10-30 23:54                   ` 3TB drives failure rate (summary) Rainer Fügenstein
2012-10-31 12:35                     ` Phil Turmel
2012-11-01 15:13                       ` Miles Fidelman
2012-11-01 15:24                         ` John Robinson
2012-11-01 15:39                           ` Miles Fidelman
2012-11-01 16:05                             ` John Robinson
2012-11-01 16:25                               ` Miles Fidelman
2013-02-05 17:43                       ` Adam Goryachev
2013-02-05 18:08                         ` Roy Sigurd Karlsbakk
2013-02-05 20:34                         ` Wolfgang Denk
2012-10-29 13:26               ` 3TB drives failure rate Miles Fidelman
2012-10-28 19:50 ` Chris Murphy
2012-10-28 19:59   ` Roman Mamedov
2012-10-28 20:10     ` Chris Murphy
2012-10-28 20:16       ` Roman Mamedov
2012-10-28 20:34         ` Chris Murphy
2012-10-28 20:49           ` Roman Mamedov
2012-10-28 20:59             ` Chris Murphy
2012-10-28 21:07               ` Miles Fidelman
2012-10-28 20:50           ` Chris Murphy
2012-10-28 21:07             ` Chris Murphy
2012-10-28 21:18               ` Roman Mamedov
2012-10-28 21:24                 ` Mikael Abrahamsson
2012-10-28 21:45                 ` Miles Fidelman
2012-10-28 22:35                   ` Chris Murphy
2012-10-28 21:51                 ` Chris Murphy
2012-10-28 21:59           ` joystick [this message]
2012-10-28 22:10             ` Phil Turmel
2012-10-29  0:12               ` joystick
2012-10-29  0:21                 ` Phil Turmel
2012-10-29  0:27                 ` Chris Murphy
2012-10-28 21:21 ` Mikael Abrahamsson
2012-10-28 23:51 ` Peter Kieser

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=508DAAD3.4050209@shiftmail.org \
    --to=joystick@shiftmail.org \
    --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 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.