shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-21 13:34:40 +03:00
Code Releases Activity

man lvm: define LVM and its terms

Browse Source 
The lvm(8) man page never said what LVM is,
it never defined what the acronym LVM stands for,
it never spelled out other common acronyms VG, PV, LV,
and never described what they are.

This adds a very minimal definition which at least defines
the acronyms and entities, but it could obviously be
expanded on, either here or elsewhere.
This commit is contained in:
David Teigland 2017-05-02 15:47:02 -05:00
parent 882a918bef
commit 253bc5eb2e
2 changed files with 20 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
man/lvm.8_main
View File

@ -11,8 +11,20 @@ lvm \(em LVM2 tools
.
.SH DESCRIPTION
.
lvm provides the command-line tools for LVM2. A separate
manual page describes each command in detail.
The Logical Volume Manager (LVM) provides tools to create virtual block
devices from physical devices. Virtual devices may be easier to manage
than physical devices, and can have capabilities beyond what the physical
devices provide themselves. A Volume Group (VG) is a collection of one or
more physical devices, each called a Physical Volume (PV). A Logical
Volume (LV) is a virtual block device that can be used by the system or
applications. Each block of data in an LV is stored on one or more PV in
the VG, according to algorithms implemented by Device Mapper (DM) in the
kernel.
.P
The lvm command, and other commands listed below, are the command-line
tools for LVM. A separate manual page describes each command in detail.
.P
If \fBlvm\fP is invoked with no arguments it presents a readline prompt
(assuming it was compiled with readline support).

11
man/lvmsystemid.7_main
View File

@ -5,11 +5,12 @@ lvmsystemid \(em LVM system ID
.SH DESCRIPTION
The LVM system ID restricts VG access to one host. This is useful when a
VG is placed on shared storage devices, or when local devices are visible
to both host and guest operating systems. In cases like these, a VG can
be visible to multiple hosts at once, and some mechanism is needed to
protect it from being used by more than one host at a time.
The \fBlvm\fP(8) system ID restricts VG access to one host. This is
useful when a VG is placed on shared storage devices, or when local
devices are visible to both host and guest operating systems. In cases
like these, a VG can be visible to multiple hosts at once, and some
mechanism is needed to protect it from being used by more than one host at
a time.
A VG's system ID identifies one host as the VG owner. The host with a
matching system ID can use the VG and its LVs, while LVM on other hosts