Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When a RADI1 is converted to thinpool, device mapper spews an error, which is not fatal, but makes very little sense
How reproducible:
Everytime
Steps to Reproduce:
[root@virt-013 ~]# vgcreate vg /dev/sd{a..f}1
No physical volume label read from /dev/sdd1
Physical volume /dev/sdd1 not found
No physical volume label read from /dev/sdf1
Physical volume /dev/sdf1 not found
Physical volume "/dev/sdd1" successfully created
Physical volume "/dev/sdf1" successfully created
Volume group "vg" successfully created
[root@virt-013 ~]# lvcreate --type raid1 -L4G -n raid1 vg
Logical volume "raid1" created
[root@virt-013 ~]# lvconvert --thinpool vg/raid1
Logical volume "raid1_tmeta" created
Logical volume "lvol0" created
device-mapper: remove ioctl on failed: Device or resource busy
Converted vg/raid1 to thin pool.
Expected results:
Not seeing a message which looks as if something went wrong, when the conversion actually finished successfully.
Additional info:
lvm2-2.02.100-5.el6.x86_64
device-mapper-1.02.79-5.el6.x86_64
This error message is related to deactivation of thin pool metadata spare device which is zeroed and deactivated - this should be handled in 2.02.102 via new udev rules flags.
Comment 3RHEL Program Management
2013-10-18 02:25:20 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
[root@virt-015 ~]# lvconvert --thinpool vg/raid1
WARNING: Converting "vg/raid1" logical volume to pool's data volume.
THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.)
Do you really want to convert "vg/raid1"? [y/n]: y
Logical volume "raid1_tmeta" created
Converted "vg/raid1" to thin pool.
[root@virt-015 ~]# lvconvert --thinpool vg/raid2 --yes
WARNING: Converting "vg/raid2" logical volume to pool's data volume.
THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.)
Logical volume "raid2_tmeta" created
Converted "vg/raid2" to thin pool.
marking VERIFIED with:
lvm2-2.02.107-1.el6 BUILT: Mon Jun 23 16:44:45 CEST 2014
lvm2-libs-2.02.107-1.el6 BUILT: Mon Jun 23 16:44:45 CEST 2014
lvm2-cluster-2.02.107-1.el6 BUILT: Mon Jun 23 16:44:45 CEST 2014
udev-147-2.55.el6 BUILT: Wed Jun 18 13:30:21 CEST 2014
device-mapper-1.02.86-1.el6 BUILT: Mon Jun 23 16:44:45 CEST 2014
device-mapper-libs-1.02.86-1.el6 BUILT: Mon Jun 23 16:44:45 CEST 2014
device-mapper-event-1.02.86-1.el6 BUILT: Mon Jun 23 16:44:45 CEST 2014
device-mapper-event-libs-1.02.86-1.el6 BUILT: Mon Jun 23 16:44:45 CEST 2014
device-mapper-persistent-data-0.3.2-1.el6 BUILT: Fri Apr 4 15:43:06 CEST 2014
cmirror-2.02.107-1.el6 BUILT: Mon Jun 23 16:44:45 CEST 2014
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2014-1387.html
Description of problem: When a RADI1 is converted to thinpool, device mapper spews an error, which is not fatal, but makes very little sense How reproducible: Everytime Steps to Reproduce: [root@virt-013 ~]# vgcreate vg /dev/sd{a..f}1 No physical volume label read from /dev/sdd1 Physical volume /dev/sdd1 not found No physical volume label read from /dev/sdf1 Physical volume /dev/sdf1 not found Physical volume "/dev/sdd1" successfully created Physical volume "/dev/sdf1" successfully created Volume group "vg" successfully created [root@virt-013 ~]# lvcreate --type raid1 -L4G -n raid1 vg Logical volume "raid1" created [root@virt-013 ~]# lvconvert --thinpool vg/raid1 Logical volume "raid1_tmeta" created Logical volume "lvol0" created device-mapper: remove ioctl on failed: Device or resource busy Converted vg/raid1 to thin pool. Expected results: Not seeing a message which looks as if something went wrong, when the conversion actually finished successfully. Additional info: lvm2-2.02.100-5.el6.x86_64 device-mapper-1.02.79-5.el6.x86_64