From: "Stefan G. Weichinger" <lists@xunil.at>
To: linux-raid@vger.kernel.org
Subject: Pending sectors in valid array - how to proceed?
Date: Wed, 28 Jul 2010 19:46:29 +0200 [thread overview]
Message-ID: <4C506CF5.2080307@xunil.at> (raw)
Greets,
in a customer-server I run these arrays:
# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sdb1[1] sda1[0]
104320 blocks [2/2] [UU]
md3 : active raid5 sdd3[3](S) sdc3[2] sdb3[1] sda3[0]
15647104 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
md4 : active raid5 sdd4[3](S) sdc4[2] sdb4[1] sda4[0]
471941376 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
So far everything OK.
--
smartctl shows for /dev/sdb:
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always
- 0
195 Hardware_ECC_Recovered 0x001a 058 039 000 Old_age Always
- 146754005
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always
- 13
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age
Offline - 13
(relevant lines as far as I understand ...)
So I have these 13 pending sectors ...
I assume it would be good to swap sdb for safety?
This would mean:
* fail sdb
* wait for the spare to be synced ... which I fear somehow (I once lost
an array as a second drive dropped out while resync ...)
* change sdb
* re-add sdb
correct?
I also read of a way of removing and re-adding a drive to get rid of
these sectors?
Is this a recommended thing to do?
What would you recommend me to do?
Thank you, Stefan
next reply other threads:[~2010-07-28 17:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 17:46 Stefan G. Weichinger [this message]
2010-07-28 18:41 ` Pending sectors in valid array - how to proceed? Tim Small
2010-07-28 20:27 ` Stefan *St0fF* Huebner
2010-07-28 21:11 ` Roman Mamedov
2010-07-29 2:50 ` Simon Matthews
2010-07-30 4:24 ` Simon Matthews
2010-07-29 8:45 ` Stefan G. Weichinger
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=4C506CF5.2080307@xunil.at \
--to=lists@xunil.at \
--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 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.