Ignore:
Timestamp:
Mar 12, 2007, 12:23:16 AM (17 years ago)
Author:
Bruno Cornec
Message:

Port from stable important patches for 2.2.2:
mindi-busybox:

  • Improve Gentoo packaging

mindi:

  • Better messages for analyze-my-lvm
  • Add support for newer Qlogic drivers (qla2300 & 2400), mpt, dm and ohci
  • Fix a bug in mindi for the FAILSAFE support
  • PATH fixed for init in restore (/usr/games added for petris)
  • Fiw a bug where restore failing because no archive files are found when -G is used
  • /media is now completely excluded as per StandardsCompliance

mondo:

  • Handle no compression + verify correctly
  • various HOWTO fixes
  • Fix temporarily a bug when a biggiefile > 32MB was compressed below the size

of a slice (16MB)

  • Better module loading in insmod_crucial_modules
  • Improve Gentoo packaging
  • Small typo fix for mondorestore man page
  • Small memory management improvements
  • Store NFS config only once
  • Fix a flaw in libmondo-mountlist.c (there since rev [1] !!)
  • Increased MAX_STR_LEN to 384 to make it divisible without remainder by eight

for 64 bits platforms

  • Fix a bug where no bzip2 format file would be found when supporting gzip
  • CentOS fixes
File:
1 edited

Legend:

