+++ This bug was initially created as a clone of Bug #284771 +++ RHEL4 clone Description of problem: I was following an example from a non-RH (or old?) version of the pvmove man page (http://linux.about.com/library/cmd/blcmdl8_pvmove.htm), that suggested using pvmove's "-n vg_name:PE" option, e.g., "-n vg1:0". However, using a PE range there is not valid, and makes pvmove complain, just as if one had specified any invalid VG name. FWIW, the PE range must be appended to the source or dest device name. Version-Release number of selected component (if applicable): LVM version: 2.02.27 (2007-07-17) How reproducible: see attached script Steps to Reproduce: 1. run the script, and note the "No data to move for vg-pvmove-demo" diagnostic ... -- Additional comment from mbroz on 2008-04-04 08:00 EST -- Patch is in upstream cvs.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Fix verified in lvm2-2.02.37-3.el4 [root@taft-03 dev]# pvmove -n taft:0 /dev/sdc#_%\($\" /dev/sdb1 Logical volume name taft:0 is invalid Run `pvmove --help' for more information.
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-2008-0776.html