From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: Wolfgang Denk <wd@denx.de>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
linux-raid@vger.kernel.org
Subject: Re: Huge values of mismatch_cnt on RAID 6 arrays under Fedora 18
Date: Mon, 28 Jan 2013 21:44:22 +0100 [thread overview]
Message-ID: <20130128204422.GA14115@lazy.lzy> (raw)
In-Reply-To: <20130128201947.2B615200607@gemini.denx.de>
On Mon, Jan 28, 2013 at 09:19:47PM +0100, Wolfgang Denk wrote:
[...]
> P(0) wrong at 1951871
> Q(1) wrong at 1951871
> Error detected at 1951871: disk slot unknown
> ...
>
> Does this allow to tell which disk it is?
Hi Wolfgang,
unfortunately, this means more than one disk
has data which cannot match the parities.
If only one disk would have been corrupted, we
could have seen it reported (apart from patological
cases), but when the slot is "unknown" it means
the detection was not possible.
It could still be the data is as it was written,
but, for some reasons I could not imagine, the
parities (both) are not correct.
This could be in case of some software bug, which
would be quite a surprise, I must say.
Still, would be nice to check if the whole array
is it this state or if, sooner or later, some
knwon slot (with error) is found somewhere else.
bye,
--
piergiorgio
next prev parent reply other threads:[~2013-01-28 20:44 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 19:26 Huge values of mismatch_cnt on RAID 6 arrays under Fedora 18 Wolfgang Denk
2013-01-27 19:45 ` Chris Murphy
2013-01-27 23:10 ` Wolfgang Denk
2013-01-27 20:05 ` Robin Hill
2013-01-27 23:11 ` Wolfgang Denk
2013-01-28 1:14 ` Phil Turmel
2013-01-28 1:42 ` Chris Murphy
2013-01-28 2:16 ` Chris Murphy
2013-01-28 6:43 ` Wolfgang Denk
2013-01-28 6:36 ` Wolfgang Denk
2013-01-28 7:00 ` Chris Murphy
2013-01-28 10:27 ` Wolfgang Denk
2013-01-28 6:27 ` Wolfgang Denk
2013-01-28 2:07 ` Brad Campbell
2013-01-28 6:39 ` Wolfgang Denk
2013-01-28 7:58 ` Dan Williams
2013-01-28 17:37 ` Piergiorgio Sartor
2013-01-28 18:12 ` Chris Murphy
2013-01-28 19:00 ` Wolfgang Denk
2013-01-28 19:10 ` Wolfgang Denk
2013-01-28 19:22 ` Piergiorgio Sartor
2013-01-28 20:19 ` Wolfgang Denk
2013-01-28 20:44 ` Piergiorgio Sartor [this message]
2013-01-28 22:47 ` Chris Murphy
2013-01-28 22:49 ` Chris Murphy
2013-01-28 23:03 ` Wolfgang Denk
2013-01-28 23:13 ` Chris Murphy
2013-01-28 23:31 ` Wolfgang Denk
2013-01-28 22:59 ` Wolfgang Denk
2013-01-28 23:07 ` Chris Murphy
2013-01-28 23:23 ` Wolfgang Denk
2013-01-28 23:42 ` Chris Murphy
2013-01-29 18:02 ` Roy Sigurd Karlsbakk
2013-01-29 18:28 ` Wolfgang Denk
2013-01-29 18:43 ` Roy Sigurd Karlsbakk
2013-01-29 17:49 ` Piergiorgio Sartor
2013-01-29 19:35 ` Paul Menzel
2013-01-29 20:18 ` Piergiorgio Sartor
2013-01-28 23:18 ` Wolfgang Denk
2013-01-29 17:57 ` Piergiorgio Sartor
2013-01-29 18:43 ` Wolfgang Denk
2013-01-29 20:24 ` Piergiorgio Sartor
2013-01-31 12:12 ` Wolfgang Denk
2013-01-31 17:14 ` Chris Murphy
2013-01-31 17:51 ` Piergiorgio Sartor
2013-01-31 18:36 ` Wolfgang Denk
2013-01-31 19:35 ` Chris Murphy
2013-01-31 19:46 ` Chris Murphy
2013-01-31 20:05 ` Wolfgang Denk
2013-01-31 20:41 ` Chris Murphy
2013-01-31 17:47 ` Piergiorgio Sartor
2013-01-28 19:18 ` Piergiorgio Sartor
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=20130128204422.GA14115@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--cc=linux-raid@vger.kernel.org \
--cc=wd@denx.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).