public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>,
	linux-xfs@vger.kernel.org
Subject: Re: Support for data CRC
Date: Mon, 21 Aug 2017 22:51:36 -0700	[thread overview]
Message-ID: <20170822055136.GA2697@infradead.org> (raw)
In-Reply-To: <20170821230232.GS10621@dastard>

On Tue, Aug 22, 2017 at 09:02:32AM +1000, Dave Chinner wrote:
> On Mon, Aug 21, 2017 at 09:04:15PM +0200, Sebastian Andrzej Siewior wrote:
> > Hi,
> > 
> > my understanding is that only metadata is protected by CRC in the new
> > on-disk format. Are there any plans to also protect data?
> 
> Not in XFS.

I had at least some customer interest in it, although not in the short
term.  Now that we have reflink we can do the required copy on write
mechanisms, but I've not done any more detailed analysis of potential
implementations yet.

  reply	other threads:[~2017-08-22  5:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21 19:04 Support for data CRC Sebastian Andrzej Siewior
2017-08-21 19:52 ` Chris Murphy
2017-08-22 11:10   ` Sebastian Andrzej Siewior
2017-08-22 22:37     ` Chris Murphy
2017-09-10 19:43       ` Testing dm-integrity (WAS: Re: Support for data CRC) Sebastian Andrzej Siewior
2017-09-10 20:06         ` Milan Broz
2017-09-11  6:38           ` Sebastian Andrzej Siewior
2017-09-11 23:44             ` Mikulas Patocka
2017-08-21 23:02 ` Support for data CRC Dave Chinner
2017-08-22  5:51   ` Christoph Hellwig [this message]
2017-08-22 11:13     ` Sebastian Andrzej Siewior
2017-08-23  6:19       ` Christoph Hellwig
2017-09-10 19:50         ` Sebastian Andrzej Siewior
2017-09-11  6:37           ` Christoph Hellwig
2017-09-11  6:52             ` Dave Chinner

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=20170822055136.GA2697@infradead.org \
    --to=hch@infradead.org \
    --cc=david@fromorbit.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sebastian@breakpoint.cc \
    /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