Provided by: lvm2_2.02.133-1ubuntu10_amd64 bug


       lvremove — remove a logical volume


       lvremove  [-A|--autobackup  {y|n}] [--commandprofile ProfileName] [-d|--debug] [-h|--help]
       [-S|--select Selection] [-t|--test] [-v|--verbose] [--version] [-f|--force] [--noudevsync]


       lvremove  removes  one  or  more  logical  volumes.  Confirmation will be requested before
       deactivating any active logical volume  prior  to  removal.   Logical  volumes  cannot  be
       deactivated  or  removed  while they are open (e.g. if they contain a mounted filesystem).
       Removing an origin logical volume will also remove all dependent snapshots.

       If the logical volume is clustered then it must be deactivated on all nodes in the cluster
       before it can be removed. A single lvchange command issued from one node can do this.


       See lvm(8) for common options.

       -f, --force
              Remove  active  logical  volumes without confirmation.  Tool will try to deactivate
              unused volume.  To proceed with damaged pools use -ff

              Disable udev synchronisation. The process will not wait for notification from udev.
              It  will  continue  irrespective of any possible udev processing in the background.
              You should only use this if udev is not  running  or  has  rules  that  ignore  the
              devices LVM2 creates.


       Remove  the  active  logical  volume  lvol1  in  volume  group  vg00  without  asking  for

       lvremove -f vg00/lvol1

       Remove all logical volumes in volume group vg00:

       lvremove vg00


       lvcreate(8), lvdisplay(8), lvchange(8), lvm(8), lvs(8), lvscan(8), vgremove(8)