source: postlfs/filesystems/lvm2.xml@ f9431b6

10.0 10.1 11.0 11.1 11.2 11.3 12.0 12.1 7.10 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind kea ken/TL2024 ken/inkscape-core-mods ken/tuningfonts lazarus lxqt nosym perl-modules plabs/newcss plabs/python-mods python3.11 qt5new rahul/power-profiles-daemon renodr/vulkan-addition trunk upgradedb xry111/intltool xry111/llvm18 xry111/soup3 xry111/test-20220226 xry111/xf86-video-removal
Last change on this file since f9431b6 was f9431b6, checked in by Pierre Labastie <pieere@…>, 9 years ago

Add further explanations for LVM2 tests. Thanks to Fernando for interesting
discussions

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@16573 af4574ff-66df-0310-9fd7-8a98e5e911e0
  • Property mode set to 100644
File size: 13.7 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6
7 <!ENTITY lvm2-download-http " ">
8 <!ENTITY lvm2-download-ftp "ftp://sources.redhat.com/pub/lvm2/releases/LVM2.&lvm2-version;.tgz">
9 <!ENTITY lvm2-md5sum "80af5af726949bbbb2aceb15b24b7d20">
10 <!ENTITY lvm2-size "1.8 MB">
11 <!ENTITY lvm2-buildsize "31 MB (during tests, transcient files can grow up to around 500 MB)">
12 <!ENTITY lvm2-time "0.3 SBU (around 10 SBU with tests, see below)">
13]>
14
15<sect1 id="lvm2" xreflabel="LVM2-&lvm2-version;">
16 <?dbhtml filename="lvm2.html"?>
17
18 <sect1info>
19 <othername>$LastChangedBy$</othername>
20 <date>$Date$</date>
21 </sect1info>
22
23 <title>LVM2-&lvm2-version;</title>
24
25 <indexterm zone="lvm2">
26 <primary sortas="a-LVM2">LVM2</primary>
27 </indexterm>
28
29 <sect2 role="package">
30 <title>Introduction to LVM2</title>
31
32 <para>
33 The <application>LVM2</application> package is a set of tools that manage
34 logical partitions. It allows spanning of file systems across multiple
35 physical disks and disk partitions and provides for dynamic growing or
36 shrinking of logical partitions, mirroring and low storage footprint
37 snapshots.
38 </para>
39
40 &lfs78_checked;
41
42 <bridgehead renderas="sect3">Package Information</bridgehead>
43 <itemizedlist spacing="compact">
44 <listitem>
45 <para>
46 Download (HTTP): <ulink url="&lvm2-download-http;"/>
47 </para>
48 </listitem>
49 <listitem>
50 <para>
51 Download (FTP): <ulink url="&lvm2-download-ftp;"/>
52 </para>
53 </listitem>
54 <listitem>
55 <para>
56 Download MD5 sum: &lvm2-md5sum;
57 </para>
58 </listitem>
59 <listitem>
60 <para>
61 Download size: &lvm2-size;
62 </para>
63 </listitem>
64 <listitem>
65 <para>
66 Estimated disk space required: &lvm2-buildsize;
67 </para>
68 </listitem>
69 <listitem>
70 <para>
71 Estimated build time: &lvm2-time;
72 </para>
73 </listitem>
74 </itemizedlist>
75
76 <bridgehead renderas="sect3">LVM2 Dependencies</bridgehead>
77
78 <bridgehead renderas="sect4">Optional</bridgehead>
79 <para role="optional">
80 <xref linkend='mdadm'/>,
81 <xref linkend='reiserfs'/>,
82 <xref linkend='valgrind'/>,
83 <xref linkend='which'/>,
84 <xref linkend='xfsprogs'/> (all five may be used, but are not required,
85 for tests), and
86 <ulink url='https://github.com/jthornber/thin-provisioning-tools'>
87 thin-provisioning-tools</ulink>
88 </para>
89
90 <para condition="html" role="usernotes">User Notes:
91 <ulink url="&blfs-wiki;/lvm2"/>
92 </para>
93
94 <note>
95 <para>
96 Kernel versions in the 4.1 and 4.2 series have a broken RAID
97 implementation. If you want to use RAID type LV's, you should
98 install a kernel with version above 4.2.4. Note that several
99 tests use RAID logical volumes, and can generate a <quote>kernel
100 oops</quote> with faulty kernel version, which ususally renders the
101 system unusable.
102 </para>
103 </note>
104 </sect2>
105
106 <sect2 role="kernel" id="lvm2-kernel">
107 <title>Kernel Configuration</title>
108
109 <para>
110 Enable the following options in the kernel configuration
111 and recompile the kernel:
112 </para>
113
114 <note><para>
115 There are several other Device Mapper options in the kernel beyond those
116 listed below. In order to get reasonable results if running the
117 regression tests, all must be enabled either internally or as a module.
118 </para></note>
119
120<screen><literal>Device Drivers ---&gt;
121 [*] Multiple devices driver support (RAID and LVM) ---&gt; [CONFIG_MD]
122 &lt;*/M&gt; Device mapper support [CONFIG_BLK_DEV_DM]
123 &lt;*/M/ &gt; Crypt target support [CONFIG_DM_CRYPT]
124 &lt;*/M/ &gt; Snapshot target [CONFIG_DM_SNAPSHOT]
125 &lt;*/M/ &gt; Thin provisioning target [CONFIG_DM_THIN_PROVISIONING]
126 &lt;*/M/ &gt; Mirror target [CONFIG_DM_MIRROR]</literal></screen>
127
128 <indexterm zone="lvm2 lvm2-kernel">
129 <primary sortas="d-lvm2">lvm2</primary>
130 </indexterm>
131
132 </sect2>
133
134 <sect2 role="installation">
135 <title>Installation of LVM2</title>
136
137 <para>
138 Install <application>LVM2</application> by running the following
139 commands:
140 </para>
141
142<screen><userinput>./configure --prefix=/usr \
143 --exec-prefix= \
144 --enable-applib \
145 --enable-cmdlib \
146 --enable-pkgconfig \
147 --enable-udev_sync &amp;&amp;
148make</userinput></screen>
149
150 <para>
151 The tests use <application>udev</application> for logical volume
152 synchronization, so that the LVM udev rules and some utilities need to
153 be installed before running the tests. If you are installing
154 <application>LVM2</application> for the first time, and do not
155 want to install the full package before running the tests, the minimal
156 set of utilities can be installed by running the following instructions
157 as the <systemitem class="username">root</systemitem> user:
158 </para>
159
160<screen role="root"><userinput>make -C tools install_dmsetup_dynamic &amp;&amp;
161make -C udev install &amp;&amp;
162make -C libdm install</userinput></screen>
163
164 <para>
165 To test the results, issue: <command>make check_local</command> as the
166 <systemitem class="username">root</systemitem> user. Other targets are
167 available and can be listed with <command>make -C test help</command>.
168 The test timings are very dependent on the speed of the disk(s), and on
169 the number of enabled kernel options.
170 </para>
171 <para>
172 Those tests do not implement the <quote>expected fail</quote> possibility,
173 and a small number of tests failures is expected by upstream. More
174 failures may happen because some kernel options are missing. For example,
175 the lack of the <emphasis>dm-delay</emphasis> device mapper target may
176 explain up to 10 failures or so. Some tests are incorrectly flagged
177 <quote>broken</quote> if
178 <ulink url='https://github.com/jthornber/thin-provisioning-tools'>
179 thin-provisioning-tools</ulink> are not installed. A workaround is to
180 add the following flags to <command>configure</command>:
181 </para>
182
183<screen role="nodump"><userinput> --with-thin-check= \
184 --with-thin-dump= \
185 --with-thin-repair= \
186 --with-thin-restore= \
187 --with-cache-check= \
188 --with-cache-dump= \
189 --with-cache-repair= \
190 --with-cache-restore= \</userinput></screen>
191
192 <para>
193 One test has been reported to hang, and can be disabled via <command>rm
194 test/shell/snapshot-remove-dmsetup.sh</command>. Other tests may hang
195 with kernel versions in the 4.1 and 4.2 series (see above). They can be
196 removed as well if necessary. The tests generate a lot
197 of kernel messages, which may clutter your terminal. You can disable them
198 by issuing <command>dmesg -D</command> before running the tests (do not
199 forget to issue <command>dmesg -E</command> when tests are done).
200 </para>
201
202 <para>
203 Now, as the <systemitem class="username">root</systemitem> user:
204 </para>
205
206<screen role="root"><userinput>make install</userinput></screen>
207
208 </sect2>
209
210 <sect2 role="commands">
211 <title>Command Explanations</title>
212
213 <para>
214 <parameter>--enable-applib</parameter>: This switch enables
215 building of the shared application library.
216 </para>
217
218 <para>
219 <parameter>--enable-cmdlib</parameter>: This switch enables
220 building of the shared command library. It is required
221 when building the event daemon.
222 </para>
223
224 <para>
225 <parameter>--enable-pkgconfig</parameter>: This switch enables
226 installation of <command>pkg-config</command> support files.
227 </para>
228
229 <para>
230 <parameter>--enable-udev_sync</parameter>: This switch enables
231 synchronisation with <application>Udev</application> processing.
232 </para>
233
234 <para>
235 <option>--enable-dmeventd</option>: This switch enables
236 building of the <application>Device Mapper</application>
237 event daemon.
238 </para>
239
240 <para>
241 <option>--enable-lvmetad</option>: This switch enables
242 building of the <application>LVM</application> metadata daemon,
243 which avoids scanning all the filesystems when an lvm command is
244 run.
245 </para>
246
247 </sect2>
248
249 <sect2 role="content">
250 <title>Contents</title>
251
252 <segmentedlist>
253 <segtitle>Installed Programs</segtitle>
254 <segtitle>Installed Libraries</segtitle>
255 <segtitle>Installed Directories</segtitle>
256
257 <seglistitem>
258 <seg>
259 blkdeactivate, dmeventd (optional), dmsetup, fsadm, lvm, lvmconf,
260 lvmdump, lvmetad (optional), and vgimportclone. There are also
261 numerous symbolic links to lvm that implement specific
262 functionalities
263 </seg>
264 <seg>
265 libdevmapper.so, liblvm2app.so and liblvm2cmd.so; optional:
266 libdevmapper-event.so, libdevmapper-event-lvm2.so,
267 libdevmapper-event-lvm2mirror.so, libdevmapper-event-lvm2snapshot.so,
268 libdevmapper-event-lvm2raid.so, and libdevmapper-event-lvm2thin.so
269 </seg>
270 <seg>
271 /etc/lvm and
272 /lib/device-mapper (optional)
273 </seg>
274 </seglistitem>
275 </segmentedlist>
276
277 <variablelist>
278 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
279 <?dbfo list-presentation="list"?>
280
281 <?dbhtml list-presentation="table"?>
282
283 <varlistentry id="blkdeactivate">
284 <term><command>blkdeactivate</command></term>
285 <listitem>
286 <para>
287 utility to deactivate block device.
288 </para>
289 <indexterm zone="lvm2 blkdeactivate">
290 <primary sortas="b-blkdeactivate">blkdeactivate</primary>
291 </indexterm>
292 </listitem>
293 </varlistentry>
294
295 <varlistentry id="dmeventd">
296 <term><command>dmeventd</command></term>
297 <listitem>
298 <para>
299 (optional) is the Device Mapper event daemon.
300 </para>
301 <indexterm zone="lvm2 dmeventd">
302 <primary sortas="b-dmeventd">dmeventd</primary>
303 </indexterm>
304 </listitem>
305 </varlistentry>
306
307 <varlistentry id="dmsetup">
308 <term><command>dmsetup</command></term>
309 <listitem>
310 <para>
311 is a low level logical volume management tool.
312 </para>
313 <indexterm zone="lvm2 dmsetup">
314 <primary sortas="b-dmsetup">dmsetup</primary>
315 </indexterm>
316 </listitem>
317 </varlistentry>
318
319 <varlistentry id="fsadm">
320 <term><command>fsadm</command></term>
321 <listitem>
322 <para>
323 is a utility used to resize or check filesystem on a device.
324 </para>
325 <indexterm zone="lvm2 fsadm">
326 <primary sortas="b-fsadm">fsadm</primary>
327 </indexterm>
328 </listitem>
329 </varlistentry>
330
331 <varlistentry id="lvm">
332 <term><command>lvm</command></term>
333 <listitem>
334 <para>
335 provides the command-line tools for <application>LVM2</application>.
336 Commands are implemented via sympolic links to this program to
337 manage physical devices (pv*), volume groups (vg*) and logical
338 volumes (lv*).
339 </para>
340 <indexterm zone="lvm2 lvm">
341 <primary sortas="b-lvm">lvm</primary>
342 </indexterm>
343 </listitem>
344 </varlistentry>
345
346 <varlistentry id="lvmconf">
347 <term><command>lvmconf</command></term>
348 <listitem>
349 <para>
350 is a script that modifies the locking configuration in
351 the <application>LVM2</application> configuration file.
352 </para>
353 <indexterm zone="lvm2 lvmconf">
354 <primary sortas="b-lvmconf">lvmconf</primary>
355 </indexterm>
356 </listitem>
357 </varlistentry>
358
359 <varlistentry id="lvmdump">
360 <term><command>lvmdump</command></term>
361 <listitem>
362 <para>
363 is a tool used to dump various information concerning
364 <application>LVM2</application>.
365 </para>
366 <indexterm zone="lvm2 lvmdump">
367 <primary sortas="b-lvmdump">lvmdump</primary>
368 </indexterm>
369 </listitem>
370 </varlistentry>
371
372 <varlistentry id="lvmetad">
373 <term><command>lvmetad</command></term>
374 <listitem>
375 <para>
376 (optional) is the LVM metadata daemon.
377 </para>
378 <indexterm zone="lvm2 lvmetad">
379 <primary sortas="b-lvmetad">lvmetad</primary>
380 </indexterm>
381 </listitem>
382 </varlistentry>
383
384 <varlistentry id="vgimportclone">
385 <term><command>vgimportclone</command></term>
386 <listitem>
387 <para>
388 is used to import a duplicated VG (e.g. hardware snapshot).
389 </para>
390 <indexterm zone="lvm2 vgimportclone">
391 <primary sortas="b-vgimportclone">vgimportclone</primary>
392 </indexterm>
393 </listitem>
394 </varlistentry>
395
396 <varlistentry id="libdevmapper">
397 <term><filename class='libraryfile'>libdevmapper.so</filename></term>
398 <listitem>
399 <para>
400 contains the <application>Device Mapper</application> API
401 functions.
402 </para>
403 <indexterm zone="lvm2 libdevmapper">
404 <primary sortas="c-libdevmapper">libdevmapper.so</primary>
405 </indexterm>
406 </listitem>
407 </varlistentry>
408
409 </variablelist>
410
411 </sect2>
412
413</sect1>
Note: See TracBrowser for help on using the repository browser.