This isn't obvious to reproduce. So far, I haven't had the system fail to boot or fail to mount all partitions. I have been testing *without* multipath-tools 0.4.9-3ubuntu7.8; so not using multipathd in the initramfs.
I suppose it may be that I'm using a partitioning that happens to work?
Could you please add the output of: sudo dmsetup ls --tree -o blkdevname
This isn't obvious to reproduce. So far, I haven't had the system fail to boot or fail to mount all partitions. I have been testing *without* multipath-tools 0.4.9-3ubuntu7.8; so not using multipathd in the initramfs.
I suppose it may be that I'm using a partitioning that happens to work?
Could you please add the output of: sudo dmsetup ls --tree -o blkdevname
No failure after 20 reboots:
mpath0-part1 <dm-2> (252:2)
└─mpath0 <dm-0> (252:0)
├─ <sdb> (8:16)
└─ <sda> (8:0)
mpath1 <dm-1> (252:1)
├─ <sdd> (8:48)
└─ <sdc> (8:32)
trusty-boot <dm-6> (252:6)
└─mpath0-part2 <dm-3> (252:3)
└─mpath0 <dm-0> (252:0)
├─ <sdb> (8:16)
└─ <sda> (8:0)
trusty-swap <dm-5> (252:5)
└─mpath0-part2 <dm-3> (252:3)
└─mpath0 <dm-0> (252:0)
├─ <sdb> (8:16)
└─ <sda> (8:0)
trusty-root <dm-4> (252:4)
└─mpath0-part2 <dm-3> (252:3)
└─mpath0 <dm-0> (252:0)
├─ <sdb> (8:16)
└─ <sda> (8:0)
My test system is indeed a ppc64el qemu VM using spapr-vscsi.
Will setup a new system using snapshot to test with multipath-tools 0.4.9-3ubuntu7.8.