Bug 284771

Summary: RFE: pvmove: give better diagnostic for invalid "-n LV" name
Product: [Fedora] Fedora Reporter: Jim Meyering <meyering>
Component: lvm2Assignee: Milan Broz <mbroz>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: agk, dwysocha, mbroz, prockai, pvrabec
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 2.02.34 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-07-31 14:38:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
show pvmove's misleading diagnostic
none
Proposed patch none

Description Jim Meyering 2007-09-10 16:30:52 UTC 
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:
Comment 1 Jim Meyering 2007-09-10 16:30:52 UTC 
Created attachment 191761 [details]
show pvmove's misleading diagnostic
Comment 2 Milan Broz 2008-04-03 15:50:39 UTC 
Created attachment 300272 [details]
Proposed patch
Comment 3 Milan Broz 2008-04-04 12:00:34 UTC 
Patch is in upstream cvs.
Comment 4 Jon Stanley 2008-04-23 20:30:03 UTC 
Adding FutureFeature keyword to RFE's.
Comment 5 Milan Broz 2008-07-31 14:38:09 UTC 
This is already fixed in rawhide since lvm2 2.02.34.