From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Chris Murphy <lists@colorremedies.com>
Cc: xfs list <linux-xfs@vger.kernel.org>
Subject: Re: Support for data CRC
Date: Tue, 22 Aug 2017 13:10:53 +0200 [thread overview]
Message-ID: <20170822111053.7jypthbydpkn2tj4@breakpoint.cc> (raw)
In-Reply-To: <CAJCQCtSUS9yZfv9xLe9a5o5x8ZSkOUWC_6QaeUi6oQ_QXg4GRQ@mail.gmail.com>
On 2017-08-21 13:52:48 [-0600], Chris Murphy wrote:
> On Mon, Aug 21, 2017 at 1:04 PM, Sebastian Andrzej Siewior
> <sebastian@breakpoint.cc> 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?
>
> See dm-integrity, merged as of 4.12 kernel. I haven't seen any
> performance benchmarking so far.
So this ensures integrity with the help of crypto algorithms. This is a
bit much as something like crc32c/crc64 would be sufficient. However
dm-integrity does not provide a way to recover (as far as I can tell).
My idea was that if the "normal" path is faulty (and noticed by the crc
check) it (xfs or the dm layer) would try to read the data via an
alternative path if possible (say on RAID1/5/6).
Sebastian
next prev parent reply other threads:[~2017-08-22 11:10 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 [this message]
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
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=20170822111053.7jypthbydpkn2tj4@breakpoint.cc \
--to=sebastian@breakpoint.cc \
--cc=linux-xfs@vger.kernel.org \
--cc=lists@colorremedies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox