cli_mklv command
Purpose
Create a new logical volume on all nodes in a cluster.Syntax
cli_mklv [ -a Position ] [ -b BadBlocks ] [ -c Copies ] [ -d Schedule ]
[ -e Range ] [ -i ] [ -L Label ] [ -o y / n ] [ -r Relocate ]
[ -s Strict ] [ -t Type ] [ -u UpperBound ] [ -v Verify ]
[ -w MirrorWriteConsistency ] [ -x Maximum ] [ -y NewLogicalVolume |
-Y Prefix ] [ -S StripSize ] [ -U Userid ] [ -G Groupid ] [ -P Modes ]
VolumeGroup NumberOfLPs [ PhysicalVolume ... ]
Description
Uses C-SPOC to run the mklv command with parameters, and make the new logical volume definition available on all cluster nodes.
Flags
- -a Position
- Sets the physical volume allocation policy (the position of the logical partitions on the
physical volume). The following Position variables are valid:
- m
- Allocates logical partitions in the outer middle section of each physical volume. This variable is the default setting.
- c
- Allocates logical partitions in the center section of each physical volume.
- e
- Allocates logical partitions in the outer edge section of each physical volume.
- ie
- Allocates logical partitions in the inner edge section of each physical volume.
- im
- Allocates logical partitions in the inner middle section of each physical volume.
- -b BadBlocks
- Sets the bad-block relocation policy. The following BadBlocks variables are
valid:
- y
- Causes bad-block relocation to occur.
- n
- Prevents bad block relocation from occurring.
- -c Copies
- Specifies the minimum number of copies that each logical volume must have after you run the mirrorvg command. It might be possible, through the independent use of the mklvcopy command, that some logical volumes might have more than the minimum number specified after you run the mirrorvg command. The minimum value that you can specify is 2 and the maximum value you can specify is 3. A value of 1 is ignored.
- -d Schedule
- Sets the scheduling policy when more than one logical partition is written. You must use
parallel or sequential processing to mirror a striped logical volume. The following
Schedule variables are valid:
- p
- Establishes a parallel scheduling policy.
- ps
- Parallel write with sequential read policy. All mirrors are written in parallel but always read from the first mirror if it is available.
- pr
- Parallel write and reads are done for all mirrors. This policy is similar to the parallel policy, except an attempt is made to spread the reads to the logical volume more evenly across all mirrors.
- s
- Establishes a sequential scheduling policy. Use this variable when you specify policy of parallel or sequential strictness (super strictness).
- -e Range
- Sets the physical volume allocation policy. The allocation policy is the number of physical
volumes to extend across by using the volumes that provide the best allocation. The value of the
Range variable is limited by the Upperbound variable that is
set with the
-u
flag. The following Range variables are valid:- x
- Allocates logical partitions across the maximum number of physical volumes.
- m
- Allocates logical partitions across the minimum number of physical volumes.
- -G Groupid
- Specifies group ID for the logical volume special file.
- -L Label
- Sets the logical volume label. The maximum size for this variable is 127 characters.
- -n NewLogicalVolume
- Changes the name of the logical volume that is specified by the NewLogicalVolume variable. Logical volume names must be unique system wide and can have a maximum of 15 characters.
- -p Permission
- Sets the access permission to read/write or read-only. The following
Permission variables are valid:
- w
- Sets the access permission to read/write.
- r
- Sets the access permission to read-only. Mounting a JFS file system on a read-only logical volume is not supported.
- -P Modes
- Specifies permissions (file modes) for the logical volume special file.
- -r Relocate
- Specifies whether you want to allow or prevent the relocation of the logical volume during
reorganization. The following Relocate variables are valid:
- y
- Allows the logical volume to be relocated during reorganization. If the logical volume is
striped, you cannot use the chlv command to change the relocation flag to
y
. - n
- Prevents the logical volume from being relocated during reorganization.
- -s Strict
- Determines the strict allocation policy. You can allocate copies of a logical partition to be
shared or not shared for the same physical volume. The following Strict variables
are valid:
- y
- Sets a strict allocation policy, so copies of a logical partition cannot share the same physical volume.
- n
- Does not set a strict allocation policy, so copies of a logical partition can share the same physical volume.
- s
- Sets a super strict allocation policy, so that the partitions allocated for one mirror cannot
share a physical volume with the partitions from another mirror. When you change to a non-super
strict logical volume to a super strict logical volume, you must use the
-u
flag.
- -S StripSize
- Specifies the number of bytes per strip (the strip size that is multiplied by the number of
disks in an array equals the stripe size). Valid values include 4K, 8K, 16K, 32K, 64K, 128K, 256K,
512K, 1M, 2M, 4M, 8M, 16M, 32M, 64M, and 128M. You cannot use the
-d
,-e
, and-s
flags when you are creating a striped logical volume with this flag. - -t Type
- Sets the logical volume type. The following are the standard types:
- jfs (journaled file systems)
- jfslog (journaled file system logs)
- jfs2 (enhanced journaled file system)
- jfs2log (enhanced journaled file system logs)
- paging (paging spaces)
- -U Userid
- Specifies user ID for the logical volume special file.
- -u Upperbound
- Sets the maximum number of physical volumes for the new allocation. The value of the Upperbound variable is between one and the total number of physical volumes. When you use super strictness, the upper bound indicates the maximum number of physical volumes that are allowed for each mirror copy. When you use striped logical volumes, the upper bound must be multiple of Stripe_width variable.
- -v Verify
- Sets the write-verify state for the logical volume. Causes all writes to the logical volume
either to be verified with a follow-up read or not to be verified with a follow-up read. The
following Verify variables are valid:
- y
- All writes to the logical volume are verified with a follow-up read.
- n
- All writes to the logical volume are not verified with a follow-up read.
- -w MirrorWriteConsistency
- The following MirrorWriteConsistency variables are valid:
- y
- Turns on active mirror write consistency. This variable verifies data consistency on the mirrored copies of a logical volume during normal I/O processing.
- p
- Turns on passive mirror write consistency. This variable verifies data consistency on the mirrored copies during volume group synchronization after a system interruption. This function is only available on Big Volume Groups.
- n
- No mirror write consistency.
- -x Maximum
- Sets the maximum number of logical partitions that can be allocated to the logical volume. 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 system-wide name, and can range from 1-15 characters. The new name must be unique across all nodes on which the volume group is defined. The name cannot begin with a prefix already defined in the predefined device database (PdDv) class in the device configuration database for other devices.
- -Y Prefix
- Specifies the prefix value to use instead of the prefix in a system-generated name for the new logical volume. The prefix value must be less than or equal to 13 characters. The name cannot begin with a prefix already defined in the predefined device database (PdDv) class in the device configuration database for other devices, and it cannot be a name that is already used by another device.
Example
To make a logical volume in volume group that is named vg02 with one logical partition and a total of two copies of the data, enter:cli_mklv -c 2 vg01 1