public inbox for cryptsetup@lists.linux.dev
 help / color / mirror / Atom feed
From: "Горбешко Богдан" <bodqhrohro@gmail.com>
To: cryptsetup@lists.linux.dev
Subject: Is it possible to set the amount of CRC32C hashes per a data sector in integritysetup?
Date: Sun, 10 Sep 2023 18:12:49 +0300	[thread overview]
Message-ID: <4685725c-4b76-47c2-86b8-377b4e1fc7fd@gmail.com> (raw)

I'd like to sacrifice a significant amount of disk space (let's say, 
20%) for recovery checksums: in a way RAR or Parchive can do that, or in 
a way it's implemented in some physical-level media (DVD, HDD, digital 
TV, etc.) Some of them store the checksums separately, some among the 
data; my goal is to store them among the data on the same medium.

Currently, I came up with splitting a medium into 6 even partitions and 
making a RAID 5 array out of them. It seems to work, though I was 
suggested that dm-integrity might be a more straightforward solution for 
the task. So, before I started using the RAID 5 solution in practice, 
I'd like to make sure if the same is possible with dm-integrity first.

AFAIU, the primary goal of dm-integrity is checking if the data are not 
corrupted and throwing read errors otherwise. Though it still supports 
checksums besides of hashes. Can they be used for recovering the data 
on-the-fly?

I've read the manual of integritysetup and still not sure if it's 
possible to achieve a significantly big checksum/data ratio. Reducing 
the sector size lower than 512 does not work. If I increase the tag 
size, would it be used to store a larger checksum, or just would be 
padded to store one tiny checksum per a tag? Maybe there is some other way?

Thanks.


             reply	other threads:[~2023-09-10 15:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-10 15:12 Горбешко Богдан [this message]
2023-09-10 16:53 ` Is it possible to set the amount of CRC32C hashes per a data sector in integritysetup? Michael Kjörling
2023-09-10 22:05   ` Arno Wagner
2023-09-11 10:12     ` Milan Broz

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=4685725c-4b76-47c2-86b8-377b4e1fc7fd@gmail.com \
    --to=bodqhrohro@gmail.com \
    --cc=cryptsetup@lists.linux.dev \
    /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