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.
DescriptionCharles Butterfield
2012-12-05 02:36:16 UTC
Description of problem: When thin LV are in use, the script /etc/lvm/lvm.conf invokes /usr/sbin/thin_check (in the package device-mapper-persistent-data) which is not pulled in by the rpm/yum dependency mechanism.
Version-Release number of selected component (if applicable):
lvm2-2.02.95-10.el6_3.2.x86_64
device-mapper-persistent-data-0.1.4-1.el6.x86_64
How reproducible: Totally
Steps to Reproduce:
1. Create thin volume (without installing device-mapper-persisten-data)
2. Reboot
3. Failure to setup thin volumes at boot time (due to missing thin_check)
Actual results:
Expected results:
Additional info:
In 6.3, the feature is classed as a Technology Preview https://access.redhat.com/support/offerings/techpreview/ and so we did not want to install this package for everyone by default.
You should also note that if the machine loses power while writing to a thin device, a subsequent thin_check might sometimes fail, and if it does you then need to run the repair manually to tidy up some reference counts after incomplete I/O. See https://bugzilla.kernel.org/show_bug.cgi?id=48851 for details. We shall automate the handling of this particular situation in future.
Comment 3Charles Butterfield
2012-12-05 04:47:25 UTC