[Bug 1540401] Comment bridged from LTC Bugzilla

2016-03-03 Thread bugproxy
--- Comment From manju...@in.ibm.com 2016-03-03 08:04 EDT---
(In reply to comment #78)
> I verified the problem is resolved w/ the package in -proposed on the QEMU
> guest scenario.
> Waiting on bug repoter's verification, then will mark verification-done.
>
> Thanks

Thank you Mauricio !!

I verified the same on PowerVM Lpar scenario, issue is fixed with
packages in -proposed :

root@miglp2:~# dpkg -l|grep multipath
ii  multipath-tools0.4.9-3ubuntu7.10ppc64el 
 maintain multipath block device access
ii  multipath-tools-boot   0.4.9-3ubuntu7.10all 
 Support booting from multipath devices

Lpar boots up with /boot :
---
root@miglp2:~# df |grep boot
/dev/mapper/mpath3-part2241965   60518168955  27% /boot

Thanks,
Manju

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-03-03 Thread bugproxy
--- Comment From manju...@in.ibm.com 2016-03-03 08:04 EDT---
(In reply to comment #78)
> I verified the problem is resolved w/ the package in -proposed on the QEMU
> guest scenario.
> Waiting on bug repoter's verification, then will mark verification-done.
>
> Thanks

Thank you Mauricio !!

I verified the same on PowerVM Lpar scenario, issue is fixed with
packages in -proposed :

root@miglp2:~# dpkg -l|grep multipath
ii  multipath-tools0.4.9-3ubuntu7.10ppc64el 
 maintain multipath block device access
ii  multipath-tools-boot   0.4.9-3ubuntu7.10all 
 Support booting from multipath devices

Lpar boots up with /boot :
---
root@miglp2:~# df |grep boot
/dev/mapper/mpath3-part2241965   60518168955  27% /boot

Thanks,
Manju

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-03-02 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-03-02 18:41 EDT---
I verified the problem is resolved w/ the package in -proposed on the QEMU 
guest scenario.
Waiting on bug repoter's verification, then will mark verification-done.

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-03-02 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-03-02 18:41 EDT---
I verified the problem is resolved w/ the package in -proposed on the QEMU 
guest scenario.
Waiting on bug repoter's verification, then will mark verification-done.

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-25 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-25 12:18 EDT---
Hi @mathieu-tl,

(In reply to comment #69)
> It's on my list, yes.
>
> The idea however is that I haven't uploaded it because it is so annoying to
> test these patches from a PPA, I uploaded the changes for xenial to the
> archive for further testing since it looked like it worked sufficiently to
> not break too many use cases.

Ok. Thanks for the update.

If that helps, I've been testing that more manually, either installing
the packages at the end of the installation (cd /target/tmp && wget
<...>.deb && chroot /target dpkg -i /target/tmp/*.deb), or by installing
the packages after system is already installed (just manually fixing the
boot problem at initramfs time break=pre-multipath for example).

Regards.

--- Comment From mauri...@br.ibm.com 2016-02-25 12:21 EDT---
Correction:

-packages at the end of the installation (cd /target/tmp && wget <...>.deb &&
-chroot /target dpkg -i /target/tmp/*.deb),

+packages at the end of the installation (cd /target/tmp && wget <...>.deb &&
+chroot /target dpkg -i /tmp/*.deb),

BTW, if you have a chance, it'd be nice to have a Trusty 'affects' row
for tracking purposes. Otherwise it seems this is already resolved
(despite your comment).  Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-25 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-25 12:18 EDT---
Hi @mathieu-tl,

(In reply to comment #69)
> It's on my list, yes.
>
> The idea however is that I haven't uploaded it because it is so annoying to
> test these patches from a PPA, I uploaded the changes for xenial to the
> archive for further testing since it looked like it worked sufficiently to
> not break too many use cases.

Ok. Thanks for the update.

If that helps, I've been testing that more manually, either installing
the packages at the end of the installation (cd /target/tmp && wget
<...>.deb && chroot /target dpkg -i /target/tmp/*.deb), or by installing
the packages after system is already installed (just manually fixing the
boot problem at initramfs time break=pre-multipath for example).

Regards.

--- Comment From mauri...@br.ibm.com 2016-02-25 12:21 EDT---
Correction:

-packages at the end of the installation (cd /target/tmp && wget <...>.deb &&
-chroot /target dpkg -i /target/tmp/*.deb),

+packages at the end of the installation (cd /target/tmp && wget <...>.deb &&
+chroot /target dpkg -i /tmp/*.deb),

BTW, if you have a chance, it'd be nice to have a Trusty 'affects' row
for tracking purposes. Otherwise it seems this is already resolved
(despite your comment).  Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-23 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-23 17:56 EDT---
Hi @mathieu-tl,

Cool, thanks; glad to see the patch made Xenial.

This is still on the queue for Trusty, correct?
- there's no 'Affects' line for Trusty on the LP bug header yet.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-23 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-23 17:56 EDT---
Hi @mathieu-tl,

Cool, thanks; glad to see the patch made Xenial.

This is still on the queue for Trusty, correct?
- there's no 'Affects' line for Trusty on the LP bug header yet.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-22 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-22 12:33 EDT---
*** Bug 129478 has been marked as a duplicate of this bug. ***

--- Comment From mauri...@br.ibm.com 2016-02-22 12:39 EDT---
*** Bug 131422 has been marked as a duplicate of this bug. ***

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-22 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-22 12:33 EDT---
*** Bug 129478 has been marked as a duplicate of this bug. ***

--- Comment From mauri...@br.ibm.com 2016-02-22 12:39 EDT---
*** Bug 131422 has been marked as a duplicate of this bug. ***

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-22 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-22 12:30 EDT---
*** Bug 131024 has been marked as a duplicate of this bug. ***

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-22 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-22 12:30 EDT---
*** Bug 131024 has been marked as a duplicate of this bug. ***

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-18 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-18 12:07 EDT---
*** Bug 137290 has been marked as a duplicate of this bug. ***

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-18 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-18 12:07 EDT---
*** Bug 137290 has been marked as a duplicate of this bug. ***

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-04 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-04 07:25 EDT---
Testing the v1 test packages from:
http://ausgsa.ibm.com/~mauricfo/public/bugs/bz135869/v1/

They include these patches (debdiffs in there):
- kpartx with spaces
- multipathd on initramfs
- lvm on multipath devices

It didn't work; getting errors from partx:
'/usr/bin/partx -d /dev/sdaa'(err) 'partx: specified range <1:0> does not make 
sense'

I'll try a few more changes.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1540401/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-04 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-04 06:30 EDT---
The test packages did not work by themselves as the LPAR uses *ibmvfc* and not 
ibmvscsi (sorry, I confused that), which has *async* SCSI scan.

So, this bug needs this patch *and* the multipathd/initramfs patch
(which doesn't fix this by itself, as verified earlier).

I'll build v1 test packages.

...
[1.558539] ibmvfc: IBM Virtual Fibre Channel Driver version: 1.0.11 (April 
12, 2013)
[1.568548] scsi host0: IBM POWER Virtual FC Adapter
[1.578741] ibmvfc 3004: Partner initialization complete
[1.588527] ibmvfc 3004: Host partition: maplev1, device: vfchost2 
U78CB.001.WZS0249-P1-C6-T1 U8247.22L.211B3DA-V2-C12 max sectors 2048
...
Begin: Discovering multipaths ... [5.179191] device-mapper: multipath 
round-robin: version 1.0.0 loaded
[5.179424] device-mapper: table: 252:2: multipath: error getting device
[5.179431] device-mapper: ioctl: error adding target to table
[5.205784] device-mapper: table: 252:2: multipath: error getting device
[5.205803] device-mapper: ioctl: error adding target to table
[5.338527] device-mapper: table: 252:6: multipath: error getting device
[5.338558] device-mapper: ioctl: error adding target to table
[5.399409] device-mapper: table: 252:6: multipath: error getting device
[5.399440] device-mapper: ioctl: error adding target to table
[5.509069] device-mapper: table: 252:6: multipath: error getting device
[5.509100] device-mapper: ioctl: error adding target to table
[5.569473] device-mapper: table: 252:6: multipath: error getting device
[5.569518] device-mapper: ioctl: error adding target to table
[5.669295] device-mapper: table: 252:6: multipath: error getting device
[5.669329] device-mapper: ioctl: error adding target to table
[5.759009] device-mapper: table: 252:6: multipath: error getting device
[5.759047] device-mapper: ioctl: error adding target to table
[5.858710] device-mapper: table: 252:6: multipath: error getting device
[5.858741] device-mapper: ioctl: error adding target to table
[5.899505] device-mapper: table: 252:6: multipath: error getting device
[5.899536] device-mapper: ioctl: error adding target to table
[6.008594] device-mapper: table: 252:6: multipath: error getting device
[6.008631] device-mapper: ioctl: error adding target to table
[6.069401] device-mapper: table: 252:6: multipath: error getting device
[6.069427] device-mapper: ioctl: error adding target to table
done.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1540401/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-04 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-04 16:52 EDT---
Hi @mathieu-tl

(In reply to comment #44)
> 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.

> My test system is indeed a ppc64el qemu VM using spapr-vscsi.

I could reproduce the problem in that scenario by using break=multipath in the 
kernel cmdline
(which forces LVM udev rules to run before multipath discovery).

> I suppose it may be that I'm using a partitioning that happens to
work?

I'd expect it to fail in any case with LVM on top of multipath devices,
and LVM scan/volume activation happening before multipath discory
(root cause: LVM locking an individual path before multipath takes it).

> Could you please add the output of: sudo dmsetup ls --tree -o
blkdevname

Sure.

qemu-kvm guest w/ ibm-vscsi:

ubuntu@mauricfo4:~$ sudo dmsetup ls --tree -o blkdevname
[sudo] password for ubuntu:
mpath0-part2  (252:2)
??mpath0  (252:0)
??  (8:16)
??  (8:0)
mpath0-part1  (252:1)
??mpath0  (252:0)
??  (8:16)
??  (8:0)
mauricfo4--vg-swap_1  (252:5)
??mpath0-part3  (252:3)
??mpath0  (252:0)
??  (8:16)
??  (8:0)
mauricfo4--vg-root  (252:4)
??mpath0-part3  (252:3)
??mpath0  (252:0)
??  (8:16)
??  (8:0)

powervm lpar w/ ibmvfc:

root@biglp1:~# dmsetup ls --tree -o blkdevname
mpath0-part2  (252:6)
??mpath0  (252:0)
??  (65:144)
??  (65:64)
??  (8:240)
??  (8:160)
??  (8:80)
??  (8:0)
mpath2  (252:2)
??  (65:176)
??  (65:96)
??  (65:16)
??  (8:192)
??  (8:112)
??  (8:32)
mpath0-part1  (252:5)
??mpath0  (252:0)
??  (65:144)
??  (65:64)
??  (8:240)
??  (8:160)
??  (8:80)
??  (8:0)
mpath1  (252:1)
??  (65:160)
??  (65:80)
??  (65:0)
??  (8:176)
??  (8:96)
??  (8:16)
biglp1--vg-root  (252:8)
??mpath0-part3  (252:7)
??mpath0  (252:0)
??  (65:144)
??  (65:64)
??  (8:240)
??  (8:160)
??  (8:80)
??  (8:0)
mpath4  (252:4)
??  (65:208)
??  (65:128)
??  (65:48)
??  (8:224)
??  (8:144)
??  (8:64)
biglp1--vg-swap_1  (252:9)
??mpath0-part3  (252:7)
??mpath0  (252:0)
??  (65:144)
??  (65:64)
??  (8:240)
??  (8:160)
??  (8:80)
??  (8:0)
mpath3  (252:3)
??  (65:192)
??  (65:112)
??  (65:32)
??  (8:208)
??  (8:128)
??  (8:48)

--- Comment From mauri...@br.ibm.com 2016-02-04 16:53 EDT---
@mathieu-tl

(In reply to comment #45)
> > My test system is indeed a ppc64el qemu VM using spapr-vscsi.
>
> I could reproduce the problem in that scenario by using break=multipath in
> the kernel cmdline
> (which forces LVM udev rules to run before multipath discovery).

Correction: break=pre-multipath

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-04 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-04 16:52 EDT---
Hi @mathieu-tl

(In reply to comment #44)
> 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.

> My test system is indeed a ppc64el qemu VM using spapr-vscsi.

I could reproduce the problem in that scenario by using break=multipath in the 
kernel cmdline
(which forces LVM udev rules to run before multipath discovery).

> I suppose it may be that I'm using a partitioning that happens to
work?

I'd expect it to fail in any case with LVM on top of multipath devices,
and LVM scan/volume activation happening before multipath discory
(root cause: LVM locking an individual path before multipath takes it).

> Could you please add the output of: sudo dmsetup ls --tree -o
blkdevname

Sure.

qemu-kvm guest w/ ibm-vscsi:

ubuntu@mauricfo4:~$ sudo dmsetup ls --tree -o blkdevname
[sudo] password for ubuntu:
mpath0-part2  (252:2)
??mpath0  (252:0)
??  (8:16)
??  (8:0)
mpath0-part1  (252:1)
??mpath0  (252:0)
??  (8:16)
??  (8:0)
mauricfo4--vg-swap_1  (252:5)
??mpath0-part3  (252:3)
??mpath0  (252:0)
??  (8:16)
??  (8:0)
mauricfo4--vg-root  (252:4)
??mpath0-part3  (252:3)
??mpath0  (252:0)
??  (8:16)
??  (8:0)

powervm lpar w/ ibmvfc:

root@biglp1:~# dmsetup ls --tree -o blkdevname
mpath0-part2  (252:6)
??mpath0  (252:0)
??  (65:144)
??  (65:64)
??  (8:240)
??  (8:160)
??  (8:80)
??  (8:0)
mpath2  (252:2)
??  (65:176)
??  (65:96)
??  (65:16)
??  (8:192)
??  (8:112)
??  (8:32)
mpath0-part1  (252:5)
??mpath0  (252:0)
??  (65:144)
??  (65:64)
??  (8:240)
??  (8:160)
??  (8:80)
??  (8:0)
mpath1  (252:1)
??  (65:160)
??  (65:80)
??  (65:0)
??  (8:176)
??  (8:96)
??  (8:16)
biglp1--vg-root  (252:8)
??mpath0-part3  (252:7)
??mpath0  (252:0)
??  (65:144)
??  (65:64)
??  (8:240)
??  (8:160)
??  (8:80)
??  (8:0)
mpath4  (252:4)
??  (65:208)
??  (65:128)
??  (65:48)
??  (8:224)
??  (8:144)
??  (8:64)
biglp1--vg-swap_1  (252:9)
??mpath0-part3  (252:7)
??mpath0  (252:0)
??  (65:144)
??  (65:64)
??  (8:240)
??  (8:160)
??  (8:80)
??  (8:0)
mpath3  (252:3)
??  (65:192)
??  (65:112)
??  (65:32)
??  (8:208)
??  (8:128)
??  (8:48)

--- Comment From mauri...@br.ibm.com 2016-02-04 16:53 EDT---
@mathieu-tl

(In reply to comment #45)
> > My test system is indeed a ppc64el qemu VM using spapr-vscsi.
>
> I could reproduce the problem in that scenario by using break=multipath in
> the kernel cmdline
> (which forces LVM udev rules to run before multipath discovery).

Correction: break=pre-multipath

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-04 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-04 08:07 EDT---
All fixed.

(In reply to comment #37)
> Testing the v1 test packages from:
> http://ausgsa.ibm.com/~mauricfo/public/bugs/bz135869/v1/

> It didn't work; getting errors from partx:
>   '/usr/bin/partx -d /dev/sdaa'(err) 'partx: specified range <1:0> does 
> not
> make sense'
>
> I'll try a few more changes.

Fixed by specifying a partition range with "kpartx -d --nr 1-1024".  e.g.,
# sed 's/partx -d/& --nr 1-1024/' -i /lib/udev/rules.d/12-dm-mpath-lvm.rules

Also had to make sure the device with LVM (/dev/sdp) was added into 
/etc/multipath/wwids,
as it was never multipathed (due to LVM locking that path), it was never added.
(wondering why it wasn't copied from the installation.. perhaps a problem w/ 
LVM/multipath on installer too)

With those 2 fixes, the system boots correctly.
I'll build v2 packages.

root@biglp1:~# mount | grep /boot
/dev/mapper/mpath0-part2 on /boot type ext2 (rw)

root@biglp1:~# mount | grep '/ '
/dev/mapper/biglp1--vg-root on / type ext4 (rw,errors=remount-ro)

root@biglp1:~# lvm pvdisplay | grep Name
PV Name   /dev/mapper/mpath0-part3
VG Name   biglp1-vg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1540401/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-04 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-04 09:52 EDT---
(In reply to comment #38)
> With those 2 fixes, the system boots correctly.
> I'll build v2 packages.

Available in
http://ausgsa.ibm.com/~mauricfo/public/bugs/bz135869/v2

With those, the boot finishes successfully.
I'll submit the new patches.

root@biglp1:~# mount | grep /boot
/dev/mapper/mpath0-part2 on /boot type ext2 (rw)

root@biglp1:~# mount | grep ' / '
/dev/mapper/biglp1--vg-root on / type ext4 (rw,errors=remount-ro)

root@biglp1:~# lvm pvdisplay | grep Name
PV Name   /dev/mapper/mpath0-part3
VG Name   biglp1-vg

root@biglp1:~# dpkg -l | grep mpathlvm
ii  kpartx 0.4.9-3ubuntu7.7mpathlvm3ppc64el 
 create device mappings for partitions
ii  kpartx-boot0.4.9-3ubuntu7.7mpathlvm3all 
 Provides kpartx during boot
ii  multipath-tools0.4.9-3ubuntu7.7mpathlvm3ppc64el 
 maintain multipath block device access
ii  multipath-tools-boot   0.4.9-3ubuntu7.7mpathlvm3all 
 Support booting from multipath devices
ii  multipath-tools-dbg0.4.9-3ubuntu7.7mpathlvm3ppc64el 
 maintain multipath block device access - debugging symbols

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-04 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-04 09:52 EDT---
(In reply to comment #38)
> With those 2 fixes, the system boots correctly.
> I'll build v2 packages.

Available in
http://ausgsa.ibm.com/~mauricfo/public/bugs/bz135869/v2

With those, the boot finishes successfully.
I'll submit the new patches.

root@biglp1:~# mount | grep /boot
/dev/mapper/mpath0-part2 on /boot type ext2 (rw)

root@biglp1:~# mount | grep ' / '
/dev/mapper/biglp1--vg-root on / type ext4 (rw,errors=remount-ro)

root@biglp1:~# lvm pvdisplay | grep Name
PV Name   /dev/mapper/mpath0-part3
VG Name   biglp1-vg

root@biglp1:~# dpkg -l | grep mpathlvm
ii  kpartx 0.4.9-3ubuntu7.7mpathlvm3ppc64el 
 create device mappings for partitions
ii  kpartx-boot0.4.9-3ubuntu7.7mpathlvm3all 
 Provides kpartx during boot
ii  multipath-tools0.4.9-3ubuntu7.7mpathlvm3ppc64el 
 maintain multipath block device access
ii  multipath-tools-boot   0.4.9-3ubuntu7.7mpathlvm3all 
 Support booting from multipath devices
ii  multipath-tools-dbg0.4.9-3ubuntu7.7mpathlvm3ppc64el 
 maintain multipath block device access - debugging symbols

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-04 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-04 13:36 EDT---
FYI.
I've been testing reboots in the LPAR (biglp1, 14.04) with PATCH V2  for 20ish 
times now.
All boots succeeded.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-04 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-04 13:36 EDT---
FYI.
I've been testing reboots in the LPAR (biglp1, 14.04) with PATCH V2  for 20ish 
times now.
All boots succeeded.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1540401] Comment bridged from LTC Bugzilla

2016-02-03 Thread bugproxy
--- Comment From mauri...@br.ibm.com 2016-02-03 19:24 EDT---
Hi @mathieu-tl,

As we just talked on IRC, the multipathd -B patches did not help here.
I'm pasting the comments about that (sorry, I forgot to mark those as external).

[reply] [-] Comment 13 Mauricio Faria De Oliveira 2016-01-25 10:39:23 BRST
Hi Manju,

(In reply to comment #12)
> Installed the suggested packages and rebooted the lpar, issue still occurs:

Thanks for verifying.

Can I check the LPAR?

<...>

[reply] [-] Comment 17 Mauricio Faria De Oliveira 2016-01-25 15:55:04 BRST
Hm, guess I got it.

This differs slightly from the other bug.
It seems that the async discovery of LVM and multipath devices is not well 
serialized, causing some inconsistencies with the access to the partitions 
(e.g., /boot).
Checking a bit more.

<...>

[reply] [-] Comment 19 Mauricio Faria De Oliveira 2016-01-25 17:55:23 BRST
The problem matches the suspicion: the LVM detection is happening before 
multipathd grabs the individual paths, and then the creation of the multipath 
map /dev/mapper/mpath0 fails, then /boot fails to mount as it's specified as 
/dev/mapper/mpath0-part2 in /etc/fstab:

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1540401/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs