The following tables show many tasks that help manage logical volume storage. The tables group tasks by those that primarily affect logical and physical volumes and those that primarily affect file systems. More complicated tasks are described in subsequent sections of this chapter.
Note: You must have root authority to perform most of the tasks in the following table.
Attention:
- Using this procedure to copy to an existing logical volume will overwrite any data on that volume without requesting user confirmation.
- Do not use the SMIT procedure or the cplv command to copy a larger logical volume to a smaller one. Doing so results in a corrupted file system because some of the data (including the superblock) is not copied to the smaller logical volume.
Notes:
- After you create a logical volume, the state will be closed. This means that no LVM structure is using that logical volume. It will remain closed until a file system has been mounted over the logical volume or the logical volume is opened for raw I/O. See also "Defining a Raw Logical Volume for an Application".
- You cannot change the name of, import, or export rootvg.
- You must have enough direct access storage to duplicate a specific logical volume.