From: Neil Brown <neilb@cse.unsw.edu.au>
To: Martin Bene <martin.bene@icomedias.com>
Cc: krause@mogli-soft.de, linux-raid@vger.kernel.org
Subject: Re: AW: recover short-time-power-failure of raid 5?
Date: Mon, 25 Nov 2002 21:15:44 +1100 [thread overview]
Message-ID: <15841.63568.187721.514489@notabene.cse.unsw.edu.au> (raw)
In-Reply-To: message from Martin Bene on Monday November 25
On Monday November 25, martin.bene@icomedias.com wrote:
> PS: not sure what happens if you're using a journaling fs on the raid - I
> think fsck replays the journal before checking, so trying out different
> combinations of disk doesn't look like a viable option in that case?
With ext3, "fsck -n" doesn't replay the journal, but will report
errors that would be fixed by replaying the journal. You would have
to ask yourself 'do these look like major errors, or just minor things
that the journal replay would fix'.
NeilBrown
prev parent reply other threads:[~2002-11-25 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 10:07 AW: recover short-time-power-failure of raid 5? Martin Bene
2002-11-25 10:15 ` Neil Brown [this message]
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=15841.63568.187721.514489@notabene.cse.unsw.edu.au \
--to=neilb@cse.unsw.edu.au \
--cc=krause@mogli-soft.de \
--cc=linux-raid@vger.kernel.org \
--cc=martin.bene@icomedias.com \
/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).