All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan G. Weichinger" <lists@xunil.at>
To: linux-raid@vger.kernel.org
Subject: raid5+hotspare: request for recommended procedure
Date: Wed, 29 Sep 2010 11:03:39 +0200	[thread overview]
Message-ID: <4CA300EB.1070909@xunil.at> (raw)


Greets, raid-users,

I would like to ask for hints on how to proceed.

I have a customers server ~500kms away ... running 2 raid5-arrays w/
hotspare:

# 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]

unused devices: <none>


sdb shows errors:

197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always
      -       13
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age
Offline      -       13

--

The customer would now take the server with him and bring it to a fellow
technician who could take out sdb, clone it to a new hdd and re-insert it.

This would be plan A.

Plan B would be that I mark sdb failed now and let the raids rebuild. I
fear that a second hdd might fail when doing this.

All Seagate-drives:

sda, sdb: ST3250310NS
sdc, sdd: ST3250621NS

I also ran a "echo check > /sys/block/mdX/md/sync_action" because this
had helped to remove those errors at another server, unfortunately it
did not help here.

Could you please advise what the better and safer alternative would be?

Thanks a lot, Stefan

             reply	other threads:[~2010-09-29  9:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29  9:03 Stefan G. Weichinger [this message]
2010-09-29 10:03 ` raid5+hotspare: request for recommended procedure Tim Small
2010-09-29 10:06   ` Tim Small
2010-09-29 12:42   ` Stefan G. Weichinger
2010-09-29 14:25   ` Stefan G. Weichinger
2010-09-29 14:29     ` Jon Hardcastle
2010-09-29 15:08       ` Stefan G. Weichinger
2010-09-29 15:39         ` Jon Hardcastle
2010-09-30  9:50           ` Stefan G. Weichinger
2010-10-01  9:00             ` Stefan G. Weichinger
2010-10-01  9:59               ` Stefan G. Weichinger
2010-10-01 21:20                 ` Stefan G. Weichinger
2010-09-29 12:01 ` Michael Tokarev
2010-09-29 12:21   ` Tim Small
2010-09-29 12:38     ` 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=4CA300EB.1070909@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.