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 some kind soul finally added `noload` for ext4 praises be unto them

Follow

@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.

Sign in to participate in the conversation
(void *) social site

(void*)