[Expired for lvm2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lvm2 (Ubuntu)
Status: Incomplete => Expired
--
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/1887372
Title:
Cannot create lvm upon IMSM raid array
Status in lvm2 package in Ubuntu:
Expired
Status in lvm2 source package in Focal:
Expired
Status in lvm2 source package in Groovy:
Won't Fix
Status in lvm2 source package in Hirsute:
Expired
Bug description:
The issue has been observed on 2.3.7 (Ubuntu 20.04).
Reported to lvm team:
https://bugzilla.redhat.com/show_bug.cgi?id=1855251
Steps to Reproduce:
1. Create IMSM raid array:
#mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1
#mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G
2. Create lvm volume on raid:
# pvcreate -ff -y /dev/md/vol
# vgcreate group0 /dev/md/vol
# lvcreate -Z y -y -l +100%FREE group0 -n lvm0
Actual results:
Vg creation fails.
Expected results:
LVM should be able to determine the best drive and ignore duplicates.
Additional info:
IMSM metadata is written at the end of the drive. The first drive sector
belongs to the raid volume and other metadata saved there (like lvm) can be
recognized directly on raid members.
The following patches should fix the issue (not verified yet):
https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca
https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
