Bug 252151 - can't move lvs out from a metadatacopies=0 pv
can't move lvs out from a metadatacopies=0 pv
Status: CLOSED DUPLICATE of bug 252150
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: lvm2 (Show other bugs)
5.0
All Linux
low Severity high
: ---
: ---
Assigned To: Milan Broz
Corey Marthaler
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-08-14 06:37 EDT by Janne Peltonen
Modified: 2013-02-28 23:05 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-08-14 06:50:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Janne Peltonen 2007-08-14 06:37:32 EDT
Description of problem:

If I try to pvmove lv's out of a pv I created using the metadatacopies 0
option, pvmove concludes that the source physical volume is not in a
volume group and refuses to commence with the move. This is, at least, within a
clustered vg.

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

lvm2-2.02.16-3.el5
lvm2-cluster-2.02.16-3.el5

How reproducible:

Steps to Reproduce:
1. create some physical volumes with the --metadatacopies 0 option
2. add these pvs into a vg
3. create some lvs in these pvs / pvmove some (extents of) existing lvs into
these new pvs
4. try to pvmove the extents out from these new pvs
  
Actual results:

pvmove says the pv isn't in a volume group, gives usage and exits

Expected results:

pvmove should move the lvs (extents) from the metadatacopies 0 pv into another pv
Comment 1 Milan Broz 2007-08-14 06:50:15 EDT

*** This bug has been marked as a duplicate of 252150 ***

Note You need to log in before you can comment on or make changes to this bug.