cluster mirrors). Cluster mirrors are not possible without this daemon
running.
.P
-This daemon relies on the cluster infrastructure provided by the corosync,
+This daemon relies on the cluster infrastructure provided by corosync,
which must be set up and running in order for cmirrord to function.
.P
Output is logged via \fBsyslog\fP(3). The \fBSIGUSR1 signal\fP(7) can be
.TP
\fB--count\fP \fIcount\fP
Specify the number of times to repeat a report.
-Set this to zero continue until interrupted.
+Set this to zero to continue until interrupted.
The default interval is one second.
.
.TP
.
.TP
.B --nolockfs
-Do not attempt to synchronize filesystem eg, when suspending a device.
+Do not attempt to synchronize filesystem, e.g., when suspending a device.
.
.TP
.B --noopencount
Otherwise a table is read from standard input unless \fB--notable\fP is used.
The optional \fIuuid\fP can be used in place of
device_name in subsequent dmsetup commands.
-If successful the device will appear in table and for live
+If successful the device will appear in table and for the live
device the node
.na
.I /dev/mapper/device_name
.NTP
.CMD_DEPS
Outputs a list of devices referenced by the live table for the specified
-device. Device names on output can be customised by following options:
+device. Device names on output can be customised by the following options:
\fBdevno\fP (major and minor pair, used by default),
\fBblkdevname\fP (block device name),
\fBdevname\fP (map name for device-mapper devices, equal to blkdevname otherwise).
List device names. Optionally only list devices that have at least
one target of the specified type. Optionally execute a command for
each device. The device name is appended to the supplied command.
-Device names on output can be customised by following options:
+Device names on output can be customised by the following options:
\fBdevno\fP (major and minor pair, used by default),
\fBblkdevname\fP (block device name),
\fBdevname\fP (map name for device-mapper devices, equal to blkdevname otherwise).
\fB--tree\fP displays dependencies between devices as a tree.
-It accepts a comma-separate list of options.
+It accepts a comma-separated list of options.
Some specify the information displayed against each node:
.BR device\ /\: \ nodevice ;
.BR blkdevname ;
.
.TP
.B cache
-Improves performance of a block device (eg, a spindle) by dynamically
-migrating some of its data to a faster smaller device (eg, an SSD).
+Improves performance of a block device (e.g., a spindle) by dynamically
+migrating some of its data to a faster smaller device (e.g., an SSD).
.
.TP
.B crypt
.
.SH DESCRIPTION
.
-fsadm utility checks or resizes the filesystem on a device (can be
-also dm-crypt encrypted device).
+fsadm utility checks or resizes the filesystem on a device
+(which can also be a dm-crypt encrypted device).
It tries to use the same API for
.BR ext2 ,
.BR ext3 ,
.
.TP
.B vgexport
-Make volume Groups unknown to the system.
+Make Volume Groups unknown to the system.
.
.TP
.B vgextend
-.TH "FSADM" "8" "LVM TOOLS #VERSION#" "Red Hat, Inc" \" -*- nroff -*-
+.TH "LVM_IMPORT_VDO" "8" "LVM TOOLS #VERSION#" "Red Hat, Inc" \" -*- nroff -*-
.
.SH "NAME"
.
-lvm_import_vdo \(em utility to import VDO volumes into a new volume group.
+lvm_import_vdo \(em utility to import VDO volumes into a new volume group
.
.SH SYNOPSIS
.
.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.
+some automatic name is selected. In case the converted VDO volume is already
+using an LV as a backend device, the name of this LV is used for VDO LV.
+In this case also the name of the volume group must stay the same.
Automatic name may change between releases and currently selects
"vdolv" as LV name and VG name is selected from sequence
"vdovg", "vdovg1", ...
.SH EXAMPLES
.
Convert VDO volume created by vdo manager into logical volume LV1
-with within volume group VG1.
+within volume group VG1.
.P
#
.B lvm_import_vdo --name VG1/LV1 /dev/mapper/vdo-volume
.P
The system ID is a string that uniquely identifies a host. It can be
configured as a custom value, or it can be assigned automatically by LVM
-using some unique identifier already available on the host, e.g.
+using some unique identifier already available on the host, e.g.,
machine-id or uname.
.P
When a new VG is created, the system ID of the local host is recorded in
.P
A
.B foreign VG
-is a VG seen by a host with an unmatching system ID, i.e. the system ID
+is a VG seen by a host with an unmatching system ID, i.e., the system ID
in the VG metadata does not match the system ID configured on the host.
If the host has no system ID, and the VG does, the VG is foreign and LVM
will ignore it. If the VG has no system ID, access is unrestricted, and