New in version 2.4.
parameter | required | default | choices | comments |
---|---|---|---|---|
copies |
no | 1 |
The number of copies of the logical volume. Maximum copies are 3.
|
|
lv |
yes |
The name of the logical volume.
|
||
lv_type |
no | jfs2 |
The type of the logical volume.
|
|
opts |
no |
Free-form options to be passed to the mklv command.
|
||
policy |
no | maximum |
|
Sets the interphysical volume allocation policy.
maximum allocates logical partitions across the maximum number of physical volumes. minimum allocates logical partitions across the minimum number of physical volumes. |
pvs |
no |
Comma separated list of physical volumes e.g.
hdisk1,hdisk2 . |
||
size |
no |
The size of the logical volume with one of the [MGT] units.
|
||
state |
no | present |
|
Control if the logical volume exists. If
present and the volume does not already exist then the size option is required. |
vg |
yes |
The volume group this logical volume is part of.
|
- name: Create a logical volume of 512M aix_lvol: vg: testvg lv: testlv size: 512M - name: Create a logical volume of 512M with disks hdisk1 and hdisk2 aix_lvol: vg: testvg lv: test2lv size: 512M pvs: hdisk1,hdisk2 - name: Create a logical volume of 512M mirrored aix_lvol: vg: testvg lv: test3lv size: 512M copies: 2 - name: Create a logical volume of 1G with a minimum placement policy aix_lvol: vg: rootvg lv: test4lv size: 1G policy: minimum - name: Create a logical volume with special options like mirror pool aix_lvol: vg: testvg lv: testlv size: 512M opts: -p copy1=poolA -p copy2=poolB - name: Extend the logical volume to 1200M aix_lvol: vg: testvg lv: test4lv size: 1200M - name: Remove the logical volume aix_lvol: vg: testvg lv: testlv state: absent
Common return values are documented here Return Values, the following are the fields unique to this module:
name | description | returned | type | sample |
---|---|---|---|---|
msg |
A friendly message describing the task result.
|
always | string | Logical volume testlv created. |
This module is flagged as preview which means that it is not guaranteed to have a backwards compatible interface.
For help in developing on modules, should you be so inclined, please read Community Information & Contributing, Testing Ansible and Developing Modules.