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.
Bug 1284197 - pvmove: "No data to move for ..." gives non-zero exit code
Summary: pvmove: "No data to move for ..." gives non-zero exit code
Keywords:
Status: CLOSED DUPLICATE of bug 1181121
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ondrej Kozina
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-21 21:07 UTC by Andrey Utkin
Modified: 2021-09-03 12:40 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-23 10:21:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Andrey Utkin 2015-11-21 21:07:25 UTC 
Description of problem:
I am using such a command during LVM partition shrinking procedure.
pvmove --allocate anywhere /dev/X 

It gives "No data to move for ..." and returns non-zero code to shell. But the outcome is perfectly correct so that procedure can go forward. This should be fixed for successful scripting.

Version-Release number of selected component (if applicable):

sys-fs/lvm2-2.02.116-r2 (gentoo)
Comment 2 Ondrej Kozina 2015-11-23 09:24:27 UTC 
Hello Andrey,

I believe this is duplicate of bug 1181121. Could you elaborate your use case a bit or do you agree that the proposed solution in bug 1181121, comment 4 will work for you as well?
Comment 3 Andrey Utkin 2015-11-23 09:48:55 UTC 
Really a duplicate. So I am not alone surprised. Feel free to close this ticket.
Comment 4 Ondrej Kozina 2015-11-23 10:21:52 UTC 

*** This bug has been marked as a duplicate of bug 1181121 ***
Note You need to log in before you can comment on or make changes to this bug.