linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: scar <scar@drigon.com>, linux-raid@vger.kernel.org
Subject: Re: moving spares into group and checking spares
Date: Thu, 29 Sep 2016 11:21:17 +1000	[thread overview]
Message-ID: <8760pf7b76.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <nramjg$n07$1@blaine.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]

On Wed, Sep 14 2016, scar wrote:

> i currently have four RAID-5 md arrays which i concatenated into one 
> logical volume (lvm2), essentially creating a RAID-50.  each md array 
> was created with one spare disk.
>
> instead, i would like to move the four spare disks into one group that 
> each of the four arrays can have access to when needed.  i was wondering 
> how to safely accomplish this, preferably without unmounting/disrupting 
> the filesystem.

You don't need to move the devices.  Just use the spare-group= setting
in mdadm.conf to tell mdadm that all arrays should be considered part of
the same spare-group.  Then "mdadm --monitor" will freely move spares
between arrays as needed.

>
> secondly, i have the checkarray script scheduled via cron to 
> periodically check each of the four arrays.  i noticed in the output of 
> checkarray that it doesn't list the spare disk(s).  so i'm guessing they 
> are not being checked?  i was wondering, then, how i could also check 
> the spare disks to make sure they are healthy and ready to be used if 
> needed?

mdadm doesn't provide any automatic support for this.
You would need to e.g.
 - remove a spare from an array
 - test it in some way: e.g. use dd to read every block.
 - if satisfied, add it back to the array.

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]

      parent reply	other threads:[~2016-09-29  1:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14  5:18 moving spares into group and checking spares scar
2016-09-14  9:29 ` Andreas Klauer
     [not found]   ` <20160914092959.GA3584-oubN3LzF/wf25t9ic+4fgA@public.gmane.org>
2016-09-14 17:52     ` scar
2016-09-14 18:22       ` Roman Mamedov
2016-09-14 21:05         ` scar
2016-09-14 22:33           ` Chris Murphy
     [not found]             ` <CAJCQCtQJwOTYsWubd0rV-6PRL4kmVRKLfLr3=7ZPr1Zb3SrwtQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-14 22:59               ` scar
2016-09-14 23:15                 ` Chris Murphy
     [not found]                   ` <CAJCQCtQ1GHdQtShbW3U1o-fmXhT3fHrC7S9BxsxrrOG=0H_p3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-15  3:42                     ` scar
2016-09-15  3:51                       ` Chris Murphy
     [not found]                         ` <CAJCQCtRW9REafzmyk+W6aVxqxMUWCdXNkrST1e7udrH-zp26Uw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-28  0:19                           ` scar
2016-09-29  1:17                             ` NeilBrown
2016-09-14 18:35       ` Wols Lists
2016-09-29  1:21 ` NeilBrown [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=8760pf7b76.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=scar@drigon.com \
    /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).