From: Jools Wills <jools@oxfordinspire.co.uk>
To: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
Cc: 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, 02 Apr 2010 02:40:13 +0100 [thread overview]
Message-ID: <1270172413.24051.2.camel@travelmate.workshop> (raw)
In-Reply-To: <20100401230437.GA5067@lazy.lzy>
On Fri, 2010-04-02 at 01:04 +0200, Piergiorgio Sartor wrote:
> you might be unaware of the repeated neverending
> discussions about this topic.
yup :)
> 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.
Is this the same for raid 5 or specifically a raid 6 issue on linux ?
I had assumed that with my raid5 array, if the raid check finds an error
it will attempt to rewrite back to the disk, and then read again, and
carry on if everything is ok.
Best Regards
Jools
Jools Wills
--
IT Consultant
Oxford Inspire - http://www.oxfordinspire.co.uk - be inspired
t: 01235 519446 m: 07966 577498
jools@oxfordinspire.co.uk
next prev parent reply other threads:[~2010-04-02 1:40 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
2010-04-01 23:46 ` Michael Evans
2010-04-02 1:40 ` Jools Wills [this message]
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=1270172413.24051.2.camel@travelmate.workshop \
--to=jools@oxfordinspire.co.uk \
--cc=dledford@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=max@maxeaves.co.uk \
--cc=neilb@suse.de \
--cc=piergiorgio.sartor@nexgo.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