Unmodified
Added
Removed

  • branches/2.2.2/mondo-doc/mondorescue-howto.sgml

    r978 r1236  
    7575</link>.</para>
    7676<para>
    77 or any later version published by the Free Software Foundation; with no Invarian
    78 t Sections, Front-Cover Texts or Back-Cover Texts. This document is distributed
    79 hoping it will be useful, but <emphasis>without any guaranty</emphasis>; you're
    80 completely responsible of its use, and coulnd't complain in case it doesn't work
    81 , or even if it breaks the hardware. All the software included in it, if not alr
    82 eady copyrighted is released under the GPL.
     77or any later version published by the Free Software Foundation; with no Invariant Sections, Front-Cover Texts or Back-Cover Texts. This document is distributed hoping it will be useful, but <emphasis>without any guaranty</emphasis>; you're completely responsible of its use, and coulnd't complain in case it doesn't work, or even if it breaks the hardware. All the software included in it, if not already copyrighted is released under the GPL.
    8378</para>
    8479</legalnotice>
    … …  
    173168e-mail! Thank you. Without it we can't offer
    174169any tangible help because you aren't either. That's what the log
    175 file is for. It is located at <filename>/var/log/mondo-archive.log</filename>; and <filename>/var/log/miindi.log</filename> or at <filename>/var/log/mondo-restore.log</filename>
    176 </para>
    177 <para>
    178 This document was originaly written by native english speakers, but is maintained by a non-native english speaker so help me correct mistaques instead of rumbling that I've done one :-)
     170file is for. It is located at <filename>/var/log/mondo-archive.log</filename>; and <filename>/var/log/mindi.log</filename> or at <filename>/var/log/mondo-restore.log</filename>
     171</para>
     172<para>
     173This document was originaly written by native english speakers, but is maintained by a non-native english speaker so help me correct mistaques (sic) instead of rumbling that I've done one :-)
    179174</para>
    180175<para>
    … …  
    711706boot-time. Mondo uses fdisk, mkfs, cat, less, more, afio, gzip,
    712707bzip2, your keyboard configuration, your glibc libraries, your
    713 other libraries, your kernel, your modules, ... a lot! Mindi takes
    714 care of all that, so that Mondo can get on with the job of backing
     708other libraries, your kernel, your modules, ... which is a lot of tools!
     709Mindi takes care of all that, so that Mondo can get on with the job of backing
    715710up or restoring your data.
    716711</para>
    … …  
    738733drives. That works for most drives but some drives just don't like
    739734that.</para>
    740 <para>Mondo Rescue has tested thousands of times on various computers.
    741 It worked for them.
     735<para>Mondo Rescue has been tested thousands of times on various computers.
     736It has worked for them.
    742737Thousands of users testify to Mondo's stability and its ease of
    743738use. However, please test it on your own system before you rely on
    … …  
    858853        Since November 2005, Hugo Rabson has tranfered the maintenance
    859854        of the Mondo Rescue suite to Andree Leidenfrost and Bruno Cornec,
    860         both previous developpers and packagers of the tool since nearly
     855        both previous developers and packagers of the tool since nearly
    861856        the begining.
    862857</para>
    … …  
    948943<para>See Mondo's <ulink url="http://www.mondorescue.org/downloads.shtml">Download
    949944page</ulink> for details.</para>
    950 <para>Mondo requires afio, bzip2, cdrtools/cdrecord/growisofs, ncurses, newt,
     945<para>Mondo requires afio, bzip2, cdrtools/cdrecord/growisofs (may be part of the dvd+rw-tools package), ncurses, newt,
    951946isolinux/syslinux, lzo (optional), lzop (optional), mkisofs, slang,
    952947and a few other packages.</para>
    … …  
    10291024</sect1>
    10301025
     1026<sect1 id="installation-mindi-busybox">
     1027<title>Mindi Busybox Installation</title>
     1028<para>If you are installing from a tarball then copy it to wherever
     1029you have enough space, for example /tmp and type:</para>
     1030<para></para>
     1031<informaltable><tgroup cols="1"><tbody>
     1032<row>
     1033<entry>
     1034
     1035        bash# cd /tmp
     1036</entry>
     1037</row>
     1038<row>
     1039    <entry>
     1040        bash# tar -zxvf mindi-busybox-1.x.tgz
     1041    </entry>
     1042</row>
     1043<row>
     1044    <entry>
     1045        bash# cd mindi-busybox-1.x
     1046    </entry>
     1047</row>
     1048<row>
     1049    <entry>
     1050        bash# make oldconfig
     1051    </entry>
     1052</row>
     1053<row>
     1054    <entry>
     1055        bash# make busybox
     1056    </entry>
     1057</row>
     1058<row>
     1059    <entry>
     1060        bash# make install
     1061    </entry>
     1062</row>
     1063</tbody></tgroup></informaltable>
     1064<para>This installs busybox files and symlinks into /usr/local/lib/mindi/rootfs
     1065</para>
     1066<para>Or, if you are installing from an RPM/deb then copy it to
     1067wherever you have enough space, for example /tmp and type:</para>
     1068<para></para>
     1069<informaltable><tgroup cols="1"><tbody>
     1070<row>
     1071<entry>
     1072
     1073bash# rpm -Uvh /tmp/mindi-busybox-1.x-x.i386.rpm
     1074</entry>
     1075</row>
     1076<row>
     1077<entry>
     1078
     1079or
     1080</entry>
     1081</row>
     1082<row>
     1083<entry>
     1084
     1085bash# dpkg -i /tmp/mindi-busybox-1.x-x.deb
     1086
     1087</entry>
     1088</row>
     1089</tbody></tgroup></informaltable>
     1090
     1091<para>This installs busybix files and symlinks into /usr/lib/mindi/rootfs
     1092</para>
     1093</sect1>
     1094
    10311095<sect1 id="installation-mondo">
    10321096<title>Mondo Installation</title>
    … …  
    10941158<para>This installs mondo into /usr/lib/mondo and installs
    10951159the programs into /usr/sbin</para>
     1160</sect1>
     1161
     1162<sect1 id=rpm-verif>
     1163        <title>RPM verifications</title>
     1164        <para>For RPM based distributions (Fedora, OpenSuSE, Mandriva, ...), you may want to do this post-install in order to check the validity of your installation:</para>
     1165<informaltable><tgroup cols="1"><tbody>
     1166<row>
     1167    <entry>
     1168        bash# rpm -Va mindi mondo mindi-busybox
     1169    </entry>
     1170</row>
     1171</tbody></tgroup></informaltable>
     1172<para>
     1173    This gives some truly obtuse output. Basically it will list all files that do NOT pass the verify tests (done on size, MD5 signature, etc). Please read rpm man page to discover the meaning of the output.
     1174    </para>
    10961175</sect1>
    10971176</chapter>
    … …  
    12691348
    12701349<sect1 id="backup-recommandations">
    1271 <title>Recommandations</title>
     1350<title>Recommendations</title>
    12721351<itemizedlist>
    12731352<listitem>
    … …  
    12751354        compare differences following the backup). Especially shutdown
    12761355        properly any running database on your system, as the recovery
    1277         may lead to corrupted data.</para>
     1356        may lead to corrupted data. Or if applicable, boot to single user mode.</para>
    12781357</listitem>
    12791358<listitem>
    … …  
    14881567 has been done. The problem lies in the fact that cron does not allow
    14891568 user interaction with a job. If you schedule a mondoarchive job via
    1490  cron, you better be sure it needs only one media. in practical terms,
     1569 cron, you better be sure it needs only one media. In practical terms,
    14911570 this means using tapes or ISOs (if CD-R(W) is your backup medium).
    14921571 However, for tape users, there's always the possibility that the
    … …  
    15151594If your backup already occupies two media, this method will allow
    15161595 as much of the backup as possible to proceed during quiet periods.
    1517  Time the backup to start wich enough time to complete the first media
     1596 Time the backup to start with enough time to complete the first media
    15181597 shortly before the operator arrives for work. The next media can
    15191598 be mounted and the backup completed asap and minimises the time for
    … …  
    15401619 of interacting via a FIFO or some such) except termination via its
    15411620 pid. The only program that I know of that allows such interaction
    1542  and serves as a wrapper for other prrocesses is 'screen'
     1621 and serves as a wrapper for other processes is 'screen'
    15431622 </para>
    15441623 </sect2>
    … …  
    15481627 attach to a terminal when it first starts. This won't happen under
    15491628 cron so screen will fail. Fortunately, screen comes with a "start
    1550  detached" option.
     1629 detached" (-d) option.
    15511630 </para>
    15521631 </sect2>
    … …  
    18451924<listitem><para>Wipe your drives and restore everything,
    18461925automatically and unattended. Warning: This does exactly what is
    1847 says, so be carefull using it.</para>
     1926says, so be careful using it.</para>
    18481927</listitem></varlistentry>
    18491928<varlistentry><term>Expert</term>
    … …  
    23752454</tbody></tgroup></informaltable>
    23762455
    2377 <para>I hope this manual is proving to be useful to you.</para>
     2456<para>I hope this manual was useful for you.</para>
    23782457</sect2>
    23792458</sect1>
    … …  
    23962475<itemizedlist>
    23972476<listitem>
    2398 <para>Your kernel version</para>
    2399 </listitem>
    2400 <listitem>
    2401 <para>Your Linux distro's name and version</para>
    2402 </listitem>
    2403 <listitem>
    2404 <para>Whether your kernel supports initrd and loopfs; it should!</para>
    2405 </listitem>
    2406 <listitem>
    2407 <para>What sort of PC you are using, including hard disk configurations</para>
     2477<para>Your kernel version (uname -a)</para>
     2478</listitem>
     2479<listitem>
     2480        <para>Your Linux distro's name and version (/etc/distro-release)</para>
     2481</listitem>
     2482<listitem>
     2483        <para>Whether your kernel supports initrd and loopfs; it should! (grep -E '^CONFIG_BLK_DEV_LOOP|^CONFIG_BLK_DEV_INITRD' /usr/src/linux/.config </para>
     2484</listitem>
     2485<listitem>
     2486<para>What sort of PC you are using, including hard disk configurations (results of dmidecode, lshw, fdisk -l are useful here)</para>
    24082487</listitem>
    24092488</itemizedlist>
    … …  
    24302509'mondo'. Hugo Rabson wasn't sure what to call this project. 'Faust' was one
    24312510idea he had, partly as a dig at his former boss who practically owned
    2432 him because of his legal status at the time. In the end, He chose
     2511him because of his legal status at the time. In the end, he chose
    24332512something short and distinctive.</para>
    24342513</answer>
    … …  
    24382517                keels over and dies. What's wrong?</para></question>
    24392518<answer>
    2440         <para>A: It works on Red Hat 7.x/8/9, RHEL 2.1/3/4, Mandrakelinux 8.x/9.x/10.x, Debian 3.0, most flavors
     2519        <para>A: It works on Red Hat 7.x/8/9, RHEL 2.1/3/4, Mandrakelinux 8.x/9.x/10.x/200x, Fedora 4/5/6, Debian 3.x, most flavors
    24412520                of SuSE/SLES, some flavors of Slackware, etc.
    24422521The more distributions we support, the more moving targets we have to
    … …  
    24572536                <para>A: Please send a copy of <filename>/var/log/mindi.log</filename> to the &ML;
    24582537along with a description of your distro, your kernel, etc.
    2459 Oh, and before sending it, please read it asit's much easier to understand it.</para>
     2538Oh, and before sending it, please read it as it is much easier to understand it.</para>
    24602539</answer>
    24612540</qandaentry>
    … …  
    24982577please?</para></question>
    24992578<answer>
    2500 <para>A: please enter the suggestion in our feature system at &WWW;
     2579<para>A: Please enter the suggestion in our feature system at &WWW;
    25012580</para>
    25022581</answer>
    … …  
    26352714<para>A: Recompile your kernel (or use '-k FAILSAFE'). Take a look
    26362715at <link linkend="overview-sysrq-kernelreq">Linux Kernel support</link> to
    2637 see what you're kernel must support.</para>
     2716see what your kernel must support.</para>
    26382717</answer>
    26392718</qandaentry>
    … …  
    26442723<para>A: Recompile your kernel and add Virtual memory file system
    26452724support. Take a look at <link linkend="overview-sysrq-kernelreq">Linux
    2646 Kernel support</link> to see what you're kernel must support. (Of
     2725Kernel support</link> to see what your kernel must support. (Of
    26472726course, if your PC has less than 64MB of RAM, you could always...
    26482727what's the phrase? I know, upgrade your RAM!)</para>
    … …  
    26562735        <para>A: Your kernel must support initrd, loopfs, IDE|SCSI|USB CD-ROM's, and
    26572736ramdisks. Take a look at <link linkend="overview-sysrq-kernelreq">Linux
    2658 Kernel support</link> to see what you're kernel must support. If
     2737Kernel support</link> to see what your kernel must support. If
    26592738your kernel does not support these things, Mondo will not boot from
    26602739your CD. However, when running Mindi, you may choose to use _its_
    … …  
    27142793kernel and/or recompile it. Take a look at
    27152794<link linkend="overview-sysrq-kernelreq">Linux Kernel support</link> to see
    2716 what you're kernel must support.</para>
     2795what your kernel must support.</para>
    27172796</answer>
    27182797</qandaentry>
    … …  
    27512830<answer>
    27522831<para>A: Recompile your kernel and add initrd support. Take a look
    2753 at <link linkend="overview-sysrq-kernelreq">Linux Kernel support</link>to
    2754 see what you're kernel must support.</para>
     2832at <link linkend="overview-sysrq-kernelreq">Linux Kernel support</link> to
     2833see what your kernel must support.</para>
    27552834</answer>
    27562835</qandaentry>
    … …  
    28082887<question><para id="TAPENICE">Q: My tape drive
    28092888doesn't play nicely with Mondo at boot-time. What do I do?</para></question>
    2810 <answer><para>A: Play with 'mt'. Use its setblksize and
     2889<answer><para>A: Play with the 'mt' command (package mt-st). Use its setblksize and
    28112890defblksize switches to reconfigure your tape drive if necessary.
    28122891Some tape drives just are painful. If yours is one of
    … …  
    28872966                drives?</para></question>
    28882967<answer>
    2889 <para>A: Yes. See above.</para>
     2968        <para>A: Yes. See above.</para>
     2969        <para>Of course, mondo will relay on the kernel to support your tape drive. So you should first check that your kernel found it correctly. Use for example one of the following commands:</para>
     2970<informaltable><tgroup cols="1"><tbody>
     2971<row>
     2972<entry>
     2973        bash# dmesg | grep tape
     2974</entry>
     2975</row>
     2976<row>
     2977<entry>
     2978        bash# cat /proc/scsi/scsi
     2979</entry>
     2980</row>
     2981<row>
     2982<entry>
     2983        bash# mt -f /dev/st0 status
     2984</entry>
     2985</row>
     2986</tbody></tgroup></informaltable>
     2987
     2988
    28902989</answer>
    28912990</qandaentry>
    … …  
    29603059partitions and their settings. Mondo will do the partitioning and
    29613060formatting for you.</para>
    2962 <para>Tested Raid controllers includes all those showind only classical devices
     3061<para>Tested Raid controllers includes all those showing only classical devices
    29633062        such as /dev/sdx, and SmartArray cciss controllers.</para>
    29643063</answer>
    … …  
    29713070<informaltable><tgroup cols="1"><tbody>
    29723071<row>
    2973 <entry>
    2974 
    2975 bash# cdrecord -scanbus
    2976 
    2977 </entry>
    2978 </row>
    2979 </tbody></tgroup></informaltable>
     3072    <entry>
     3073        bash# cdrecord -scanbus
     3074    </entry>
     3075</row>
     3076</tbody></tgroup></informaltable>
     3077<para>or for ATAPI type of devices:</para>
     3078<para></para>
     3079<informaltable><tgroup cols="1"><tbody>
     3080<row>
     3081    <entry>
     3082        bash# cdrecord -scanbus dev=ATAPI
     3083    </entry>
     3084</row>
     3085</tbody></tgroup></informaltable>
     3086<para>you may replace ATAPI by ATA in the previous line with certain cdrecord versions and hadrware configurations</para>
     3087
    29803088
    29813089<para>Find your CD burner's device# (e.g. '0,0,0'). Call Mondo with
    … …  
    32093317<qandaentry>
    32103318<question>
    3211 <para id="LVM"/>Q: I can't nuke-restore my LVM or RAID or
     3319<para id="LVM">Q: I can't nuke-restore my LVM or RAID or
    32123320LVM-on-RAID setup. I have to do it manually. What now?</para></question>
    32133321<answer>
Note: See TracChangeset for help on using the changeset viewer.