From: CaT <cat@zip.com.au>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid5 stuck in degraded, inactive and dirty mode
Date: Thu, 10 Jan 2008 21:29:20 +1100 [thread overview]
Message-ID: <20080110102919.GZ3940@zip.com.au> (raw)
In-Reply-To: <20080109081634.GS3940@zip.com.au>
On Wed, Jan 09, 2008 at 07:16:34PM +1100, CaT wrote:
> > But I suspect that "--assemble --force" would do the right thing.
> > Without more details, it is hard to say for sure.
>
> I suspect so aswell but throwing caution into the wind erks me wrt this
> raid array. :)
Sorry. Not to be a pain but considering the previous email with all the
examine dumps, etc would the above be the way to go? I just don't want
to have missed something and bugger the array up totally.
--
"To the extent that we overreact, we proffer the terrorists the
greatest tribute."
- High Court Judge Michael Kirby
next prev parent reply other threads:[~2008-01-10 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 5:55 raid5 stuck in degraded, inactive and dirty mode CaT
2008-01-09 6:52 ` Neil Brown
2008-01-09 8:16 ` CaT
2008-01-10 10:29 ` CaT [this message]
2008-01-10 20:21 ` Neil Brown
2008-01-10 22:23 ` CaT
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=20080110102919.GZ3940@zip.com.au \
--to=cat@zip.com.au \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).