All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed W <lists@wildgooses.com>
To: stefan.huebner@stud.tu-ilmenau.de
Cc: linux-raid@vger.kernel.org
Subject: Re: HBA Adaptor advice
Date: Mon, 23 May 2011 11:18:05 +0100	[thread overview]
Message-ID: <4DDA345D.1010603@wildgooses.com> (raw)
In-Reply-To: <4DD9F0EB.5040801@stud.tu-ilmenau.de>

On 23/05/2011 06:30, Stefan /*St0fF*/ Hübner wrote:

> We sell 200+ drives a week from our "at that time preferred"
> Manufacturer.  That was WD from 2008 till the beginning of 2010.  

Just to clarify - are all those "failures" basically attributable to
drives with unreadable sectors which then drop out of arrays due to lack
of TLER?

ie if the drive DID have TLER then it would likely not have been
reported as a failed drive? (But presumably smart might report a
re-allocated sector and you might get a sectors dataloss?)



> But
> since the climb of wd failure rates we're at "Hitachi" and have
> astounding failure rates of less than one percent.  I hope this will
> stay the case even after WD bought Hitachi GST...

Likewise is this because the Hitachi drives appear more reliable or
because they incorporate some kind of TLER which keeps them running in
the face of reallocated sectors?

Can you draw your conclusion to the desktop Hitachi drives also? Do
these also suffer lower failure rates? Can they be made "TLER" compatible?


> Conclusion about this university-storage-failure: wrong drives for this
> scenario.  It would've been OK to use the cheap WDs for backup (if the
> backup was at least RAID6 and sends error-mails to the admin).  But the
> primary storage was a big fail.  You do not use this kind of storage for
> data which is worth much time (and by that much money).

How do folks here react to Googles paper stating that largely they find
little difference in reliability between "raid drives" and consumer drives?

Granted it's a problem if a drive pops out of an array because it has a
reallocated sector, but a) do folks with TLER drives immediately replace
the drive when they see a reallocated sector? b) those without TLER run
badblocks and put the drive back into the array c) can MD raid work
around the limitations of lacking TLER and consumer drives?

Thanks

Ed W

--
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

  reply	other threads:[~2011-05-23 10:18 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 12:26 HBA Adaptor advice Ed W
2011-05-19 12:36 ` Roman Mamedov
2011-05-19 12:43   ` Mathias Burén
2011-05-19 14:06 ` Michael Sallaway
2011-05-19 19:10 ` Thomas Harold
2011-05-19 21:12   ` Rudy Zijlstra
2011-05-19 21:07 ` Brad Campbell
2011-05-20 20:58   ` Tobias McNulty
2011-05-20 21:23     ` Brad Campbell
2011-05-20  2:08 ` Andy Smith
2011-05-20  5:30   ` Stan Hoeppner
2011-05-21  9:52     ` Ed W
2011-05-20  7:33   ` Ed W
2011-05-20 10:21     ` Stan Hoeppner
2011-05-21 11:17       ` Ed W
2011-05-21 11:29         ` Rudy Zijlstra
2011-05-21 11:54           ` Ed W
2011-05-21 17:37             ` Leslie Rhorer
2011-05-22  9:41             ` Stan Hoeppner
2011-05-22 10:03               ` Rudy Zijlstra
2011-05-23  9:32                 ` Ed W
2011-05-21 17:05           ` Leslie Rhorer
2011-05-22  9:04         ` Stan Hoeppner
2011-05-22 10:09           ` Brad Campbell
2011-05-22 19:25             ` Stan Hoeppner
2011-05-22 20:57               ` Tobias McNulty
2011-05-22 21:13                 ` Johannes Truschnigg
2011-05-23  9:48                   ` Ed W
2011-05-23 10:44                     ` John Robinson
2011-05-22 23:19               ` Brad Campbell
2011-05-23  4:09                 ` Roman Mamedov
2011-05-23  5:54                   ` Brad Campbell
2011-05-23  6:08                     ` Roman Mamedov
2011-05-23 10:42                     ` Stan Hoeppner
2011-05-23 11:35                       ` David Brown
2011-05-23  6:54                 ` Stan Hoeppner
2011-05-23  7:23                   ` Brad Campbell
2011-05-22 23:44               ` Brad Campbell
2011-05-23  0:07                 ` Brad Campbell
2011-05-23  5:30                   ` Stefan /*St0fF*/ Hübner
2011-05-23 10:18                     ` Ed W [this message]
2011-05-23  9:58                 ` Stan Hoeppner
2011-05-23 10:33                   ` Ed W
2011-05-23 11:21                     ` Stan Hoeppner
2011-05-20 12:18     ` Joe Landman
2011-05-20 12:34       ` Roman Mamedov
2011-05-20 12:36         ` Mathias Burén
2011-05-20 12:48         ` Joe Landman
2011-05-20 13:21       ` Ed W
2011-05-20 14:23         ` Joe Landman
2011-05-20 20:01       ` Andy Smith
2011-05-20 20:12         ` Stan Hoeppner
2011-05-20 20:24         ` Drew
2011-05-20 20:58           ` Stan Hoeppner
     [not found]             ` <4DD7A100.2010807@wildgooses.com>
2011-05-22  8:13               ` Stan Hoeppner
2011-05-23  2:11 Jim Schatzman
2011-05-23  3:39 ` Tobias McNulty
2011-05-23 10:42   ` Ed W
2011-05-23 11:14 HBA Adaptor Advice Ed W
2011-05-23 11:55 ` Joe Landman

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=4DDA345D.1010603@wildgooses.com \
    --to=lists@wildgooses.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=stefan.huebner@stud.tu-ilmenau.de \
    /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.