One of the well-known properties of
dm-crypt is that it does not handle write barriers properly and hence it requires turning off on-drive write cache to prevent corruption of filesystems. As far as I understand it is not shared by all other dm devices (like LVM w/out snapshoting).
My question is whether it is an inherent property of
dm-crypt for any reason (I cannot find any but it is possible) or is it simply not implemented (yet)?