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:
We would like to be able to add and\or remove multiple tags in one lvchange command.
These changes should also be atomic.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Comment 2Heinz Mauelshagen
2010-09-15 13:28:07 UTC
For the record:
this involves being able to create and change *many* tags, hence growing the MDA size significantly (eg. ~100MB per MDA), hence we need respective scalabiliy and test coverage in order to ensure decent MDA update performance.
(In reply to comment #2)
> For the record:
>
> this involves being able to create and change *many* tags, hence growing the
> MDA size significantly (eg. ~100MB per MDA), hence we need respective
> scalabiliy and test coverage in order to ensure decent MDA update performance.
In general, what about allowing to compress the MD area containing all the LVs info? Seeing as it is all text it would compress significantly, making required IO much smaller. (This mechanism could kick in only if MD crosses certain size). This could improve performance.
This is now blocking our dev for coming release as running dozens of commands per update takes its toll and slows down our testing suites considerably.
(In reply to comment #2)
> For the record:
>
> this involves being able to create and change *many* tags, hence growing the
> MDA size significantly (eg. ~100MB per MDA), hence we need respective
> scalabiliy and test coverage in order to ensure decent MDA update performance.
Actually what is required here does not involve growing MDA size significantly at all. What is required is to be able to change less than 100 tags simultaneously and we do not need to store more than a few MB of MD.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0772.html