linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: CaT <cat@zip.com.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid5 stuck in degraded, inactive and dirty mode
Date: Wed, 9 Jan 2008 17:52:57 +1100	[thread overview]
Message-ID: <18308.28489.479077.86397@notabene.brown> (raw)
In-Reply-To: message from CaT on Wednesday January 9

On Wednesday January 9, cat@zip.com.au wrote:
> 
> I'd provide data dumps of --examine and friends but I'm in a situation
> where transferring the data would be a right pain. I'll do it if need
> be, though.
> 
> So, what can I do? 

Well, providing the output of "--examine" would help a lot.

But I suspect that "--assemble --force" would do the right thing.
Without more details, it is hard to say for sure.

NeilBrown

  reply	other threads:[~2008-01-09  6:52 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 [this message]
2008-01-09  8:16   ` CaT
2008-01-10 10:29     ` CaT
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=18308.28489.479077.86397@notabene.brown \
    --to=neilb@suse.de \
    --cc=cat@zip.com.au \
    --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).