Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069579
Title:
My problem seems exactly the same, except as far as I can see all
symlinks are created. Interestingly, a vgscan -y -a at the command
prompt returns immediately, without error.
I do have a rather elaborate setup, with lot's of LVs containing either
filesystems or PVs (yes, PVs in LVs) and some
I don't now much about udev works. But it starts with the highest
partition (sdb7 vg: vgswift lv: lvswift as dm-0) of the second disk
which is configured for lvm and takes than the next lower partition
(sdb6 vg: nova-volumes lv: nova-disk dm-1) and so on. Ok one reason for
the working order
While I do have nested LVMs myself, I never actually boot off nested LVM. E.g.
the inner vg is presented as top-level for the VM.
Sounds like a very interesting bug.
** Changed in: lvm2 (Ubuntu)
Assignee: (unassigned) = Dmitrijs Ledkovs (xnox)
--
You received this bug notification because
