I have a bug in the ZFS Crypto Alpha binaries where I'm tripping over an
assert that I put in to check that io_crypt is valid. The zio_t that
was in progess has io_checksum, io_compress and io_crypt all set to 0
(ie ZIO_C*_INHERIT). Why would we have written these to disk and what
does it mean ?
The assert I have is in both zio_encrypt_data and zio_decrypt_data:
ASSERT3U(crypt, !=, ZIO_CRYPT_INHERIT);
So somehow we managed to write something to disk with io_crypt set to 0
and we are failing on reading it.
Is it valid to store ZIO_CHECKSUM_INHERIT/ZIO_COMPRESS_INHERIT on disk,
if so I guess I need to work out how to deal with ZIO_CRYPT_INHERIT
being stored on disk.
The crash dump files (thanks to Tim Foster) is on stinger4p-3.west core
file number 6.
--
Darren J Moffat
