[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2021-02-08 Thread Frank Heimes
Sorry, I can't answer that for huge LVM installations. But what I can say is that it is for s390x installations (multipath with LVMs on top) a kind of immediately responding. One thought is to check/do this for example at the end of the dist- upgrade process, where a potential delay wouldn't be

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2021-02-08 Thread Dimitri John Ledkov
> So one solution to this would be to run "vgck --updatemetadata" on each vg in postinst... would there be downside to that? how slow is it on very very large LVMs? Is it distructive? Maybe something to check with devops-y people, like I.S. / bootstack? -- You received this bug notification

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2021-02-01 Thread Brian Murray
** Changed in: lvm2 (Ubuntu Focal) Milestone: ubuntu-20.04.2 => focal-updates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1874381 Title: LVM device unavailable after

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2021-01-08 Thread Brian Murray
** Changed in: lvm2 (Ubuntu Focal) Milestone: ubuntu-20.04.1 => ubuntu-20.04.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1874381 Title: LVM device unavailable after

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-10-14 Thread Matthieu Clemenceau
** Tags added: fr-81 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1874381 Title: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-07-17 Thread veribaka
Hello, please see https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887964 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1874381 Title: LVM device unavailable after 18.04

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-07-09 Thread Michael Hudson-Doyle
So one solution to this would be to run "vgck --updatemetadata" on each vg in postinst... would there be downside to that? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu.

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-07-07 Thread John George
I redeployed the system where this failures was original observed and recreated the issue. Running 'sudo vgck --updatemetadata s5lp8-vg' did work around this bug, when run after the upgrade but prior to the reboot. Here is the vgdisplay output requested by Steve: ubuntu@s5lp8:~$ sudo vgdisplay

Re: [Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-06-08 Thread Brian Murray
On Fri, Jun 05, 2020 at 09:38:35AM -, veribaka wrote: > Is there a time frame to consider that the original reporter will not be > returning to this discussion? > > Should I open my own bug report with my logs? Please do open your own bug report with the relevant log files and make a comment

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-06-05 Thread veribaka
Is there a time frame to consider that the original reporter will not be returning to this discussion? Should I open my own bug report with my logs? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu.

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-05-27 Thread Steve Langasek
awaiting feedback from the original reporter to confirm that these particular commands are applicable to his install. ** Changed in: lvm2 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-05-27 Thread veribaka
Reporting back: "sudo vgck -t vg" reports that no changes would be made, it seems to be looking in /dev/sda rather than /dev/nvme0n1. "sudo vgscan" first reports that /dev/sda open failed and then successfully detects the vg using metadata type lvm2. -- You received this bug notification

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-05-22 Thread Serhiy Zahoriya
You need to either execute these commands after upgrade and _before_ rebooting or chroot from a LiveUSB boot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1874381 Title:

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-05-22 Thread veribaka
I too tried to upgrade from 18.04 and ended up with a busybox, Ubuntu not finding my vg. Not sure how to enter those commands from a busybox Steve. Re-imaging the device with 18.04 for the time being. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-05-22 Thread Francis Ginther
** Tags added: id-5ec6a06d9ddd891b690ef2e4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1874381 Title: LVM device unavailable after 18.04 to 20.04 upgrade Timed out

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-05-21 Thread Steve Langasek
You might also want to try 'sudo vgck -t s5lp8-vg' first before committing changes with --updatemetadata. ** Changed in: lvm2 (Ubuntu Focal) Milestone: None => ubuntu-20.04.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-05-21 Thread Steve Langasek
John, are you able to confirm that a 'sudo vgck --updatemetadata s5lp8-vg' fixes this for you? Also, before running that command, can you post the output of 'sudo vgdisplay' on this system? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

2020-05-21 Thread Brian Murray
** Package changed: ubuntu-release-upgrader (Ubuntu) => lvm2 (Ubuntu) ** Tags removed: rls-ff-incoming ** Also affects: lvm2 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: lvm2 (Ubuntu Focal) Status: New => Confirmed ** Changed in: lvm2 (Ubuntu Focal)