From: Richard Scobie <richard@sauce.co.nz>
To: linux-raid@vger.kernel.org
Subject: Re: two questions re. proactive recovery and forced assembly
Date: Fri, 09 May 2008 08:23:21 +1200 [thread overview]
Message-ID: <48236139.70301@sauce.co.nz> (raw)
In-Reply-To: <c4985c940805080401k5851a9d5n35d12d6d07ff2496@mail.gmail.com>
rosenfield.albert@gmail.com wrote:
> But will this assemble a RAID5 array where the event counters are out
> of sync on not one, but two disks?
I cannot read code unfortunately, but the man page states:
" --force
Insist that mdadm accept the geometry and layout specified without
question."
I would therefore expect it to.
Regards,
Richard
next prev parent reply other threads:[~2008-05-08 20:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 12:01 two questions re. proactive recovery and forced assembly rosenfield.albert
2008-04-12 22:36 ` Richard Scobie
2008-05-07 11:22 ` rosenfield.albert
2008-05-08 1:13 ` Richard Scobie
2008-05-08 11:01 ` rosenfield.albert
2008-05-08 20:23 ` Richard Scobie [this message]
2008-05-07 12:52 ` rosenfield.albert
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=48236139.70301@sauce.co.nz \
--to=richard@sauce.co.nz \
--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).