From: Chris Mason <chris.mason@oracle.com>
To: Gregory Farnum <gregory.farnum@dreamhost.com>
Cc: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
linux-scsi@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Sven Breuner <sven.breuner@itwm.fraunhofer.de>,
Chuck Lever <chuck.lever@oracle.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
lsf-pc@lists.linux-foundation.org
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] end-to-end data and metadata corruption detection
Date: Wed, 1 Feb 2012 11:45:21 -0500 [thread overview]
Message-ID: <20120201164521.GY16796@shiny> (raw)
In-Reply-To: <CAF3hT9AgVpcZkGLkr4EH4x4heNFgxNykM4Mp3V_C-RBSwJh7mA@mail.gmail.com>
On Tue, Jan 31, 2012 at 11:28:26AM -0800, Gregory Farnum wrote:
> On Tue, Jan 31, 2012 at 11:22 AM, Bernd Schubert
> <bernd.schubert@itwm.fraunhofer.de> wrote:
> > I guess we should talk to developers of other parallel file systems and see
> > what they think about it. I think cephfs already uses data integrity
> > provided by btrfs, although I'm not entirely sure and need to check the
> > code. As I said before, Lustre does network checksums already and *might* be
> > interested.
>
> Actually, right now Ceph doesn't check btrfs' data integrity
> information, but since Ceph doesn't have any data-at-rest integrity
> verification it relies on btrfs if you want that. Integrating
> integrity verification throughout the system is on our long-term to-do
> list.
> We too will be said if using a kernel-level integrity system requires
> using DIO, although we could probably work out a way to do
> "translation" between our own integrity checksums and the
> btrfs-generated ones if we have to (thanks to replication).
DIO isn't really required, but doing this without synchronous writes
will get painful in a hurry. There's nothing wrong with letting the
data sit in the page cache after the IO is done though.
-chris
next prev parent reply other threads:[~2012-02-01 16:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 20:15 [LSF/MM TOPIC] end-to-end data and metadata corruption detection Chuck Lever
2012-01-17 20:15 ` Chuck Lever
2012-01-26 12:31 ` Bernd Schubert
2012-01-26 12:31 ` Bernd Schubert
2012-01-26 14:53 ` Martin K. Petersen
2012-01-26 14:53 ` Martin K. Petersen
2012-01-26 16:27 ` Bernd Schubert
2012-01-26 16:27 ` Bernd Schubert
2012-01-26 23:21 ` James Bottomley
2012-01-31 19:16 ` Bernd Schubert
2012-01-31 19:16 ` Bernd Schubert
2012-01-31 19:21 ` Chuck Lever
2012-01-31 20:04 ` Martin K. Petersen
2012-01-31 2:10 ` Martin K. Petersen
2012-01-31 19:22 ` Bernd Schubert
2012-01-31 19:28 ` Gregory Farnum
2012-02-01 16:45 ` Chris Mason [this message]
2012-02-01 16:52 ` [Lsf-pc] " James Bottomley
2012-02-01 17:41 ` Chris Mason
2012-02-01 17:41 ` Chris Mason
2012-02-01 17:59 ` Bernd Schubert
2012-02-01 18:16 ` James Bottomley
2012-02-01 18:30 ` Andrea Arcangeli
2012-02-02 9:04 ` Bernd Schubert
2012-02-02 19:26 ` Andrea Arcangeli
2012-02-02 19:46 ` Andreas Dilger
2012-02-02 19:46 ` Andreas Dilger
2012-02-02 22:52 ` Bernd Schubert
2012-02-02 22:52 ` Bernd Schubert
2012-02-01 18:15 ` Martin K. Petersen
2012-02-01 23:03 ` Boaz Harrosh
2012-02-01 23:03 ` Boaz Harrosh
2012-02-01 23:03 ` Boaz Harrosh
[not found] ` <DE0353DF-83EA-480E-9C42-1EE760D6EE41@dilger.ca>
2012-01-31 2:22 ` Martin K. Petersen
2012-01-31 2:22 ` Martin K. Petersen
2012-01-26 15:36 ` Martin K. Petersen
2012-01-26 15:36 ` Martin K. Petersen
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=20120201164521.GY16796@shiny \
--to=chris.mason@oracle.com \
--cc=bernd.schubert@itwm.fraunhofer.de \
--cc=chuck.lever@oracle.com \
--cc=gregory.farnum@dreamhost.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=martin.petersen@oracle.com \
--cc=sven.breuner@itwm.fraunhofer.de \
/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.