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.
Created attachment 422647[details]
A crude bug fix that would prevent the erroneous error message.
Description of problem:
pvmove relies on polldaemon.c:_wait_for_single_lv() to read the percentage complete on the mirror that is used to do the pvmove. However, the mirror goes away sometimes while this program is running, presumably in between init_full_scan_done(0) and locking the volume group. This would appear to be a race condition, so it only happens sometimes.
When the problem occurs, a user gets something like this printed out:
/dev/sde1: Moved: 99.6%
ABORTING: Can't find mirror LV in homedirs for /dev/sde1
This is very confusing, as the user may think that the pvmove operation failed.
Version-Release number of selected component (if applicable):
2.02.54, code appears similar in 2.02.67
How reproducible:
As this is a race condition, it does not always happen. However users have reported it happening with enough frequency to cause alarm as the error message
Steps to reproduce:
assuming /dev/sdb has two equal sized partitions of at least 10G
Setup:
pvcreate /dev/sdb1
pvcreate /dev/sdb2
vgcreate test /dev/sdb1 /dev/sdb2
lvcreate -L 9G -n t1 test /dev/sdb1
Then repeat these in an alternating manner:
pvmove -i1 /dev/sdb1
pvmove -i1 /dev/sdb2
It may take many iterations to reproduce the race, or it may never reproduce it, as other factors may be necessary to make it more likely (such as many more physical volumes).
Actual results:
Expected results:
I would expect that if the pvmove completes successfully, that pvmove would show that fact rather than abort.
Additional info:
Comment 2RHEL Program Management
2010-06-09 18:52:55 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
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
Created attachment 422647 [details] A crude bug fix that would prevent the erroneous error message. Description of problem: pvmove relies on polldaemon.c:_wait_for_single_lv() to read the percentage complete on the mirror that is used to do the pvmove. However, the mirror goes away sometimes while this program is running, presumably in between init_full_scan_done(0) and locking the volume group. This would appear to be a race condition, so it only happens sometimes. When the problem occurs, a user gets something like this printed out: /dev/sde1: Moved: 99.6% ABORTING: Can't find mirror LV in homedirs for /dev/sde1 This is very confusing, as the user may think that the pvmove operation failed. Version-Release number of selected component (if applicable): 2.02.54, code appears similar in 2.02.67 How reproducible: As this is a race condition, it does not always happen. However users have reported it happening with enough frequency to cause alarm as the error message Steps to reproduce: assuming /dev/sdb has two equal sized partitions of at least 10G Setup: pvcreate /dev/sdb1 pvcreate /dev/sdb2 vgcreate test /dev/sdb1 /dev/sdb2 lvcreate -L 9G -n t1 test /dev/sdb1 Then repeat these in an alternating manner: pvmove -i1 /dev/sdb1 pvmove -i1 /dev/sdb2 It may take many iterations to reproduce the race, or it may never reproduce it, as other factors may be necessary to make it more likely (such as many more physical volumes). Actual results: Expected results: I would expect that if the pvmove completes successfully, that pvmove would show that fact rather than abort. Additional info: