linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Carlos Carvalho <carlos@fisica.ufpr.br>
Cc: linux-raid@vger.kernel.org
Subject: Re: Verifying spare drive, best practices
Date: Sat, 22 Mar 2008 13:25:53 -0400	[thread overview]
Message-ID: <47E54121.80806@tmr.com> (raw)
In-Reply-To: <18403.53429.355889.906445@fisica.ufpr.br>

Carlos Carvalho wrote:
> Maurice Hilarius (maurice@harddata.com) wrote on 20 March 2008 22:35:
>  >Given this situation:
>  >7 disks in total
>  >RAID5 of 6 disks, and a hot spare.
>  >
>  >mdadm show the 6 disks, but not the spare.
>  >
>  >As a maintenance question, where one wants to periodically ensure that 
>  >the hot spare is both available and good.
>  >How should one best :
>  >1) Verify the hot spare is still available.
>  >2) Verify that the hot spare is healthy?
>
> I usually do a dd if=/dev/zero of=/dev/spare to write to all sectors
> and give the drive a chance to remap bad blocks. Then run smartctl
> with a long test, and smartctl -a to see the results.
>
>   
I hope you disable use as a spare before doing this... If you were so 
"lucky" as to have a failure in the array and start using the drive as a 
spare while writing zeros to it, you might have an unexpected learning 
experience.

> If there are partitions I use sfdisk -d /dev/disk-in-array |sfdisk -f
> /dev/spare to copy the partition table from one of the other disks to
> the spare, or any other (non-manual...) method to restore the partitioning.
>
> This can be easily included in the routine array checks.
-- 
Bill Davidsen <davidsen@tmr.com>
  "Woe unto the statesman who makes war without a reason that will still
  be valid when the war is over..." Otto von Bismark 



  reply	other threads:[~2008-03-22 17:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21  4:35 Verifying spare drive, best practices Maurice Hilarius
2008-03-21 15:13 ` Carlos Carvalho
2008-03-22 17:25   ` Bill Davidsen [this message]
2008-03-25  4:48 ` Neil Brown
2008-03-25 13:29   ` Peter Evertz
2008-03-25 16:19   ` Bill Davidsen

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=47E54121.80806@tmr.com \
    --to=davidsen@tmr.com \
    --cc=carlos@fisica.ufpr.br \
    --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).