From: NeilBrown <neilb@suse.de>
To: Nagilum <nagilum@nagilum.org>
Cc: rob pfile <rpfile@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: 4-disk raid5 with 2 disks going bad: best way to proceed?
Date: Fri, 8 Apr 2011 22:05:28 +1000 [thread overview]
Message-ID: <20110408220528.40971e55@notabene.brown> (raw)
In-Reply-To: <20110407221334.16604ufejmh3q9s0@cakebox.homeunix.net>
On Thu, 07 Apr 2011 22:13:34 +0200 Nagilum <nagilum@nagilum.org> wrote:
> Hmm, I think you could:
> - add a disk,
> - reshape your raid5 to raid6 while using the layout where the raid5
> disks aren't really changed
That would be
mdadm --grow /dev/md0 --level=6 --parity=preserve
(I think).
> - let it finish syncing
> - reshape the raid6 to raid5 taking one of the bad disks out
I don't think that makes sense. (what command would you use exactly?)
It would be better to remove the bad device and replace it with another good
device (which means more dollars of course...)
>
> I'm sure Neil will let us know if this is nonsense. ;)
Only half ;-)
NeilBrown
> Alex.
>
> ----- Message from rpfile@gmail.com ---------
> Date: Wed, 6 Apr 2011 18:45:15 -0700
> From: rob pfile <rpfile@gmail.com>
> Subject: 4-disk raid5 with 2 disks going bad: best way to proceed?
> To: linux-raid@vger.kernel.org
>
> > is there a way to construct a clean copy of one of the disks even if
> > there are raid-correctable read errors?
>
> ----- End message from rpfile@gmail.com -----
>
>
>
> ========================================================================
> # _ __ _ __ http://www.nagilum.org/ \n icq://69646724 #
> # / |/ /__ ____ _(_) /_ ____ _ nagilum@nagilum.org \n +491776461165 #
> # / / _ `/ _ `/ / / // / ' \ Amiga (68k/PPC): AOS/NetBSD/Linux #
> # /_/|_/\_,_/\_, /_/_/\_,_/_/_/_/ Mac (PPC): MacOS-X / NetBSD /Linux #
> # /___/ x86: FreeBSD/Linux/Solaris/Win2k ARM9: EPOC EV6 #
> ========================================================================
>
>
> ----------------------------------------------------------------
> cakebox.homeunix.net - all the machine one needs..
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-04-08 12:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 1:45 4-disk raid5 with 2 disks going bad: best way to proceed? rob pfile
2011-04-07 3:35 ` Roberto Spadim
2011-04-07 7:21 ` Mikael Abrahamsson
2011-04-07 22:15 ` rob pfile
2011-04-08 12:10 ` NeilBrown
2011-04-09 14:39 ` rob pfile
2011-04-07 20:13 ` Nagilum
2011-04-08 12:05 ` NeilBrown [this message]
2011-04-08 15:47 ` Nagilum
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=20110408220528.40971e55@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=nagilum@nagilum.org \
--cc=rpfile@gmail.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).