Hey Dave,
thanks for your response!
Am 01.08.24 um 03:53 schrieb Dave Chinner:
Is there a way to mitigate it?
If you want to stop the filesystem writing to the block device, you
have to set the -block device- to be read only. At this point, the
filesystem will refuse to mount if it needs to write to the block
device during mount.
But my point is, that is what I am doing -- creating the losetup mapping
R/O:
# losetup --read-only --show -f image.img
/dev/loop35
# echo foo >/dev/loop35
bash: echo: write error: Operation not permitted
I.e., the block device is write protected and *yet* it changes content.
This is what I find so extremely puzzling, that the file system should
not have the capability to change the underlying block device, yet it does.
Cheers,
Johannes
--
"A PC without Windows is like a chocolate cake without mustard."
