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:
in case of multipath path error lvm commands are taking a long time (in my deployment it took 4.5 minutes) adding disable_after_error_count parameter to lvm.conf should put the device as disabled after a specific amount of errors has happened and make lvm and vdsm respond quicker.
Version-Release number of selected component (if applicable):
vdsm-4.9-81.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1.make a multipath path faulty
2.lvm pvs vgs takes around 4.5 -5 minutes (50 SDs connected)
3.
Actual results:
Expected results:
Additional info:
changing this config value on lvm.conf makes operations to run much faster.
Comment 3Federico Simoncelli
2011-07-20 13:41:11 UTC
Some additional notes, I just talked with Moran and "multipath path error" should be intended as "the storage is unreachable through all its paths".
Looking at the disable_after_error_count code introduced with the patch:
http://sources.redhat.com/git/gitweb.cgi?p=lvm2.git;a=commitdiff;h=74b228ee945934c3b979cbb70a29b3a721f5c683
The error_count is a one-shot value for each lvm command.
Summarizing: using disable_after_error_count has no side effects (eg: it's not permanently disabling a device) and would improve the lvm responsiveness when one storage is completely unreachable.
which value should we put in disable_after_error_count so we do not have to many false negatives? Moran, this question is directly also to your team :-)
Comment 5Federico Simoncelli
2011-07-21 07:55:30 UTC
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/RHEA-2011-1782.html