Follow
Booting the Linux kernel with `ro` or running `mount -o ro` might still generate writes to the root filesystem device, which will corrupt any dmverity hashes. That's problematic.
@th One could use losetup to make a read-only copy of the block device, I guess? But it's still kind of a workaround...
@th some kind soul finally added `noload` for ext4 praises be unto them
@eqe although even with `noatime` it doesn't seem to prevent writes. I need to dig into the code to figure out where it happens.
@th This is good to know!