Comment 13 for bug 1541510

Why does it even try to activate the dasd code on a logical volume? It shouldn't be doing that at all as it should not know or care that the logical volume is built on top of a dasd disk. Unless... iirc there was some special ioctl that dasd disks have and that is how parted knows it is dasd... maybe device-mapper is passing this ioctl down and so parted really is talking to a dasd disk?