linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carsten Aulbert <Carsten.Aulbert@aei.mpg.de>
To: Phil Turmel <philip@turmel.org>,
	Ram Ramesh <rramesh2400@gmail.com>,
	Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: When do you replace old hard drives in a raid6?
Date: Mon, 7 Mar 2016 07:59:40 +0100	[thread overview]
Message-ID: <56DD26DC.8020701@aei.mpg.de> (raw)
In-Reply-To: <56DCCB55.1060906@turmel.org>

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

Hi

On 03/07/2016 01:29 AM, Phil Turmel wrote:
> I replace drives when their relocation count hits double digits.  In my
> limited sample, that's typically after 40,000 hours.

It really depends a lot on the drive type and manufacturer (for example
see the various reports by Backblaze).

We run quite a number of "desktop" style drives and many have seen 60k
and more power on hours, but then our data collection is a bit biased as
we replace disks once they do not complete a "long" smartcheck (smartctl
-t long).

I've attached a sorted list of current data, columns are mostly:

manufacturer
model number
reallocated sectors (ID 5 of smartctl -a)
power on hours (also according to smartctl -a)

So, not sure one could infer much from these lines due to the inherent bias.

Personally, I would monitor the number of reallocated and pending
blocks, run short tests often and long tests about once a week. This
should give you at least some hint, if a drive may go down. And if it
does unexpectedly, you should be covered by RAID6.

Cheers

Carsten

[-- Attachment #2: disk-realloc-poweron.gz --]
[-- Type: application/gzip, Size: 9866 bytes --]

  parent reply	other threads:[~2016-03-07  6:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-05 20:49 When do you replace old hard drives in a raid6? Ram Ramesh
2016-03-07  0:29 ` Phil Turmel
2016-03-07  0:52   ` Ram Ramesh
2016-03-07  2:31     ` Weedy
2016-03-07  4:40       ` Ram Ramesh
2016-03-07  5:18     ` Phil Turmel
2016-03-09  0:11       ` Ram Ramesh
2016-03-09  2:49         ` John Stoffel
2016-03-09  6:43         ` Mikael Abrahamsson
2016-03-09  6:59           ` Roman Mamedov
2016-03-07  6:59   ` Carsten Aulbert [this message]
2016-03-08 22:01     ` Wols Lists

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=56DD26DC.8020701@aei.mpg.de \
    --to=carsten.aulbert@aei.mpg.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.org \
    --cc=rramesh2400@gmail.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).