From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: Jools Wills <jools@oxfordinspire.co.uk>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
Neil Brown <neilb@suse.de>,
max@maxeaves.co.uk, linux-raid@vger.kernel.org,
Doug Ledford <dledford@redhat.com>
Subject: Re: Problems with RAID 6 across 15 disks
Date: Fri, 2 Apr 2010 01:04:37 +0200 [thread overview]
Message-ID: <20100401230437.GA5067@lazy.lzy> (raw)
In-Reply-To: <1270162736.24051.0.camel@travelmate.workshop>
Hi,
> > but since it is not possible to correct those errors,
> > there is no point in doing it... :-)
>
> Well it can. It can try and rewrite the block based on the data from the
> other disks, and if the drive needs to, it can remap the bad block.
you might be unaware of the repeated neverending
discussions about this topic.
It is *possible* to do it, but, as of today, it
cannot do it.
I mean, there is no functionality, in the RAID-6, to
detect and correct those errors using the available
double parity.
Consider that the RAID check returns only how many
mismatch are present, not where they are, i.e. on
which disks.
bye,
--
piergiorgio
next prev parent reply other threads:[~2010-04-01 23:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 13:23 Problems with RAID 6 across 15 disks Max Eaves
2010-04-01 13:49 ` Doug Ledford
2010-04-01 14:07 ` Max Eaves
2010-04-01 20:43 ` Neil Brown
2010-04-01 22:46 ` Piergiorgio Sartor
2010-04-01 22:58 ` Jools Wills
2010-04-01 23:04 ` Piergiorgio Sartor [this message]
2010-04-01 23:46 ` Michael Evans
2010-04-02 1:40 ` Jools Wills
2010-04-02 5:03 ` Neil Brown
2010-04-02 8:22 ` Piergiorgio Sartor
2010-04-02 10:21 ` Max Eaves
2010-04-02 5:55 ` responsiveness during raid check (Was: Problems with RAID 6 across 15 disks) Luca Berra
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=20100401230437.GA5067@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--cc=dledford@redhat.com \
--cc=jools@oxfordinspire.co.uk \
--cc=linux-raid@vger.kernel.org \
--cc=max@maxeaves.co.uk \
--cc=neilb@suse.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