[Pkg-cryptsetup-devel] Bug#381921:

[David Härdeman]

Rafal Krypa wrote:
> I'm sorry that I bothered you. Just the corruption that is still appearing in 
> my filesystems put me in a state where I act quicker and think less.
> That ugly corruption has nothing to do with the scenario described by me in the 
> previous report, although it would be nice if cryptsetup could at least put the 
> mapping read-only.
> Unfortunatelly I got dirty filesystem on some other mapping, and to cause me 
> more pain - this time it appeared without a single reboot.
> So it seems that some part of the kernel is doing something wrong - but is it 
> not a Debian thing - as I use a vanilla kernel.

And thinking a bit more about this...I don't see this as a problem. A 
filesystem can be mounted read-only, a block device can be read-only, 
but device-mapper (with or without crypto) is just a mapping between the 
two, so I don't see why it should support something like this.

So, I'm inclined to close this bug unless someone can convince me 
otherwise...

I've CC:ed the lvm/devmapper maintainer to perhaps get some more 
insights (this is bug #381921).

Regards,
David