From: Ram Ramesh <rramesh2400@gmail.com>
To: Phil Turmel <philip@turmel.org>, Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: When do you replace old hard drives in a raid6?
Date: Tue, 8 Mar 2016 18:11:37 -0600 [thread overview]
Message-ID: <56DF6A39.4020904@gmail.com> (raw)
In-Reply-To: <56DD0F12.2060104@turmel.org>
On 03/06/2016 11:18 PM, Phil Turmel wrote:
> On 03/06/2016 07:52 PM, Ram Ramesh wrote:
>> On 03/06/2016 06:29 PM, Phil Turmel wrote:
>>> On 03/05/2016 03:49 PM, Ram Ramesh wrote:
>>>> I am curious if people actually replace hard drives periodically because
>>>> they are old or out of warranty. My 5 device raid6 has several older
>>>> drives (3/5 are 3+ years old and out of warranty) They seem fine with
>>>> SMART and raid scrubs. However, it makes me wonder when they will die.
>>>> What is the best policy in such situations? More importantly, do people
>>>> wait for disks to die and then replace or have some ad hoc schedule of
>>>> replacing (like every 6mo replace oldest) to keep things safe?
>>> I replace drives when their relocation count hits double digits. In my
>>> limited sample, that's typically after 40,000 hours.
>>>
>>> Phil
>> Thanks for the data point. 40K hours means roughly 4.5 years with 24/7.
>> That is very good. You use enterprise drives? Mine are desktop (and may
>> be one HGST NAS)
> I moved from desktop drives to NAS drives about 4 years ago. So the
> 40k+ hours were on desktop drives. (A couple started dying in the mid
> 30,000's, but I suspect I overheated those two.) The oldest NAS drives
> I have now are approaching 40k, and are all still @ zero relocations.
> WD Reds, fwiw.
>
>> My SMART is perfect except for power on hours. I am going to take it
>> easy for now as I have a spare (not part of a RAID) just in case
>> something bad happens.
> Yes, sounds reasonable.
>
> Phil
>
My disks have about 10K hours (my server only runs from 4pm-2am). I
think I have quite a bit of life left
assuming an on/off cycle is not as bad as extra 14 hours of run time.
Ramesh
next prev parent reply other threads:[~2016-03-09 0:11 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 [this message]
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
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=56DF6A39.4020904@gmail.com \
--to=rramesh2400@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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 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).