All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Goryachev <mailinglists@websitemanagers.com.au>
To: Roman Mamedov <rm@romanrm.net>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Uneven wear on raid1 devices
Date: Wed, 27 Jan 2016 11:05:31 +1100	[thread overview]
Message-ID: <56A809CB.8070207@websitemanagers.com.au> (raw)
In-Reply-To: <20160125104027.597041a3@natsu>

On 25/01/16 16:40, Roman Mamedov wrote:
> On Mon, 25 Jan 2016 16:29:02 +1100
> Adam Goryachev <adam@websitemanagers.com.au> wrote:
>
>>     9 Power_On_Hours          -O--CK   098   098   000    -    6435
>>     9 Power_On_Hours          -O--CK   095   095   000    -    23178
> 2nd drive has almost 4x as much power-on time than the first one. My guess
> would be that it accumulated all that write usage back before you put it into
> this RAID1.
>
> If you want to ensure the RAID1 usage is even, record the SMART data you have
> now, and compare to the readings you will have a month later.

Hmmm, oops, I should have looked at that. Now of course, I realise one 
drive was replaced under warranty when it failed around 6 months ago 
(well, the value says just under 9 months actually), and that would 
explain the difference in wear and power on hours (aside from the 
initial full sync when the new device was first installed).

So, 2.5 years old, and 74% life remaining, and 9 months with 93% life 
remaining.

Sounds good to me, I should expect these to last at least the 5 years I 
was hoping for, and probably before that happens I will want to upgrade 
them to increase capacity anyway.

Thanks for your help

Regards,
Adam

-- 
Adam Goryachev Website Managers www.websitemanagers.com.au

      parent reply	other threads:[~2016-01-27  0:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25  5:29 Uneven wear on raid1 devices Adam Goryachev
2016-01-25  5:40 ` Roman Mamedov
2016-01-25 18:00   ` Phil Turmel
2016-01-27  0:18     ` Adam Goryachev
2016-01-27  0:05   ` Adam Goryachev [this message]

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=56A809CB.8070207@websitemanagers.com.au \
    --to=mailinglists@websitemanagers.com.au \
    --cc=linux-raid@vger.kernel.org \
    --cc=rm@romanrm.net \
    /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.