linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Random bit flips - better data integrity needed [Was: Re: 	mismatch_count != 0 on multiple hosts]
Date: Sun, 20 Sep 2009 10:36:08 +0100	[thread overview]
Message-ID: <4AB5F788.6090701@anonymous.org.uk> (raw)
In-Reply-To: <87f94c370909190910s6992a671re507ddcf91ea623e@mail.gmail.com>

On 19/09/2009 17:10, Greg Freemyer wrote:
[...]
> I don't know how specifically, but it also seems to me the mdraid
> stack could add to currently poor data integrity process even in the
> absence of a supporting scsi subsystem.  Maybe by pulling out the
> integrity checksum / crc info and putting it on yet another disk, or
> mixing it in with the parity calculation.
> 
> Specifically you could steal the second parity stripe from a raid 6
> setup and replace it with this end-to-end data integrity checksum /
> crc.  The checksum / crc is much smaller than the original data so the
> one integrity disk should support a reasonable number of data disks.
> Obviously this would not be one of the formal raid levels, but that
> doesn't mean its not useful.

I vaguely remember someone here was prototyping/developing a device 
mapper thingy which added checksumming/integrity to simulate high-end 
RAID cards adding a checksum to each 512-byte sector by using 520- or 
528-byte sectors on their component discs. I don't remember the details, 
but what I have in mind was something along the lines of using an extra 
sector on the underlying device per 64 sectors or so. There wouldn't be 
too heavy an overhead on small reads - we do readahead anyway - and it 
would make small writes even more painful than they are already, but 
shouldn't significantly reduce throughput on large (chunk size) reads 
and writes. I'd use it.

Cheers,

John.

  reply	other threads:[~2009-09-20  9:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19 16:10 Random bit flips - better data integrity needed [Was: Re: mismatch_count != 0 on multiple hosts] Greg Freemyer
2009-09-20  9:36 ` John Robinson [this message]
2009-09-20  9:43   ` Majed B.
2009-09-20 15:30 ` Mario 'BitKoenig' Holbe
2009-09-20 21:55   ` Random bit flips - better data integrity needed Martin K. Petersen
2009-09-20 21:48 ` Martin K. Petersen
2009-09-22 11:18 ` Random bit flips - better data integrity needed [Was: Re: mismatch_count != 0 on multiple hosts] Matthias Urlichs
2009-10-13 21:45   ` Bill Davidsen

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=4AB5F788.6090701@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=greg.freemyer@gmail.com \
    --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).