From: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
To: linux-raid@vger.kernel.org
Subject: Re: NVRAM support
Date: Thu, 16 Feb 2006 11:05:54 +0100 [thread overview]
Message-ID: <dt1iq2$c29$1@sea.gmane.org> (raw)
In-Reply-To: 17395.45710.99321.522482@cse.unsw.edu.au
Neil Brown <neilb@suse.de> wrote:
> On Wednesday February 15, mirko.benz@web.de wrote:
>> E.g. Data and parity write requests are issued in parallel but only one
>> finishes. This will
>> lead to inconsistent data. It will be undetected and can not be
> If the array is degraded, that the inconsistency cannot be detected.
Hmm, if the array is degraded, then there is no redundancy at all, so
there is no chance for any inconsistency.
Btw., this reminds me... now when you have raid6 - when is a raid6
defined to be degraded? Perhaps you have equal issues there as with
raid1 >2 mirrors some months ago (resync was not started when 3rd
mirror failed and 1st and 2nd were inconsistent)?
> If the array is fully functioning, then any inconsistency will be
> corrected by a 'resync'.
Yes, because the redundancy is ignored and rebuilt.
regards
Mario
--
Why did the tachyon cross the road?
Because it was on the other side.
next prev parent reply other threads:[~2006-02-16 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 9:01 NVRAM support Mirko Benz
2006-02-10 12:42 ` Erik Mouw
2006-02-10 15:43 ` Bill Davidsen
2006-02-11 1:02 ` dean gaudet
2006-02-13 9:22 ` Erik Mouw
2006-02-13 11:54 ` Andy Smith
2006-02-13 13:35 ` Guy
2006-02-14 10:17 ` Erik Mouw
2006-02-15 8:24 ` Mirko Benz
2006-02-15 23:00 ` Neil Brown
2006-02-16 10:05 ` Mario 'BitKoenig' Holbe [this message]
2006-02-20 9:57 ` Mirko Benz
2006-02-20 23:16 ` Neil Brown
2006-02-10 17:38 ` Paul Clements
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='dt1iq2$c29$1@sea.gmane.org' \
--to=mario.holbe@tu-ilmenau.de \
--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).