[pkg-cryptsetup-devel] Bug#949336: Mapped integrity devices of size ≥2TiB are unusable on 32-bits platforms

Guilhem Moulin guilhem at debian.org
Mon Jan 20 13:11:26 GMT 2020


Control: tag -1 upstream

Hi,

On Sun, 19 Jan 2020 at 23:41:15 +0000, nbf at waifu.club wrote:
> clarification: I am testing it with a volume I created and used with
> cryptsetup 2:2.0. With 2:2.1 and 2:2.2 integritysetup-open seems to succeed,
> but the embedded ext4 filesystem cannot be used. Attempt to read the
> superblock raise I/O errors due to integrity mismatches.

I won't be able to help debugging this as I don't have a >2TiB disk
around.  (Could fake the size and format with --no-wipe, but the
resulting device contains invalid checksums for obvious reasons,
regardless of the architecture.)  Milan, should I forward that upstream
(verbatim)?

Cheers,
-- 
Guilhem.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/attachments/20200120/31a7f390/attachment.sig>


More information about the pkg-cryptsetup-devel mailing list