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.
Before, an improper activation sequence was used while performing an image split operation. That caused a device-mapper table to be loaded while some of processed devices were known to be suspended. This has been fixed and the activation sequence has been reordered so that the table is always loaded at proper time.
Bug in _split_mirror_images() in mirror.c:
It has the sequence suspend, commit, activate, resume.
That sequence is not permitted - it must be suspend, commit, resume.
The activate has to be handled another way e.g. before, after, or implicitly by the existing suspend+resume detecting the requirement for it and handling it internally.
The error message is a new message to detect bugs like this so we can get them fixed. The bug itself is not a regression, as it'll have been doing the wrong thing for a long time. But in the unlikely event we find it impossible to fix this and any other similar bugs before the release, we'll disable the error message and hide the bugs again.
Comment 4Jonathan Earl Brassow
2011-09-01 19:27:47 UTC
committed upstream for LVM version 2.02.89
Comment 5Jonathan Earl Brassow
2011-09-01 19:28:48 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Before, an improper activation sequence was used while performing an image split operation. That caused a device-mapper table to be loaded while some of devices processed were known to be suspended. This has been fixed and the activation sequence has been reordered so that the table is always loaded at proper time.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-Before, an improper activation sequence was used while performing an image split operation. That caused a device-mapper table to be loaded while some of devices processed were known to be suspended. This has been fixed and the activation sequence has been reordered so that the table is always loaded at proper time.+Before, an improper activation sequence was used while performing an image split operation. That caused a device-mapper table to be loaded while some of processed devices were known to be suspended. This has been fixed and the activation sequence has been reordered so that the table is always loaded at proper time.
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-2011-1522.html