linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
To: David Brown <david.brown@hesbynett.no>
Cc: Linux Raid <linux-raid@vger.kernel.org>,
	Bernd Schubert <bernd.schubert@fastmail.fm>
Subject: Re: Checksumming RAID?
Date: Tue, 27 Nov 2012 14:56:34 +0100 (CET)	[thread overview]
Message-ID: <25425956.18.1354024591879.JavaMail.root@zimbra> (raw)
In-Reply-To: <50B4BE27.1050101@hesbynett.no>

> > If this system is running RAID-6, recovery should be possible to
> > check both parity chunks, right?
> 
> Yes, of course. (And if anyone ever needs it, it is possible to extend
> raid6 to 3 parity chunks. I've done the maths, but it is not
> implemented - there doesn't seem to be a big need for it.) But - again
> referring back to Neil's blog - if the low-level raid spots a
> consistency error, it still cannot correct it reliably even with 2
> parity chunks, and should pass on a read error to the higher level
> raid.
> Using raid6 at the low level would let you do a good consistency check
> even in the case of a failed drive (or a known read error on a drive)
> -
> or two simultaneous undetected read errors. And raid6 on the higher
> level raid would let you correct such errors, even when there are
> other
> errors around. You'd soon reach the point where it is more likely for
> your disks to spontaneously turn into a bowl of petunias than for read
> errors to be undetected or unrecoverable.

That would be nice. So what should be done here in the first place, is to change the code to allow parity data to be read and calculated also on reads?

Vennlige hilsener / Best regards

roy
--
Roy Sigurd Karlsbakk
(+47) 98013356
roy@karlsbakk.net
http://blogg.karlsbakk.net/
GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
--
I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-11-27 13:56 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 13:27 Checksumming RAID? Roy Sigurd Karlsbakk
2012-11-27  9:45 ` David Brown
2012-11-27 10:17   ` Bernd Schubert
2012-11-27 11:20     ` David Brown
2012-11-27 11:39       ` Roy Sigurd Karlsbakk
2012-11-27 12:37         ` David Brown
2012-11-27 13:09           ` Roy Sigurd Karlsbakk
2012-11-27 13:20             ` David Brown
2012-11-27 13:56               ` Roy Sigurd Karlsbakk [this message]
2012-11-27 14:34                 ` David Brown
2012-11-27 20:49           ` Stan Hoeppner
2012-11-28 10:58             ` Roy Sigurd Karlsbakk
2012-11-27 12:31       ` Bernd Schubert
2012-11-27 13:05         ` David Brown
2012-11-27 18:53           ` Chris Murphy
2012-11-27 19:27             ` Roy Sigurd Karlsbakk
2012-11-27 19:50               ` Chris Murphy
2012-11-28 10:56                 ` Roy Sigurd Karlsbakk
2012-11-28 10:59                   ` Roy Sigurd Karlsbakk
2012-11-28 13:25                   ` Drew
2012-11-28 17:51                     ` Roy Sigurd Karlsbakk
2012-11-28 19:16                       ` Chris Murphy
2012-11-28 19:08                   ` Chris Murphy
2012-11-28 19:18                     ` Roy Sigurd Karlsbakk
2012-11-28 20:02                       ` Chris Murphy
2012-11-27 13:54       ` Joe Landman
2012-11-27 18:48   ` Chris Murphy
2012-11-27 19:36     ` Chris Murphy
2012-12-03 12:24 ` Pasi Kärkkäinen
2012-12-03 14:09   ` Checksumming RAID? / SCSI SAS T10 PI and DIF/DIX / T13 SATA EPP Pasi Kärkkäinen
2012-12-05 19:05     ` Martin K. Petersen
2012-12-06 11:10       ` John Robinson

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=25425956.18.1354024591879.JavaMail.root@zimbra \
    --to=roy@karlsbakk.net \
    --cc=bernd.schubert@fastmail.fm \
    --cc=david.brown@hesbynett.no \
    --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).