Creates a logical volume.
mklv [ -a Position ] [ -b BadBlocks ] [ -c Copies ] [ -d Schedule ] [ -e Range ] [ -i ] [ -L Label ] [ -m MapFile ] [ -r Relocate ] [ -s Strict ] [ -t Type ] [ -u UpperBound ] [ -v Verify ] [ -w MirrorWriteConsistency ] [ -x Maximum ] [ -y NewLogicalVolume | -Y Prefix ] [ -S StripeSize ] VolumeGroup Number [ PhysicalVolume ... ]
The mklv command creates a new logical volume within the VolumeGroup. For example, all file systems must be on separate logical volumes. The mklv command allocates the number of logical partitions to the new logical volume. If you specify one or more physical volumes with the PhysicalVolume parameter, only those physical volumes are available for allocating physical partitions; otherwise, all the physical volumes within the volume group are available.
The default settings provide the most commonly used characteristics, but use flags to tailor the logical volume to the requirements of your system. Once a logical volume is created, its characteristics can be changed with the chlv command.
The default allocation policy is to use a minimum number of physical volumes per logical volume copy, to place the physical partitions belonging to a copy as contiguously as possible, and then to place the physical partitions in the desired region specified by the -a flag. Also, by default, each copy of a logical partition is placed on a separate physical volume.
The -m flag specifies exact physical partitions to be used when creating the logical volume.
Physical partitions are numbered starting at the outermost edge with number one.
- Changes made to the logical volume are not reflected in the file systems. To change file system characteristics use the chfs command.
- Each logical volume has a control block. This logical volume control block is the first few hundred bytes within the logical volume. Care has to be taken when reading and writing directly to the logical volume to allow for the control block. Logical volume data begins on the second 512-byte block.
- A mirrored, or copied, logical volume is not supported as the active dump device. System dump error messages will not be displayed, and any subsequent dumps to a mirrored logical volume will fail.
- To use this command, you must either have root user authority or be a member of the system group.
- When creating a striped logical volume using the -S flag, you must specify two or more physical volumes or use the -u flag.
- When creating a striped logical volume, the number of partitions must be an even multiple of the striping width.
You can use the Web-based System Manager Volumes application (wsm lvm fast path) to run this command. You could also use the System Management Interface Tool (SMIT) smit mklv fast path to run this command.
Note: The -c, -d, -e, -m, -s, and -w flags are not valid when creating a striped logical volume using the -S flag.
|-a Position|| Sets the intra-physical volume allocation policy (the position of the logical partitions on the physical volume). The Position variable can be one of the following:
|-b BadBlocks|| Sets the bad-block relocation policy. The Relocation variable can be one of the following:
|-c Copies||Sets the number of physical partitions allocated for each logical partition. The Copies variable can be set to a value from 1 to 3; the default is 1.|
|-d Schedule|| Sets the scheduling policy when more than one logical partition is written. The Schedule variable can be one of the following:
|-e Range|| Sets the inter-physical volume allocation policy (the number of physical volumes to extend across, using the volumes that provide the best allocation). The Range value is limited by the UpperBound variable, (set with the -u flag) and can be one of the following:
|-i||Reads the PhysicalVolume parameter from standard input. Use the -i flag only when PhysicalVolume is entered through standard input.|
|-L||Sets the logical volume label. The default label is None. The maximum size of the label file is 127 characters.|
|-m MapFile|| Specifies the exact physical partitions to allocate. Partitions are used in the order given in the MapFile parameter. Used partitions in the MapFile parameter are not legal, since the new logical volume cannot occupy the same physical space as a previously allocated logical volume. All physical partitions belonging to a copy are allocated before allocating for the next copy of the logical volume. The MapFile parameter format is: PVname:PPnum1[-PPnum2].
In this example, PVname
is a physical volume name (for example, hdisk0
) as specified by the system. It is one record per physical partition or a range of consecutive physical partitions. PPnum
is the physical partition number.
|-r Relocate|| Sets the reorganization relocation flag. For striped logical volumes, the Relocate parameter must be set to n (the default for striped logical volumes). The Relocate parameter can be one of the following:
|-s Strict|| Determines the strict allocation policy. Copies of a logical partition can be allocated to share or not to share the same physical volume. The Strict parameter is represented by one of the following:
|-S StripeSize||Specifies the number of bytes per striped. Must be a power of two, between 4K and 128K , for example 4K, 8K, 16K, 32K, 64K, or 128K.|
|-t Type||Sets the logical volume type. The standard types are jfs (file systems), jfslog (journal file system logs), and paging (paging spaces), but a user can define other logical volume types with this flag. You cannot create a striped logical volume of type boot. The default is jfs. If a log is manually created for a filesystem, the user must run the logform command to clean out the new jfslog before the log can be used. For example, to format the logical volume logdev , enter:|
|-u UpperBound||Sets the maximum number of physical volumes for new allocation. The value must be between one and the total number of physical volumes. The default is the total number of physical volumes in the volume group. When used to create a striped logical volume, using the -S flag, the -u flag sets the number of physical volumes being striped across.|
|-v Verify|| Sets the write-verify state for the logical volume. Causes (y) all writes to the logical volume to either be verified with a follow-up read, or prevents (n) the verification of all writes to the logical volume. The Verify parameter is represented by one of the following:
|-w MirrorWriteConsistency|| |
|-x Maximum||Sets the maximum number of logical partitions that can be allocated to the logical volume. The default value is 512. The number represented by the Number parameter must be equal to or less than the number represented by the Maximum variable. The maximum number of logical partitions per logical volume is 32,512.|
|-y NewLogicalVolume||Specifies the logical volume name to use instead of using a system- generated name. Logical volume names must be unique systemwide name, and can range from 1 to 15 characters. If the volume group is varied on in concurrent mode, the new name should be unique across all the concurrent nodes the volume group is varied on. The name cannot begin with a prefix already defined in the PdDv class in the Device Configuration Database for other devices.|
|-Y Prefix||Specifies the Prefix to use instead of the prefix in a system-generated name for the new logical volume. The prefix must be less than or equal to 13 characters. The name cannot begin with a prefix already defined in the PdDv class in the Device Configuration Database for other devices, nor be a name already used by another device.|
mklv -c 2 vg02 1
mklv -c 3 -u 2 -s n vg03 9
mklv -a c -t paging -b n vg04 5
mklv vg03 15 hdisk5 hdisk6 hdisk9
mklv -u 3 -S 64K vg05 12
mklv -S 8K vg05 12 hdisk1 hdisk2 hdisk3
|/usr/sbin||Directory where the mklv command resides.|
|/tmp||Directory where the temporary files are stored while the command is running.|
|/dev||Directory where the character and block device entries for the logical volume are created.|
The chfs command, chlv command, chpv command, extendlv command, mklvcopy command, rmlvcopy command, syncvg command.
The Logical Volume Storage Overview in AIX Version 4.3 System Management Guide: Operating System and Devices.
Setting up and running Web-based System Management in AIX Version 4.3 System Management Guide: Operating System and Devices.
The System Management Interface Tool (SMIT) Overview in AIX Version 4.3 System Management Guide: Operating System and Devices.
AIX HACMP/6000 Concepts and Facilities.