lvm_import_vdo - Man Page

• Import a VDO volume with automatic names for the VG/LV: lvm_import_vdo /dev/mapper/vdo_volume
• Import and set the destination VG/LV name: lvm_import_vdo [-n|--name] vg_name/lv_name /dev/mapper/vdo_volume
• Simulate the import, showing what would be done without changing anything: lvm_import_vdo --dry-run /dev/mapper/vdo_volume
• Convert in place without using a temporary snapshot (less safe): lvm_import_vdo --no-snapshot /dev/mapper/vdo_volume
• Convert a VDO volume with verbose output and automatically answer "yes" to prompts: lvm_import_vdo [-v|--verbose] [-y|--yes] /dev/mapper/vdo_volume
• Use a VDO manager configuration file during import: lvm_import_vdo --vdo-config path/to/vdo.conf /dev/mapper/vdo_volume

tldr.sh

lvm_import_vdo [options] device

The lvm_import_vdo utility imports VDO volumes created and managed by the vdo(8) manager into a VDO LV managed by lvm2(8). This is done by moving the VDO superblock by 2 MiB and creating LVM2 metadata at the front of the device. The operation is not reversible; therefore, after conversion to LVM2, access to VDO data is only possible with lvm2(8) commands, and the vdo(8) manager no longer controls such a volume.

-f|--force

Bypass some sanity checks.

-h|--help

Display the help text.

-n|--name

Specifies the name of the converted VDO LV. When the name is not specified, a name is selected automatically. If the converted VDO volume is already using an LV as a backend device, the name of that LV is used for the VDO LV. In this case, the name of the volume group must also stay the same. The automatic name may change between releases and currently selects "vdolv" as the LV name, and the VG name is selected from the sequence "vdovg", "vdovg1", ​...

-v|--verbose

Be more verbose.

-y|--yes

Answer "yes" at any prompts.

--dry-run

Print a shell-escaped preview of commands without running storage-changing commands.

--no-snapshot

With this option, the conversion tool will not use a snapshot (COW storage) for conversion in your $TMPDIR filesystem and will directly manipulate the VDO device in-place. Warning: using a snapshot makes the whole conversion transactional and the snapshot can simply be merged once the conversion has completed successfully. If an error occurs, the snapshot is just removed. Without a snapshot, there is a higher risk of problems with recoverability in case some unexpected error occurs.

--vdo-config

Specifies the configuration file for the vdo manager.

On successful completion, the status code is 0. A status code of 1 is used for failure.

Convert VDO volume created by vdo manager into logical volume LV1 within volume group VG1.

# lvm_import_vdo --name VG1/LV1 /dev/mapper/vdo-volume

TMPDIR

The temporary directory name for mount points. Defaults to "/tmp".

DM_DEV_DIR

The device directory name. Defaults to "/dev" and must be an absolute path.

DM_UUID_PREFIX

Specify a UUID prefix for the snapshot volume used during VDO conversion.

LVM_BINARY

Overrides the command used to run lvm. Defaults to "lvm".

VDO_BINARY

Overrides the command used to run vdo. Defaults to "vdo".

lvm(8), lvm.conf(5),

vdo(8)