blob: 20be6847d5802ff6259f5189816d0a3e24451469 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
|
.TH "FSADM" "8" "LVM TOOLS #VERSION#" "Red Hat, Inc" "\""
.
.SH "NAME"
.
lvm_import_vdo \(em utility to import VDO volumes into a new volume group.
.
.SH SYNOPSIS
.
.PD 0
.ad l
.TP 10
.B lvm_import_vdo
.RI [ options ]
.IR device
.
.PD
.
.SH DESCRIPTION
.
lvm_import_vdo utility imports VDO volumes created and managed by
.BR vdo (8)
manager into
.BR lvm2 (8)
managed VDO LV. This is realized by moving VDO superblock by 2MiB
and creating lvm2 metadata at the front of this device. The operation is not reversible,
thus after conversion to lvm2 the access to VDO data is only possible with
.BR lvm2 (8)
commands,
.BR vdo (8)
manager no longer control such volume.
.
.SH OPTIONS
.
.TP
.BR -f | --force
Bypass some sanity checks.
.
.TP
.BR -h | --help
Display the help text.
.
.TP
.BR -n | --name
Specifies the name of converted VDO LV. When the name is not specified,
some automatic name is selected. In case the converted VDO volume is
already using LV a backend device, the name of this LV is used for VDO LV.
In this case also the of volume group must stay same.
Automatic name may change between releases and currently selects
"vdolv" as LV name and VG name is selected from sequence
"vdovg", "vdovg1", ...
.
.TP
.BR -v | --verbose
Be more verbose.
.
.TP
.BR -y | --yes
Answer "yes" at any prompts.
.
.TP
.BR --dry-run
Print verbosely commands without running them.
.
.TP
.BR --no-snapshot
With this option conversion tool will not use snapshot (COW storage) for conversion
in your $TMPDIR filesystem and it will directly manipulate with VDO device in-place.
Warning: the snapshot usage makes the whole conversion transactional and
the snapshot can be just simply merged once the whole conversion
has successfully proceeded. In the case of error the snapshot is just removed.
Without the use of snapshot there is higher risk of problems with recoverability in
case some unexpected error occurs.
.
.TP
.BR --vdo-config
Configuration file for VDO manager. Can be used to specify configuration for vdo manager.
.
.
.SH DIAGNOSTICS
.
On successful completion, the status code is 0.
A status code of 1 is used for failure.
.
.SH EXAMPLES
.
Convert VDO volume created by vdo manager into logical volume LV1 with within volume group VG1.
.P
#
.B lvm_import_vdo --name VG1/LV1 /dev/mapper/vdo-volume
.
.SH ENVIRONMENT VARIABLES
.
.TP
.B TMPDIR
The temporary directory name for mount points. Defaults to "\fI/tmp\fP".
.TP
.B DM_DEV_DIR
The device directory name.
Defaults to "\fI/dev\fP" and must be an absolute path.
.TP
.B DM_UUID_PREFIX
Specify uuid prefix for snapshot volume used during vdo conversion.
.TP
.B LVM_BINARY
Allow to overide command called from lvm. Defaults to "\fIlvm\fP".
.TP
.B VDO_BINARY
Allow to overide command called from vdo. Defaults to "\fIvdo\fP".
.
.SH SEE ALSO
.
.nh
.ad l
.BR lvm (8),
.BR lvm.conf (5),
.P
.BR vdo (8),
|
