From ff7b23bd274c5519fbc66997a6f5bf0825ca2d65 Mon Sep 17 00:00:00 2001 From: vortechs <> Date: Tue, 3 Sep 2002 20:12:01 +0000 Subject: [PATCH] o updated for LVM 1.0.5 which pretty much just meant changing the version numbers o Removed the glossary - it was unnecessary o Made note that Slackware 8.1 needs no boot-time script modifications o removed all mention of bugzilla.sistina.com - this has been removed due to disuse and neglect o Updated bug reporting sections due to bugzilla removal. o removed mention of Mike Tilstra from document at his request. --- LDP/howto/linuxdoc/LVM-HOWTO.sgml | 179 +++++++----------------------- 1 file changed, 42 insertions(+), 137 deletions(-) diff --git a/LDP/howto/linuxdoc/LVM-HOWTO.sgml b/LDP/howto/linuxdoc/LVM-HOWTO.sgml index 09e7fd19..ebbe12b1 100644 --- a/LDP/howto/linuxdoc/LVM-HOWTO.sgml +++ b/LDP/howto/linuxdoc/LVM-HOWTO.sgml @@ -3,15 +3,15 @@ LVM HOWTO <author>Maintainer: AJ Lewis <tt>lewis(at)sistina.com</tt> -<date>v0.1, 2002-04-28 +<date>v0.2, 2002-09-02 <abstract> This document describes how to build, install, and configure LVM for Linux. A basic description of LVM is also included. This version of -the HowTo is for 1.0.3. <bf>This HOWTO should be considered BETA. -Please provide any feedback at -<url url="http://bugzilla.sistina.com" name="http://bugzilla.sistina.com"></bf> -Copyright 2001 Sistina Software, Inc. +the HowTo is for 1.0.5. +<bf> Please provide any feedback at +<url url="mailto:linux-lvm@sistina.com_NOSPAM" name="linux-lvm(at)sistina.com"></bf> +Copyright 2002 Sistina Software, Inc. </abstract> <toc> @@ -25,7 +25,7 @@ This is an attempt to collect everything needed to know to get LVM up and running. The entire process of getting, compiling, installing, and setting up LVM will be covered. Pointers to LVM configurations that have been tested with will also be included. -This version of the HowTo is for LVM 1.0.3. +This version of the HowTo is for LVM 1.0.5. All previous versions of LVM are considered obsolete and are only kept for historical reasons. This document makes no attempt to explain or describe @@ -33,15 +33,11 @@ the workings or use of those versions. <sect1>Latest Version <P> -We will keep the latest version of this HOWTO in the CVS with the other -papers. You can get it by checking out ``papers'' from the same CVS -server as GFS. You should always be able to get a human readable version -of this HowTo from the -<url url="http://www.sistina.com/lvm/Pages/howto.html" name="http://www.sistina.com/lvm/Pages/howto.html">. - -Most of the layout and setup for this HOWTO was originally put together by -<htmlurl url="mailto:conrad@sistina.com_NOSPAM" name="Mike Tilstra"> for the -<url url="http://sistina.com/gfs/Pages/howto.html" name="Global File System HowTo">. +We will keep the latest version of this HOWTO in the CVS with the other LDP +HowTos. You can get it by checking out ``LDP/howto/linuxdoc/LVM-HOWTO.sgml'' +from the same CVS server as GFS. You should always be able to get a human +readable version of this HowTo from the +<url url="http://www.tldp.org/HOWTO/LVM-HOWTO.html" name="http://www.tldp.org/HOWTO/LVM-HOWTO.html">. <sect1>Disclaimer <P> @@ -57,21 +53,21 @@ the use of the information documented herein. List of everyone who has put words into this file. <itemize> - <item> <htmlurl url="mailto:thornber@sistina.com_NOSPAM" name="Joe Thornber"> - <item> <htmlurl url="mailto:conrad@sistina.com_NOSPAM" name="Mike Tilstra"> <item> <htmlurl url="mailto:lewis@sistina.com_NOSPAM" name="AJ Lewis"> + <item> <htmlurl url="mailto:thornber@sistina.com_NOSPAM" name="Joe Thornber"> <item> <htmlurl url="mailto:caulfield@sistina.com_NOSPAM" name="Patrick Caulfield"> </itemize> +Please notify the HowTo maintainer if you believe you should be listed above. <sect>What is LVM? <P> LVM is a Logical Volume Manager implemented by Heinz Mauelshagen for the Linux operating system. As of kernel version 2.4, LVM is incorporated in the main kernel source tree. This does not mean, however, -that your 2.4.x kernel is up to date with the latest version of LVM. -You currently still need to apply LVM patches to kernel 2.4.9 if you want -to be safe. +that your 2.4.x kernel is up to date with the latest version of LVM. Look at +the <url url="ftp://ftp.sistina.com/pub/LVM/1.0/README" name="README"> for the +latest information about which kernels have the latest code in them. <sect>What is Logical Volume Management? <P> @@ -531,25 +527,25 @@ you already have the LVM module. Check the version of the tools you have on your system. You can do this by running any of the LVM command line tools with the '-h' flag. Use <tt>pvscan -h</tt> if you don't know any of the commands. If the version number listed at the -top of the help listing is LVM 1.0.3, <bf>use your current setup</bf> +top of the help listing is LVM 1.0.5, <bf>use your current setup</bf> and avoid the rest of this section. <sect1>Building a patch for your kernel <label id="buildlvmpatch"> <P> -In order to patch the linux kernel to support LVM 1.0.3, you must do the +In order to patch the linux kernel to support LVM 1.0.5, you must do the following: <enum> -<item> Unpack LVM 1.0.3 +<item> Unpack LVM 1.0.5 <tscreen><verb> -# tar zxf lvm_1.0.3.tar.gz +# tar zxf lvm_1.0.5.tar.gz </verb></tscreen> <item> Enter the root directory of that version. <tscreen><verb> -# cd LVM/1.0.3 +# cd LVM/1.0.5 </verb></tscreen> @@ -575,13 +571,13 @@ configure if your linux kernel source is not in /usr/src. (Run </verb></tscreen> -You should now have a patch called <tt>lvm-1.0.3-$KERNELVERSION.patch</tt> +You should now have a patch called <tt>lvm-1.0.5-$KERNELVERSION.patch</tt> in the patches directory. This is the LVM kernel patch referenced in later sections of the howto. <item> Patch the kernel <tscreen><verb> -# cd /usr/src/linux ; patch -pX < /directory/lvm-1.0.3-$KERNELVERSION.patch +# cd /usr/src/linux ; patch -pX < /directory/lvm-1.0.5-$KERNELVERSION.patch </verb></tscreen> @@ -631,7 +627,7 @@ it will be called <tt>lvm-mod.o</tt> If you want to use snapshots with ReiserFS, make sure you apply the <tt>linux-2.4.x-VFS-lock</tt> patch (there are copies of this -in the <tt>LVM/1.0.3/PATCHES</tt> directory.) +in the <tt>LVM/1.0.5/PATCHES</tt> directory.) <sect1>Checking the proc file system <P> @@ -757,7 +753,11 @@ are mounted read-only, before the comment that says <sect1>Slackware <p> -You should apply the following patch to /etc/rc.d/rc.S +Slackware 8.1 requires no updating of boot time scripts in order to make LVM +work. + +For versions previous to Slackware 8.1, +you should apply the following patch to /etc/rc.d/rc.S <tscreen><verb> cd /etc/rc.d cp -a rc.S rc.S.old @@ -910,18 +910,18 @@ To remove the library and tools you just installed, run ``<tt>make remove</tt>''. You must have the original source tree you used to install LVM to use this feature. -<sect>Transitioning from previous versions of LVM to LVM 1.0.3 +<sect>Transitioning from previous versions of LVM to LVM 1.0.5 <P> -Transitioning from previous versions of LVM to LVM 1.0.3 should +Transitioning from previous versions of LVM to LVM 1.0.5 should be fairly painless. We have come up with a method to read in PV version 1 metadata (LVM 0.9.1 Beta7 and earlier) as well as PV version 2 metadata (LVM 0.9.1 Beta8 and LVM 1.0). -<em>Warning:</em> New PVs initialized with LVM 1.0.3 are created with +<em>Warning:</em> New PVs initialized with LVM 1.0.5 are created with the PV version 1 on-disk structure. This means that LVM 0.9.1 Beta8 and -LVM 1.0 cannot read or use PVs created with 1.0.3. +LVM 1.0 cannot read or use PVs created with 1.0.5. -<sect1>Upgrading to LVM 1.0.3 with a non-LVM root partition +<sect1>Upgrading to LVM 1.0.5 with a non-LVM root partition <P> There are just a few simple steps to transition this setup, but it is still recommended that you backup your data before you try it. You @@ -966,7 +966,7 @@ Reboot and enjoy. </enum> -<sect1>Upgrading to LVM 1.0.3 with an LVM root partition and initrd +<sect1>Upgrading to LVM 1.0.5 with an LVM root partition and initrd <P> This is relatively straightforward if you follow the steps carefully. It is recommended you have a good backup and a suitable rescue disk @@ -2716,7 +2716,7 @@ Just telling us that LVM did not work does not provide us with enough information to help you. We need to know about your setup and the various components of your configuration. The first thing you should do is check the -<url url="http://bugzilla.sistina.com/" name="Bug Reporting System"> +<url url="http://lists.sistina.com/pipermail/linux-lvm/" name="linux-lvm mailing list archives"> to see if someone else has already reported the same bug. If you do not find a bug report for a problem similar to yours you should collect as much of the following information as possible. The list @@ -2767,10 +2767,7 @@ is grouped into three categories of errors. This can be a lot of information. If you end up with more than a couple of files, tar and gzip them into a single archive. Submit this compressed -archive file to the bug reporting system or send mail to lvm-devel along -with a short description of the error. We would prefer you used the -<url url="http://bugzilla.sistina.com/" name="Bug Reporting System">, -that is why we have it. +archive file to lvm-devel along with a short description of the error. <sect>Contact and Links <P> @@ -2792,6 +2789,8 @@ Subscription to all lists is accomplished through a web interface <tag/linux-lvm/ This list is aimed at user-related questions and comments. You may be able to get the answers you need from other people who have the same issues. Open discussion is encouraged. + Bug reports should be sent to this list, although technical discussion + regarding the bug's fix may be moved to the lvm-devel list. <tag/lvm-devel/ This is the development list for LVM. It is intended to be an open discussion on bugs, desired features, and questions about the @@ -2803,8 +2802,9 @@ Subscription to all lists is accomplished through a web interface commits to the cvs tree. Its main purpose is to keep up with the cvs tree. - <tag/lvm-bugs/ This is the default owner for all bugs in our bug tracking - system. Sign up to this list if you want to see all of the new bugs. + <tag/lvm-bugs/ This list is rarely used anymore. Bugs should be sent to the + linux-lvm list. + </descrip> <sect1>Links <label id="Links"> @@ -2815,102 +2815,7 @@ LVM Links: <item>The <url url="http://www.sistina.com/lvm/" name="Logical Volume Manager"> home page. - <item><url url="http://bugzilla.sistina.com/" name="Bug Reporting System">. - <item> The <url url="ftp://ftp.sistina.com/pub/LVM/" name="LVM ftp"> site. </itemize> -<sect1>Glossary <label id="Glossary"> -<P> -<descrip> - <tag/1 MHz/ A frequency of one million (<f>10<sup/6/</f>) Hertz (cycles per second). - - <tag/1 Mflop/s/ A computational rate of one million (<f>10<sup/6/</f>) floating-point - operations per second. - - <tag/1 Gflop/s/ A computational rate of one billion (<f>10<sup/9/</f>) floating-point - operations per second. - - <tag/1 Tflop/s/ A computational rate of one trillion (<f>10<sup/12/</f>) - floating-point operations per second. - - <tag/1 KByte/ <f>2<sup/10/</f> bytes of data. - - <tag/1 MByte/ <f>2<sup/20/</f> bytes of data. - - <tag/1 GByte/ <f>2<sup/30/</f> bytes of data. - - <tag/1 TByte/ <f>2<sup/40/</f> bytes of data. - - <tag/1 MByte/s/ A data transfer rate of <f>2<sup/20/</f> bytes of data - per second. - - <tag/1 GByte/s/ A data transfer rate of <f>2<sup/30/</f> bytes of data - per second. - - <tag/1 TByte/s/ A data transfer rate of <f>2<sup/40/</f> bytes of data per second. - - <tag/arbitrate/ Process of selecting one L_Port from a collection of - several ports that concurrently request use of the - arbitrated loop. - - <tag/arbitrated loop/ A loop type topology where two or more ports can be - interconnected, but only two ports at a time can - communicate. - - <tag/CDSL/ Context Dependant Symbolic Links - - <tag/CIDEV/ Configuration Information Device - - <tag/DMEP/ Device Memory Export Protocol - - <tag/F_Port/ A port in a fabric where an N_Port or NL_Port may attach - - <tag/fabric/ A group of interconnections between ports that includes a - fabric element. - - <tag/FCP/ Fibre Channel Protocol. - - <tag/FL_Port/ A port in a fabric when an N_Port or an NL_Port may attach. - - <tag/GNBD/ GNBD Network Block Device. A method of sharing a disk on one - node to many other nodes. - - <tag/HBA/ See Host Bus Adapter. - - <tag/Host Bus Adapter/ The physical hardware installed in a node that - allows the node to access a shared network medium. - - <tag/L_Port/ An arbitrated loop port: either an NL_Port, an FL_Port, or - a GL_Port. - - <tag/LUN/ Logical Unit Number - - <tag/N_Port/ A port attached to a node for use with point-to-point or - fabric technology. - - <tag/NL_Port/ A port attached to a node for use in all three topologies. - - <tag/node/ A device that has at least one N_Port or NL_Port (Fibre Channel - only). - - <tag/NPS/ Network Power Switch - - <tag/point-to-point/ A topology where exactly two ports communicate. - - <tag/RAID/ Redundant Arrays of Independent Disks - - <tag/stomith/ Shoot The Other Machine In The Head. A technique used for - removing a node from a cluster operation. - - <tag/storage cluster/ A group of networked computers that have equal, - concurrent access to a shared storage space. - - <tag/switch/ A particular implementation of a fabric topology. Almost - exclusively a hardware device. - - <tag/topology/ The arrangment in which the nodes of a LAN are connected - to each other. -</descrip> - </article>