Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
The ONE Campaign to make poverty history

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 79 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       pvmove  [-A|--autobackup{y|n}]  [-d|--debug]  [-f|--force]
       [-h|--help]     [-i|--ignore_read_errors]      [-t|--test]
       [-v[v]|--verbose    [--verbose]]   [{-n|--name}LogicalVol­
       ume[:LogicalExtent[-LE]...]]  SourcePhysicalVolume[:Physi­
       calExtent[-PE]...]                [DestinationPhysicalVol­


       pvmove allows you to move the allocated  physical  extents
       (PEs)  on SourcePhysicalVolume to one or more other physi­
       cal volumes (PVs).  You can optionally select a subset  of
       the  allocated physical extents on SourcePhysicalVolume by
       giving colon-separated lists  and/or  ranges  of  physical
       extents, or by specifying the source LogicalVolume option­
       ally with colon-separated lists and/or ranges  of  logical
       extents.   In  this  case  only these extents are moved to
       free (or  specified)  extents  on  DestinationPhysicalVol­
       ume(s).   If no DestinationPhysicalVolume is specifed, the
       normal allocation rules for the volume group are used.

       You can move physical extents in use  but  make  sure  you
       have  an  current  backup  in case of a system crash while

       pvmove may be safely interrupted by  SIGINT  while  moving
       "next  free"  allocated  logical volumes.  Striped logical
       volume moves can't be interrupted by SIGINT  because  that
       may cause stripe inconsistencies.

       -A, --autobackup {y|n}
              Controls  automatic backup of VG metadata after the
              move (see vgcfgbackup (8)).  Default is yes.

       -d, --debug
              Enables additional debugging  output  (if  compiled
              with DEBUG).

       -f, --force
              Forces physical extent move without confirmation.

       -h, --help
              Print  a  usage message on standard output and exit

       -i, --ignore_read_errors
              Ignore read errors while moving  data.  Usefull  in
              case  data is moved away from a broken or unaccess­
              able disk (area).

       -n,    --name     LogicalVolume[:LogicalExtent[-LogicalEx­


       To  move  all  logical  extents  of any logical volumes on
       /dev/hda4 to free physical extents elsewhere in the volume
       group, giving verbose runtime information, use:

            pvmove -v /dev/hda4

       To  move  three  logical  extents (numbers 3, 5 and 11) of
       logical volume my_lv to free ones on /dev/hdb3 use:

            pvmove -n my_lv:3:5:11 /dev/sdb6 /dev/hdb3

       To move four logical extents (numbers 1, 25, 26,  and  27)
       of  logical  volume  my_lv  on  /dev/sdb6 to four physical
       extents (numbers 46, 47, 48, and 49) on /dev/hdb3 use:

            pvmove -n my_lv:1:25-27 /dev/sdb6 /dev/hdb3:46-49


       pvmove returns an exit code of 0 for success and >  0  for

       1  no source physical volume on command line
       2  invalid extent numbers on command line
       2  invalid source physical volume name
       4  error reading physical volume
       5  source physical volume is inconsistent
       6  volume group doesn't exist
       7  error reading VGDA
       8  volume group is inconsistent
       9  error getting index of physical volume
       10 no logical volumes on source physical volume
       12 invalid logical volume name
       13 error getting logical volume number in VGDA
       14 logical volume not on source physical volume
       15 malloc() error
       16 invalid physical volume name
       17 physical volume doesn't belong to this volume group
       18 more than one physical volume with destination physical extents given
       19 error getting index of logical volume from VGDA
       20 invalid logical extent given
       21 invalid physical extent given
       22 destination physical index in use
       23 error moving physical extent(s)

       95 driver/module not in kernel
       96 invalid I/O protocol version
       97 error locking logical volume manager
       98 invalid lvmtab (run vgscan(8))
       99 invalid command line

              This  variable  determines the backup history depth
              of kept VGDA copy files in /etc/lvmconf.  It can be
              set  to  a  positive number between 0 and 999.  The
              higher this number is, the  more  changes  you  can
              restore using vgcfgrestore(8).


       lvm(8),  lvchange(8),  lvcreate(8),  lvdisplay(8),  pvdis­


       Heinz Mauelshagen <Linux-LVM@Sistina.com>

Heinz Mauelshagen           LVM TOOLS                   PVMOVE(8)

There are several different ways to navigate the tutorial.



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
You can help in many different ways.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.08 Seconds