All of lore.kernel.org
 help / color / mirror / Atom feed
From: scar <scar-47zfDnpWZoPQT0dZR+AlfA@public.gmane.org>
To: linux-raid-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: moving spares into group and checking spares
Date: Wed, 14 Sep 2016 10:52:55 -0700	[thread overview]
Message-ID: <nrc2pm$2a9$1@blaine.gmane.org> (raw)
In-Reply-To: <20160914092959.GA3584-oubN3LzF/wf25t9ic+4fgA@public.gmane.org>

Andreas Klauer wrote on 09/14/2016 02:29 AM:
> On Tue, Sep 13, 2016 at 10:18:41PM -0700, 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.
> That's perfect for switching to RAID-6. More redundancy should be
> more useful than spares that only sync in when you already completely
> lost redundancy ...
>
> And the disks would also be covered by your checks that way ;)

i'm not sure what you're suggesting, that 4x 11+1 RAID5 arrays should be 
changed to 1x 46+2 RAID6 array?  that doesn't seem as safe to me.  and 
checkarray isn't going to check the spare disks just as it's not doing 
now.... also that would require me to backup/restore the data so i can 
create a new array


--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-09-14 17:52 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 [this message]
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

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='nrc2pm$2a9$1@blaine.gmane.org' \
    --to=scar-47zfdnpwzopqt0dzr+alfa@public.gmane.org \
    --cc=linux-raid-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.