Red Hat Bugzilla – Bug 284771
RFE: pvmove: give better diagnostic for invalid "-n LV" name
Last modified: 2013-03-13 16:41:35 EDT
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)
see attached script
Steps to Reproduce:
1. run the script, and note the "No data to move for vg-pvmove-demo" diagnostic
Created attachment 191761 [details]
show pvmove's misleading diagnostic
Created attachment 300272 [details]
Patch is in upstream cvs.
Adding FutureFeature keyword to RFE's.
This is already fixed in rawhide since lvm2 2.02.34.