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
*** This bug has been marked as a duplicate of 252150 ***