On Tue, 15 Jun 2010, Phillip Susi wrote: > After further testing of mainline kernels, it seems that the bug was > fixed between 2.6.32 and 2.6.33. Looking over the logs, I see no > changes that were intended to fix this issue, but there were quite a > number of changes to the snapshot code. I can only conclude that these > inadvertently fixed the problem. Hi I wasn't able to reproduce this bug on any upstream kernel and I suspect it is caused by incorrect patching on Ubuntu side. Ubuntu kernels 2.6.31-16 and before don't have the bug, 2.6.31-17 and above have it. Mikulas -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
