From: Wolfgang Denk <wd@denx.de>
To: Brad Campbell <brad@fnarfbargle.com>
Cc: Anssi Hannula <anssi.hannula@iki.fi>,
Jan Ceuleers <jan.ceuleers@gmail.com>,
linux-raid@vger.kernel.org
Subject: Re: Preventative replacement of active RAID1 disks
Date: Sat, 21 Jan 2012 18:21:11 +0100 [thread overview]
Message-ID: <20120121172111.AB3CD1FD330@gemini.denx.de> (raw)
In-Reply-To: <4F1AECB8.6020905@fnarfbargle.com>
Dear Brad Campbell,
In message <4F1AECB8.6020905@fnarfbargle.com> you wrote:
>
> If you've got no reallocations, SMART tells you the drive is ok and you are not noticing any odd
> behaviour the chances of the drive being in distress are pretty slim.
Agreed. That's also what I do: routinely check for reallocated
sectors.
This is what it looks when a disk is slowly dying:
--- previous 2011-12-24 19:18:02.117252227 +0100
+++ latest 2011-12-25 07:18:02.332549299 +0100
@@ -1,4 +1,5 @@
...
-=== /dev/sdb : ST31000340AS S/N 9QJ5DS23 OK
+=== /dev/sdb : ST31000340AS S/N 9QJ5DS23 *** ERRORS ***
+ Reallocated Sectors: 20
--- previous 2011-12-26 07:18:01.948581196 +0100
+++ latest 2011-12-26 19:18:01.968947510 +0100
@@ -1,5 +1,5 @@
...
=== /dev/sdb : ST31000340AS S/N 9QJ5DS23 *** ERRORS ***
- Reallocated Sectors: 20
+ Reallocated Sectors: 31
--- previous 2011-12-31 19:18:02.009911235 +0100
+++ latest 2012-01-01 07:18:02.678021034 +0100
...
=== /dev/sdb : ST31000340AS S/N 9QJ5DS23 *** ERRORS ***
- Reallocated Sectors: 31
+ Reallocated Sectors: 33
--- previous 2012-01-09 19:18:02.433054750 +0100
+++ latest 2012-01-10 07:18:02.207395854 +0100
@@ -1,7 +1,4 @@
...
=== /dev/sdb : ST31000340AS S/N 9QJ5DS23 *** ERRORS ***
- Reallocated Sectors: 33
+ Reallocated Sectors: 34
--- previous 2012-01-10 19:18:02.502390238 +0100
+++ latest 2012-01-11 07:18:02.147518681 +0100
...
=== /dev/sdb : ST31000340AS S/N 9QJ5DS23 *** ERRORS ***
- Reallocated Sectors: 34
+ Reallocated Sectors: 71
--- previous 2012-01-11 19:18:02.502390238 +0100
+++ latest 2012-01-12 07:18:02.147518681 +0100
...
=== /dev/sdc : ST31000340AS S/N 9QJ5DS23 *** ERRORS ***
- Reallocated Sectors: 71
+ Reallocated Sectors: 103
--- previous 2012-01-14 19:18:01.773819479 +0100
+++ latest 2012-01-15 07:18:02.414494003 +0100
...
=== /dev/sdb : ST31000340AS S/N 9QJ5DS23 *** ERRORS ***
- Reallocated Sectors: 103
+ Reallocated Sectors: 127
If you see such behaviour you really want to replace the drive.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
What's the sound a name makes when it's dropped?
next prev parent reply other threads:[~2012-01-21 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 17:04 Preventative replacement of active RAID1 disks Jan Ceuleers
2012-01-21 16:09 ` Anssi Hannula
2012-01-21 16:50 ` Brad Campbell
2012-01-21 17:21 ` Wolfgang Denk [this message]
2012-01-21 17:01 ` Jan Ceuleers
2012-01-29 8:43 ` Jan Ceuleers
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=20120121172111.AB3CD1FD330@gemini.denx.de \
--to=wd@denx.de \
--cc=anssi.hannula@iki.fi \
--cc=brad@fnarfbargle.com \
--cc=jan.ceuleers@gmail.com \
--cc=linux-raid@vger.kernel.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).