linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
Cc: linux-raid@vger.kernel.org
Subject: Re: Random bit flips - better data integrity needed
Date: Sun, 20 Sep 2009 17:55:15 -0400	[thread overview]
Message-ID: <yq17hvt5lj0.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <slrnhbcijr.f3a.Mario.Holbe@darkside.dyn.samba-tng.org> (Mario Holbe's message of "Sun, 20 Sep 2009 17:30:03 +0200")

>>>>> "Mario" == Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE> writes:

>> With regards to data storage, one major step in this direction is the
>> "integrity" patch that went into the kernel last winter (2.6.28?).

Mario> That's far from being end-to-end. Actually, it is even against
Mario> the end-to-end argument. End-to-end means from application to
Mario> application.

Oracle has a custom (as in non-POSIX) async I/O submission interface
called oracleasm.  Hooking into my Linux kernel block integrity
infrastructure I can protect the I/O all the way from within the Oracle
DB context in userland to the drive firmware and back.

We're working on a generic (as in POSIX-like) interface that allows data
integrity passthrough for normal applications.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2009-09-20 21:55 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
2009-09-20  9:43   ` Majed B.
2009-09-20 15:30 ` Mario 'BitKoenig' Holbe
2009-09-20 21:55   ` Martin K. Petersen [this message]
2009-09-20 21:48 ` Random bit flips - better data integrity needed 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=yq17hvt5lj0.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=Mario.Holbe@TU-Ilmenau.DE \
    --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).