Description of problem: pvmove should behave like other lvm cmds: [root@taft-04 ~]# pvremove Please enter a physical volume path pvremove: Remove LVM label(s) from physical volume(s) pvremove [-d|--debug] [-f[f]|--force [--force]] [-h|-?|--help] [-t|--test] [-v|--verbose] [-y|--yes] [--version] PhysicalVolume [PhysicalVolume...] [root@taft-04 ~]# pvresize Please supply physical volume(s) pvresize: Resize physical volume(s) pvresize [-d|--debug] [-h|-?|--help] [--setphysicalvolumesize PhysicalVolumeSize[kKmMgGtT] [-t|--test] [-v|--verbose] [--version] PhysicalVolume [PhysicalVolume...] [root@taft-04 ~]# pvchange Please give exactly one option of -x, -uuid, --addtag or --deltag pvchange: Change attributes of physical volume(s) pvchange [-a|--all] [-A|--autobackup y|n] [-d|--debug] [-h|--help] [-t|--test] [-u|--uuid] [-x|--allocatable y|n] [-v|--verbose] [--addtag Tag] [--deltag Tag] [--version] [PhysicalVolumePath...] [root@taft-04 ~]# pvmove [root@taft-04 ~]# Version-Release number of selected component (if applicable): [root@taft-04 ~]# rpm -q lvm2 lvm2-2.02.06-6.0.RHEL4
Apparently, a pvmove without any args is supposed to pick up where an old pvmove attempt may have left off.