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?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541510 Title: parted crashes on lvm, on a dasd drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1541510/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
