From: NeilBrown <neilb@suse.de>
To: Keith Keller <kkeller@wombat.san-francisco.ca.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID-6 problem
Date: Sun, 14 Oct 2012 06:31:02 +1100 [thread overview]
Message-ID: <20121014063102.0755820b@notabene.brown> (raw)
In-Reply-To: <mepok9xf4q.ln2@goaway.wombat.san-francisco.ca.us>
[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]
On Sat, 13 Oct 2012 11:45:10 -0700 Keith Keller
<kkeller@wombat.san-francisco.ca.us> wrote:
> On 2012-10-13, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> >
> > Re-creating a raid5/6 with --assume-clean is for me a disaster recovery,
> > something that should be performed when everything else fails. It's
> > extremely unfortunate that a lot of guides bring this in very early in the
> > fault finding process.
>
> Actually the RAID wiki suggests exactly this path, and suggests against
> --force, contrary to the advice I've gotten here from Neil and others.
>
> https://raid.wiki.kernel.org/index.php/RAID_Recovery#Restore_array_by_recreating_.28after_multiple_device_failure.29
>
> I could update this, but not being expert all it'd say is "use
> --assemble --force; if it fails ask on the mailing list." :) Perhaps
> that's actually the best advice to give, but if there's something more
> useful to put on that page maybe someone with more expertise could
> update it?
>
> --keith
>
You should definitely try '--assemble --force' before trying to recreate the
array. There is no question about that.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-10-13 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 12:03 RAID-6 problem Piergiorgio Sartor
2012-10-13 17:23 ` Mikael Abrahamsson
2012-10-13 18:45 ` Keith Keller
2012-10-13 19:31 ` NeilBrown [this message]
2012-10-13 21:22 ` Piergiorgio Sartor
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=20121014063102.0755820b@notabene.brown \
--to=neilb@suse.de \
--cc=kkeller@wombat.san-francisco.ca.us \
--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).