Changeset 54789f3 for postlfs/filesystems/lvm2.xml
- Timestamp:
- 01/24/2016 02:04:18 AM (8 years ago)
- Branches:
- systemd-13485
- Children:
- 83f6c770
- Parents:
- 295ca00
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
postlfs/filesystems/lvm2.xml
r295ca00 r54789f3 6 6 7 7 <!ENTITY lvm2-download-http " "> 8 <!ENTITY lvm2-download-ftp "ftp://sources.redhat.com/pub/lvm2/ LVM2.&lvm2-version;.tgz">9 <!ENTITY lvm2-md5sum " b3f4c273a30b316678755cec2a129718">8 <!ENTITY lvm2-download-ftp "ftp://sources.redhat.com/pub/lvm2/releases/LVM2.&lvm2-version;.tgz"> 9 <!ENTITY lvm2-md5sum "f2191c4798c8927a6d31a96010b9f568"> 10 10 <!ENTITY lvm2-size "1.8 MB"> 11 <!ENTITY lvm2-buildsize " 31 MB (additional 10 MB to run the test suite)">12 <!ENTITY lvm2-time "0. 6 SBU (additional 8.2 SBU to run the test suite)">11 <!ENTITY lvm2-buildsize "46 MB (during the test suite, transient files can grow up to around 500 MB)"> 12 <!ENTITY lvm2-time "0.4 SBU (additional about 10 SBU to run the test suite with parallelism = 4)"> 13 13 ]> 14 14 … … 31 31 32 32 <para> 33 The <application>LVM2</application> package is a packagethat manages33 The <application>LVM2</application> package is a set of utilities that manages 34 34 logical partitions. It allows spanning of file systems across multiple 35 35 physical disks and disk partitions and provides for dynamic growing or 36 shrinking of logical partitions .36 shrinking of logical partitions, mirroring and low storage footprint snapshots. 37 37 </para> 38 38 … … 77 77 <bridgehead renderas="sect4">Optional</bridgehead> 78 78 <para role="optional"> 79 <xref linkend='mdadm'/> (for checks) and 80 <xref linkend='xfsprogs'/> (for checks) 79 <xref linkend='mdadm'/> (for checks), 80 <xref linkend='reiserfs'/>, 81 <xref linkend='valgrind'/>, 82 <xref linkend='which'/>, 83 <xref linkend='xfsprogs'/> (all five may be used, but are not required, 84 for tests), and 85 <ulink url='https://github.com/jthornber/thin-provisioning-tools'> 86 thin-provisioning-tools</ulink> 81 87 </para> 82 88 … … 84 90 <ulink url="&blfs-wiki;/lvm2"/> 85 91 </para> 92 93 <note> 94 <para> 95 Kernel versions in the 4.1 and 4.2 series have a broken RAID 96 implementation. If you want to use RAID style LV's, you should 97 install a kernel with a version number above 4.2.4. Note that several 98 tests use RAID logical volumes, and can generate a <quote>kernel 99 oops</quote> with faulty kernel versions, which usually renders the 100 system unusable. 101 </para> 102 </note> 86 103 </sect2> 87 104 … … 105 122 <*/M/ > Crypt target support [CONFIG_DM_CRYPT] 106 123 <*/M/ > Snapshot target [CONFIG_DM_SNAPSHOT] 124 <*/M/ > Thin provisioning target [CONFIG_DM_THIN_PROVISIONING] 107 125 <*/M/ > Mirror target [CONFIG_DM_MIRROR]</literal></screen> 108 126 … … 121 139 </para> 122 140 123 <screen><userinput>./configure --prefix=/usr \ 141 <screen><userinput>SAVEPATH=$PATH && 142 PATH=$PATH:/sbin:/usr/sbin && 143 ./configure --prefix=/usr \ 124 144 --exec-prefix= \ 125 145 --with-confdir=/etc \ … … 128 148 --enable-pkgconfig \ 129 149 --enable-udev_sync && 130 make</userinput></screen> 131 132 <para> 133 <!--The check command must be run as the <systemitem 134 class="username">root</systemitem> user. Also the tests are known to 135 hang if at least one partition on a hard drive is not set up as a Linux 136 LVM partition (type 8e00).-->To test the results, issue: <command>make -k 137 check</command> as the <systemitem class="username">root</systemitem> 138 user. At least one partition on a hard drive must be set up as a Linux 139 LVM partition (type 8e00). The test timings are very dependent on the 140 speed of the disk(s) and on the number of enabled kernel options. 150 make && 151 PATH=$SAVEPATH && 152 unset SAVEPATH</userinput></screen> 153 154 <para> 155 The tests use <application>udev</application> for logical volume 156 synchronization, so the LVM udev rules and some utilities need to 157 be installed before running the tests. If you are installing 158 <application>LVM2</application> for the first time, and do not 159 want to install the full package before running the tests, the minimal 160 set of utilities can be installed by running the following commands 161 as the <systemitem class="username">root</systemitem> user: 162 </para> 163 164 <screen role="root"><userinput>make -C tools install_dmsetup_dynamic && 165 make -C udev install && 166 make -C libdm install</userinput></screen> 167 168 <para> 169 To test the results, issue: <command>make check_local</command> as the 170 <systemitem class="username">root</systemitem> user. Other targets are 171 available and can be listed with <command>make -C test help</command>. 172 The test timings are very dependent on the speed of the disk(s), and on 173 the number of enabled kernel options. 174 </para> 175 <para> 176 Those tests do not implement the <quote>expected fail</quote> possibility, 177 and a small number of test failures is expected by upstream. More 178 failures may happen because some kernel options are missing. For example, 179 the lack of the <emphasis>dm-delay</emphasis> device mapper target may 180 explain up to 10 failures or so. Some tests are flagged 181 <quote>warned</quote> if 182 <ulink url='https://github.com/jthornber/thin-provisioning-tools'> 183 thin-provisioning-tools</ulink> are not installed. A workaround is to 184 add the following flags to <command>configure</command>: 185 </para> 186 187 <screen role="nodump"><userinput> --with-thin-check= \ 188 --with-thin-dump= \ 189 --with-thin-repair= \ 190 --with-thin-restore= \ 191 --with-cache-check= \ 192 --with-cache-dump= \ 193 --with-cache-repair= \ 194 --with-cache-restore= \</userinput></screen> 195 196 <para> 197 Some tests may hang with kernel versions within the 4.1 and 4.2 series (see 198 above). They can be removed if necessary, for example: <command>rm 199 test/shell/lvcreate-large-raid.sh</command>. The tests generate a lot 200 of kernel messages, which may clutter your terminal. You can disable them 201 by issuing <command>dmesg -D</command> before running the tests (do not 202 forget to issue <command>dmesg -E</command> when the tests are done). 141 203 </para> 142 204 … … 151 213 <sect2 role="commands"> 152 214 <title>Command Explanations</title> 215 216 <para> 217 <command>PATH=$PATH:/sbin:/usr/sbin</command>: The path 218 must contain <filename class="directory">/sbin</filename> and 219 <filename class="directory">/usr/sbin</filename> for proper system tool 220 detection by the <command>configure</command> script. This command 221 ensures that it is properly set if you are building as an unprivileged user. 222 </para> 153 223 154 224 <para> … … 161 231 building of the shared command library. It is required 162 232 when building the event daemon. 233 </para> 234 235 <para> 236 <option>--enable-lvmetad</option>: This switch enables 237 building of the <application>LVM</application> metadata daemon, 238 which avoids scanning all the filesystems when an LVM command is 239 run. 163 240 </para> 164 241 … … 191 268 <seglistitem> 192 269 <seg> 193 blkdeactivate, dmeventd (optional), dmsetup, fsadm, lvm, lvmconf, 194 lvmdump, and vgimportclone. There are also numerous symbolic links to 270 blkdeactivate, 271 dmeventd (optional), 272 dmsetup, 273 fsadm, 274 lvm, 275 lvmconf, 276 lvmdump, 277 lvmetad (optional), 278 and vgimportclone. 279 There are also numerous symbolic links to 195 280 lvm that implement specific functionalities 196 281 </seg> 197 282 <seg> 198 libdevmapper.so, liblvm2app.so and liblvm2cmd.so; optional: 199 libdevmapper-event.so, libdevmapper-event-lvm2.so, 200 libdevmapper-event-lvm2mirror.so, libdevmapper-event-lvm2snapshot.so, 201 libdevmapper-event-lvm2raid.so, and libdevmapper-event-lvm2thin.so 283 libdevmapper.so, 284 liblvm2app.so, 285 and liblvm2cmd.so; 286 optional: libdevmapper-event.so, 287 libdevmapper-event-lvm2.so, 288 libdevmapper-event-lvm2mirror.so, 289 libdevmapper-event-lvm2snapshot.so, 290 libdevmapper-event-lvm2raid.so, 291 and libdevmapper-event-lvm2thin.so 202 292 </seg> 203 293 <seg> … … 303 393 </varlistentry> 304 394 395 <varlistentry id="lvmetad"> 396 <term><command>lvmetad</command></term> 397 <listitem> 398 <para> 399 (optional) is the LVM metadata daemon. 400 </para> 401 <indexterm zone="lvm2 lvmetad"> 402 <primary sortas="b-lvmetad">lvmetad</primary> 403 </indexterm> 404 </listitem> 405 </varlistentry> 406 305 407 <varlistentry id="vgimportclone"> 306 408 <term><command>vgimportclone</command></term>
Note:
See TracChangeset
for help on using the changeset viewer.