On 01/31/2011 10:30 AM, Andreas Heinlein wrote: > Expected behavior: Writing to the still mounted mapping should at least > give an error It should, at least the first flush must return error. Reading from page cache will probably not hit DM code at all, so it is possible that you can read some data without failure. Can you reproduce this on recent kernel? 2.6.32 is quite old and I expect it is some heavy patches distro kernel. > This does not happen with whole block devices as targets, which is AFAIK > the case in most uses of the device mapper. What do you mean by "whole block devices" here? Like not partitioned disk? > Since this is reproducible with other device mapper targets, I am sure > this is not a truecrypt problem. It might be related to udev, which > AFAIK should notify higher levels when a device is removed. Yes, Truecrypt uses dm-crypt here. Udev should get remove event and remove all symlinks, also there can be some higher level (udisks) which forcily removes crypt mapping when underlying device disappears. But it still must return error on write when underlying device disappeared. Milan -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
