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: Fri, 11 Jan 2008 07:21:42 +1100 [thread overview]
Message-ID: <18310.32342.80387.311569@notabene.brown> (raw)
In-Reply-To: message from CaT on Thursday January 10
On Thursday January 10, cat@zip.com.au wrote:
> 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.
Yes, definitely.
The superblocks look perfectly normal for a single drive failure
followed by a crash. So "--assemble --force" is the way to go.
Technically you could have some data corruption if a write was under
way at the time of the crash. In that case the parity block of that
stripe could be wrong, so the recovered data for the missing device
could be wrong.
This is why you are required to use "--force" - to confirm that you
are aware that there could be a problem.
It would be worth running "fsck" just to be sure that nothing critical
has been corrupted. Also if you have a recent backup, I wouldn't
recycle it until I was fairly sure that all your data was really safe.
But in my experience the chance of actual data corruption in this
situation is fairly low.
NeilBrown
next prev parent reply other threads:[~2008-01-10 20:21 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
2008-01-10 20:21 ` Neil Brown [this message]
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=18310.32342.80387.311569@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).