Changeset 9a3e4ba for postlfs/filesystems
- Timestamp:
- 02/24/2016 07:31:59 AM (9 years ago)
- Branches:
- systemd-13485
- Children:
- 996dfc4a
- Parents:
- a91856d1
- Location:
- postlfs/filesystems
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
postlfs/filesystems/lvm2.xml
ra91856d1 r9a3e4ba 7 7 <!ENTITY lvm2-download-http " "> 8 8 <!ENTITY lvm2-download-ftp "ftp://sources.redhat.com/pub/lvm2/releases/LVM2.&lvm2-version;.tgz"> 9 <!ENTITY lvm2-md5sum " f2191c4798c8927a6d31a96010b9f568">9 <!ENTITY lvm2-md5sum "53dffb3ba964c0f0709f6e8922795bdd"> 10 10 <!ENTITY lvm2-size "1.8 MB"> 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)">11 <!ENTITY lvm2-buildsize "26 MB (during tests, transient files can grow up to around 500 MB)"> 12 <!ENTITY lvm2-time "0.4 SBU (additional 5.4 SBU for tests)"> 13 13 ]> 14 14 … … 91 91 </para> 92 92 93 < note>93 <caution> 94 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. 95 Kernel versions between 4.1 and 4.4.1 have a broken RAID 96 implementation. If you want to use RAID type LV's, you should install 97 kernel version 4.4.2 or above. Note that several tests use RAID logical 98 volumes, and can generate a <quote>kernel oops</quote> with the faulty 99 kernel version, which usually renders the system unusable. 101 100 </para> 102 </ note>101 </caution> 103 102 </sect2> 104 103 -
postlfs/filesystems/mdadm.xml
ra91856d1 r9a3e4ba 10 10 <!ENTITY mdadm-size "416 KB"> 11 11 <!ENTITY mdadm-buildsize "416 MB (12 MB with tests)"> 12 <!ENTITY mdadm-time "0.1 SBU ( 23 SBU, with tests)">12 <!ENTITY mdadm-time "0.1 SBU (tests take about an hour, only partially processor dependent)"> 13 13 <!-- tests statistcs repeated from previous one, given by Pierre--> 14 14 ]> … … 60 60 <para condition="html" role="usernotes">User Notes: 61 61 <ulink url="&blfs-wiki;/mdadm"/></para> 62 < note>62 <caution> 63 63 <para> 64 Kernel versions in series 4.1 and 4.2have a broken RAID65 implementation. Use a kernel with version a bove 4.2.4.64 Kernel versions in series 4.1 through 4.4.1 have a broken RAID 65 implementation. Use a kernel with version at or above 4.4.2. 66 66 </para> 67 </ note>67 </caution> 68 68 69 69 </sect2> … … 101 101 102 102 <para>If you wish to run the tests, ensure that your kernel supports 103 RAID and that a version of mdadm is not already running, and issue: 104 <command>make test</command> and then, as the 105 <systemitem class="username">root</systemitem> user: 106 <command>./test --keep-going --logdir=tests-logs --save-logs</command>. 107 Some tests fail for unknown reasons.</para> 103 RAID and that a version of mdadm is not already running. As many as 51 out 104 of 123 tests may fail.</para> 105 106 <para>First fix the test script to avoid a bogus error message when 107 tests fail and build the supporting programs:</para> 108 109 <screen><userinput>sed -i 's# if.* == "1"#& -a -e $targetdir/log#' test && 110 make test</userinput></screen> 111 112 <para>Run the tests as the <systemitem class="username">root</systemitem> user:</para> 113 114 <screen><userinput>./test --keep-going --logdir=test-logs --save-logs</userinput></screen> 108 115 109 116 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> … … 129 136 130 137 <para> 131 <parameter>--logdir=test s-logs</parameter>: Defines that the directory132 where test slogs are saved.138 <parameter>--logdir=test-logs</parameter>: Defines that the directory 139 where test logs are saved. 133 140 </para> 134 141
Note:
See TracChangeset
for help on using the changeset viewer.