From: Craig Dunwoody <cdunwoody@graphstream.com>
To: Sage Weil <sage@newdream.net>
Cc: cdunwoody@graphstream.com, ceph-devel@lists.sourceforge.net
Subject: End to end data integrity checking in Ceph?
Date: Sun, 21 Mar 2010 13:22:29 -0700 [thread overview]
Message-ID: <29143.1269202949@n20.hq.graphstream.com> (raw)
Hi Sage,
- Some of my customers are particularly paranoid about data integrity.
I believe that there are some parallel/distributed storage systems
(Panasas? Others?) that claim to provide options for some kind of
data integrity checking within the fault domain of the client, as a
final step before delivering read-data to the application, and
perhaps also as a first step after receiving write-data from the
application.
The hope would be to catch any data corruption that could possibly
take place between clients and servers, even if relatively unlikely
(e.g. bits getting flipped in network transport).
- Does the current Ceph implementation already do some variation of
this? If not, how difficult do you think it might be to add as a
future optional feature? Could it be added without breaking
compatibility of wire-protocol and on-disk format?
Thanks in advance for any comments/suggestions on this.
Craig Dunwoody
GraphStream Incorporated
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
next reply other threads:[~2010-03-21 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 20:22 Craig Dunwoody [this message]
2010-03-22 16:58 ` End to end data integrity checking in Ceph? Sage Weil
2010-03-22 17:24 ` Craig Dunwoody
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=29143.1269202949@n20.hq.graphstream.com \
--to=cdunwoody@graphstream.com \
--cc=ceph-devel@lists.sourceforge.net \
--cc=sage@newdream.net \
/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.