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 14:05:13 -0700	[thread overview]
Message-ID: <nrce27$2km$1@blaine.gmane.org> (raw)
In-Reply-To: <20160914232249.6e5fc568@natsu>

Roman Mamedov wrote on 09/14/2016 11:22 AM:
> But you think an 11-member RAID5, let alone four of them joined by LVM is
> safe? From a resiliency standpoint that setup is like insanity squared.

yeah it seems fine?  disks are healthy and regularly checked, just 
wondering how to check the spares.  use cron to schedule weekly smartctl 
long test?


> Considering that your expenses for redundancy are 8 disks at the moment, you
> could go with 3x15-disk RAID6 with 2 shared hotspares, making overall
> redundancy expense the same 8 disks -- but for a massively safer setup.

actually it would be 9 disks (3x15 +2 = 47 not 48) but i'm ok with that. 
  but rebuilding the array right now is not an option

> might just as well join them using mdadm RAID0 and
> at least gain the improved linear performance.

i did want to do that but debian-installer didn't seem to support it...


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

  reply	other threads:[~2016-09-14 21:05 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 [this message]
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='nrce27$2km$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.