Now all traces of the snapshot are remove. If I only "dmsetup remove"
the snapshot, but not the "-cow" it persists and prevents future
I am not sure if it is a bug in lvm2 or rather in
kernel-image-2.6.32-trunk-* and* kernel-image-2.6.32-5-* together with
udev and dm. If I downgrade lvm2 from 2.02.62-1 to 2.02.39-7 the error
remains. Instead downgrading to 2.6.26 works as before.
Shall I report the bug against linux-2.6?
The sample uses the symbolic links because I modified
/lib/udev/rules.d/55-dm.rules according to message #44 of debian bug* #581593, but with the
block device the problem and solution is the same.
@Tim: I think you were right, that the bug is the same... Sorry!
I hope the workaround helps the maintainers to find the real source of