From: Konrad Rzeszutek <konrad@virtualiron.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: A simple, generic DM-API, for codecs/transcoders to use?
Date: Mon, 22 Jun 2009 11:08:49 -0400 [thread overview]
Message-ID: <20090622150849.GA23765@mars.virtualiron.com> (raw)
In-Reply-To: <49C0B79A.9010601@googlemail.com>
On Wed, Mar 18, 2009 at 09:58:02AM +0100, Navid Zamani wrote:
> Hello DM mailing list.
>
> I a have a simple question:
> Is there a way to use the device-mapper to hang an arbitrary program
> in-between a real block device, and the virtual device created by the
> device-mapper?
> Like with LUKS. Only that I do not want to compress or encrypt. I want
> to hang an error-correcting transcoder in between, so I can put ECC on
> any block device I want.
> The optimal thing would be a simple API, that is implemented in many
> languages. (Like FUSE is available in many languages.)
> Something like this would really be a powerful abstraction to have.
>
> In case you are interested in the reasons: Modern consumer HDDs do not
> have any ECC, but they get less and less reliable. It went so far, that
I thought that the more recent patches by Oracle to support DIF/DIX (Data
Integrity Extensions):
http://oss.oracle.com/projects/data-integrity/dist/documentation/linux-hba.pdf
Are addressing this by adding a checksum for each block sector that is
checked by each device. So the firmware on the hard-drive, along with
the SAS controller would carry out the checksumming?
next prev parent reply other threads:[~2009-06-22 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 8:58 A simple, generic DM-API, for codecs/transcoders to use? Navid Zamani
2009-06-22 15:08 ` Konrad Rzeszutek [this message]
2009-06-23 5:30 ` Martin K. Petersen
2009-06-22 23:13 ` Wes Felter
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=20090622150849.GA23765@mars.virtualiron.com \
--to=konrad@virtualiron.com \
--cc=dm-devel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.