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
2.
3.
  
Actual results:


Expected results:


Additional info: