Menu
▾
▴
[Evms-cvs-commits] Documentation/user_guide appx-csm.xml,NONE,1.1 appx-ext23.xml,NONE,1.1 appx-initram.xml,NONE,1.1 appx-jfs.xml,NONE,1.1 appx-md.xml,NONE,1.1 appx-reiserfs.xml,NONE,1.1 appx-xfs.xml,NONE,1.1 clusterops-ug.xml,NONE,1.1 containerops-ug.xml,NONE,1.1 fsim-template.xml,NONE,1.1 EVMSUG.xml,1.1,1.2 EVMSUG2.xml,1.1,1.2 addfeatures-ug.xml,1.1,1.2 appx-dos.xml,1.1,1.2 appx-drivelink.xml,1.1,1.2 appx-lvm.xml,1.1,1.2 appx-snap.xml,1.1,1.2 assignseg-ug.xml,1.1,1.2 cmuse-ug.xml,1.1,1.2 convertto-ug.xml,1.1,1.2 create-cont.xml,1.1,1.2 create-drivelinking.xml,1.1,1.2 create-reg-ug.xml,1.1,1.2 create-seg.xml,1.1,1.2 create-snapshot.xml,1.1,1.2 createvol-ug.xml,1.1,1.2 debuglog-ug.xml,1.1,1.2 deleterecurs-ug.xml,1.1,1.2 displaydetails-ug.xml,1.1,1.2 expandshrink.xml,1.1,1.2 fsimops-ug.xml,1.1,1.2 install-ug.xml,1.1,1.2 over-ug.xml,1.1,1.2 plugintasks.xml,1.1,1.2 pref-ug.xml,1.1,1.2 EVMS_UG_idplan.xml,1.1,NONE cli.png,1.1,NONE evms_config.png,1.1,NONE gui.png,1.1,NONE gui_comp_vols.png,1.1,NONE linux_config.png,1.1,NONE lvm.png,1.1,NONE nbak.png,1.1,NONE view_evms.png,1.1,NONE view_xconfig.png,1.1,NONE
Update of /cvsroot/evms/Documentation/user_guide In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv16716 Modified Files: EVMSUG.xml EVMSUG2.xml addfeatures-ug.xml appx-dos.xml appx-drivelink.xml appx-lvm.xml appx-snap.xml assignseg-ug.xml cmuse-ug.xml convertto-ug.xml create-cont.xml create-drivelinking.xml create-reg-ug.xml create-seg.xml create-snapshot.xml createvol-ug.xml debuglog-ug.xml deleterecurs-ug.xml displaydetails-ug.xml expandshrink.xml fsimops-ug.xml install-ug.xml over-ug.xml plugintasks.xml pref-ug.xml Added Files: appx-csm.xml appx-ext23.xml appx-initram.xml appx-jfs.xml appx-md.xml appx-reiserfs.xml appx-xfs.xml clusterops-ug.xml containerops-ug.xml fsim-template.xml Removed Files: EVMS_UG_idplan.xml cli.png evms_config.png gui.png gui_comp_vols.png linux_config.png lvm.png nbak.png view_evms.png view_xconfig.png Log Message: Update for the EVMS User-Guide for version 2.0. Index: fsimops-ug.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/fsimops-ug.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- fsimops-ug.xml 16 Feb 2005 17:06:46 -0000 1.1 +++ fsimops-ug.xml 16 Feb 2005 17:13:57 -0000 1.2 @@ -1,4 +1,6 @@ + + <chapter id="evmsfsimops"><title>FSIMs and file system operations</title> <para>This chapter discusses the five File System Interface Modules (FSIMs) shipped with EVMS, and then provides examples of adding file systems and coordinating file system checks with the FSIMs.</para> @@ -22,13 +24,17 @@ The JFS module supports the IBM journaling file system (JFS). Current support includes <command>mkfs</command>, <command>unmkfs</command>, <command>fsck</command>, and online file system expansion. -Support for external logging will be added in the near future. +Support for external logging will be added in a future release of EVMS. You must have at least version 1.0.9 of the JFS utilities for your system to work with this EVMS FSIM. You can download the latest utilities from the <ulink url="http://oss.software.ibm.com/jfs">JFS for Linux</ulink> site. </para> +<para> +For more information on the JFS FSIM, refer to <xref linkend="jfsfsim"/>. +</para> + </sect2> <sect2 id="fsimxfs"><title>XFS</title> @@ -37,6 +43,10 @@ Command support includes <command>mkfs</command>, <command>unmkfs</command>, <command>fsck</command>, and online expansion. Use version 1.2 or higher, which you can download from <ulink url="ftp://oss.sgi.com/projects/xfs/download">the SGI open source FTP directory.</ulink> </para> + +<para> +For more information on the XFS FSIM, refer to <xref linkend="xfsfsim"/>. +</para> </sect2> @@ -49,6 +59,10 @@ the ReiserFS utilities from <ulink url="http://www.namesys.com">The Naming System Venture (Namesys) </ulink> web site. </para> + +<para> +For more information on the ReiserFS FSIM, refer to <xref linkend="reiserfsim"/>. +</para> </sect2> <sect2 id="fsimext23"><title>Ext2/3</title> @@ -57,6 +71,10 @@ The FSIM supports <command>mkfs</command>, <command>unmkfs</command>, <command>fsck</command>, and offline shrinkage and expansion. </para> + +<para> +For more information on the Ext2/3 FSIM, refer to <xref linkend="ext23fsim"/>. +</para> </sect2> <sect2 id="fsimswapfs"><title>SWAPFS</title> @@ -118,9 +136,9 @@ <para>Alternatively, you can perform some of the steps to create a file system with the GUI context sensitive menu:</para> <orderedlist> - <listitem><para>From the <guimenuitem>Volumes</guimenuitem> tab, right click on + <listitem><para>From the <guimenuitem>Volumes</guimenuitem> tab, right click <filename>/dev/evms/my_vol</filename>.</para></listitem> - <listitem><para>Click on <guimenuitem>Make Filesystem...</guimenuitem></para></listitem> + <listitem><para>Click <guimenuitem>Make Filesystem...</guimenuitem></para></listitem> <listitem><para>Continue creating the file system beginning with step 2 of the GUI instructions. You can skip steps 4 and 5 of the GUI instructions.</para></listitem> </orderedlist> @@ -132,34 +150,21 @@ <para>Follow these steps to create a JFS file system with Ncurses: <orderedlist> - <listitem><para>Press - <keycap>2</keycap> for the volumes view. - </para></listitem> - - <listitem><para>Scroll down using the down arrow key until - <guimenuitem>/dev/evms/my_vol</guimenuitem> is highlighted. - </para></listitem> - - <listitem><para>Press <keycap>Enter</keycap>. + <listitem><para>Select <menuchoice><guimenu>Actions</guimenu><guimenuitem>File Systems</guimenuitem><guimenuitem>Make</guimenuitem></menuchoice>. </para></listitem> - <listitem><para>Scroll down using the down arrow until - <guimenuitem>Make File System</guimenuitem> is highlighted. - </para></listitem> +<listitem><para>Select JFS File System Interface Module.</para></listitem> - <listitem><para>Press <keycap>Enter</keycap>. - </para></listitem> +<listitem><para>Activate <guibutton>Next</guibutton>.</para></listitem> - <listitem><para>Scroll down using the down arrow until - <guimenuitem>JFS</guimenuitem> is highlighted. - </para></listitem> +<listitem><para>Select <filename>/dev/evms/my_vol</filename>.</para></listitem> - <listitem><para>Press <keycap>Enter</keycap>. - </para></listitem> +<listitem><para>Activate <guibutton>Next</guibutton>.</para></listitem> - <listitem><para>Scroll down using the down arrow until - <guimenuitem>Volume Label</guimenuitem> is highlighted. + <listitem><para>Scroll down using the <keycap>down</keycap> arrow until + <guimenuitem>Volume Label</guimenuitem> is highlighted. </para></listitem> + <listitem><para>Press <keycap>Spacebar</keycap>. </para></listitem> @@ -170,19 +175,24 @@ <listitem><para>Press <keycap>Enter</keycap>. </para></listitem> - <listitem><para>Customize any other options are you are interested in, - following the previous steps 8-11. - </para></listitem> + <listitem><para>Activate <guibutton>Make</guibutton>.</para></listitem> - <listitem><para>When you have finished customizing, press - <keycap>Enter</keycap>. - </para></listitem> +</orderedlist> +</para> +<para>Alternatively, you can perform some of the steps to create a file system with the +context sensitive menu:</para> - <listitem><para>The operation is completed when you save. - </para></listitem> +<orderedlist> +<listitem><para>From the Volumes view, press <keycap>Enter</keycap> on +<filename>/dev/evms/my_vol</filename>.</para> +</listitem> +<listitem><para>Activate the <guimenuitem>Make Filesystem</guimenuitem> menu item.</para> +</listitem> +<listitem><para>Continue creating the file system beginning with step 2 of the +Ncurses instructions.</para> +</listitem> </orderedlist> -</para> </sect2> <!-- CLI--> @@ -211,7 +221,7 @@ <para>You can also coordinate file system checks from the EVMS user interfaces.</para> <blockquote><example><title>Check a JFS File System</title> -<para>This example shows how to performa file system check on a JFS file system, named <filename>jfs_vol</filename>, on volume <filename>/dev/evms/my_vol</filename>, with verbose output. +<para>This example shows how to perform a file system check on a JFS file system, named <filename>jfs_vol</filename>, on volume <filename>/dev/evms/my_vol</filename>, with verbose output. </para></example></blockquote> <sect2 id="FSIMmkfsgui"><title>Using the EVMS GUI</title> @@ -244,9 +254,9 @@ <para>Alternatively, you can perform some of the steps to check a file system with the GUI context sensitive menu:</para> <orderedlist> - <listitem><para>From the <guimenuitem>Volumes</guimenuitem> tab, right click on + <listitem><para>From the <guimenuitem>Volumes</guimenuitem> tab, right click <filename>/dev/evms/my_vol</filename>.</para></listitem> - <listitem><para>Click on <filename>Check/Repair File System...</filename> + <listitem><para>Click <filename>Check/Repair File System...</filename> </para></listitem> <listitem><para>Continue checking the file system beginning with step 3 of the GUI instructions.</para></listitem> @@ -260,43 +270,42 @@ <para>Follow these steps to check a JFS file system with Ncurses: <orderedlist> - <listitem><para>Press - <keycap>2</keycap> for the volumes view. - </para></listitem> - - <listitem><para>Scroll down using the down arrow key until - <guimenuitem>/dev/evms/my_vol</guimenuitem> is highlighted. - </para></listitem> - - <listitem><para>Press <keycap>Enter</keycap>. + <listitem><para>Select <menuchoice><guimenu>Actions</guimenu> + <guimenuitem>File System</guimenuitem><guimenuitem>Check/Repair</guimenuitem></menuchoice> </para></listitem> - <listitem><para>Scroll down using the down arrow until - <guimenuitem>Check/Repair File System</guimenuitem> is highlighted. + <listitem><para>Select + <filename> /dev/evms/my_vol</filename>. </para></listitem> - <listitem><para>Press <keycap>Enter</keycap>. + <listitem><para>Activate <guibutton>Next</guibutton>. </para></listitem> - <listitem><para>Scroll down using the down arrow until - <guimenuitem>Verbose Output</guimenuitem> is highlighted. + <listitem><para>Scroll down using the <keycap>down</keycap> arrow until + <guimenuitem>Vebose Output</guimenuitem> is highlighted. </para></listitem> - <listitem><para>Press <keycap>Spacebar</keycap> to change <guimenuitem>Verbose Output</guimenuitem> to <keycap>True</keycap>. + <listitem><para>Press <keycap>Spacebar</keycap> to change <guimenuitem>Verbose Output</guimenuitem> to <keycap>Yes</keycap>. </para></listitem> - <listitem><para>Repeat steps 6 and 7 to customize any other options you are interested in. + <listitem><para>Activate <guibutton>Check</guibutton>. </para></listitem> - <listitem><para>When you have finished customizing, press - <keycap>Enter</keycap>. - </para></listitem> +</orderedlist> +</para> - <listitem><para>The operation is completed when you save. - </para></listitem> +<para>Alternatively, you can perform some of the steps to check a file system with the +context sensitive menu:</para> +<orderedlist> +<listitem><para>From the Volumes view, press <keycap>Enter</keycap> on <filename>/dev/evms/my_vol</filename>.</para> +</listitem> +<listitem><para>Activate the <guimenuitem>Check/Repair File System</guimenuitem> menu item.</para> +</listitem> +<listitem><para>Continue checking the file system beginning with step 3 of the Ncurses +instructions.</para> +</listitem> </orderedlist> -</para> </sect2> <!-- CLI--> Index: create-seg.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/create-seg.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- create-seg.xml 16 Feb 2005 17:06:46 -0000 1.1 +++ create-seg.xml 16 Feb 2005 17:13:56 -0000 1.2 @@ -1,4 +1,6 @@ + + <chapter id="evmscreateseg"><title>Creating segments</title> <para>This chapter discusses when to use segments and how to create them using @@ -62,9 +64,9 @@ fields, the <guibutton>Create</guibutton> button becomes available.</para></listitem> - <listitem><para>Click the - <guibutton>Create</guibutton> - button. A window opens to display the + <listitem><para>Click + <guibutton>Create</guibutton>. + A window opens to display the outcome.</para> </listitem> </orderedlist></para> @@ -73,60 +75,50 @@ <orderedlist><listitem><para>From the <guimenuitem>Segments</guimenuitem> tab, right click on <filename>sde_freespace1</filename>.</para></listitem> -<listitem><para>Click on <guibutton>Create Segment...</guibutton></para></listitem> +<listitem><para>Click <guibutton>Create Segment...</guibutton></para></listitem> <listitem><para>Continue beginning with step 4 of the GUI instructions.</para></listitem> </orderedlist> </sect2> <!-- Ncurses--> <sect2 id="ncurseg"><title>Using Ncurses</title> - <para>To create a segment using the Ncurses, follow the steps below:</para> + <para>To create a segment using Ncurses, follow these steps:</para> <orderedlist> - <listitem><para>Press <keycap>4</keycap> - to switch views.</para></listitem> - - <listitem><para>Scroll down using the - down arrow key until <guimenuitem>Disk Segments</guimenuitem> is highlighted. - Press <keycap>Enter</keycap>.</para></listitem> - - <listitem><para>Press <keycap>Enter</keycap> - again to display a sub menu on the - current selection.</para></listitem> - - <listitem><para>Select <guimenuitem>Create a - New Segment</guimenuitem>. Press - <keycap>Enter</keycap>. A list of segment - manager plug-ins opens. </para></listitem> - - <listitem><para>Select <guimenuitem>DOS Segment Manager</guimenuitem>. Press <keycap>Enter</keycap>.</para> + <listitem><para>Select <menuchoice><guimenu>Actions</guimenu><guimenuitem>Create</guimenuitem><guimenuitem>Segment</guimenuitem></menuchoice> to see a list of segment manager plug-ins.</para></listitem> - <para>The next dialog window - presents a list of free space + <listitem><para>Select <guimenuitem>DOS Segment Manager</guimenuitem>. + Activate <guibutton>Next</guibutton>.</para> +<para>The next dialog window + lists free space storage objects suitable for creating a new segment. </para></listitem> - <listitem><para>Select <filename>sde_freespace1</filename> by moving to it with the arrows - and then using <keycap>spacebar</keycap> - to select it. After the storage object is selected (it - is marked by an "X"), press <keycap>Enter</keycap>.</para> - <para>The last dialog window displays the selected freespace object and configuration options - available from the plug-in manager. Required fields are denoted by the "*" in front of the field - description. The DOS Segment Manager provides default values, but you might want to change some of these - values. </para></listitem> + <listitem><para>Select <filename>sde_freespace1</filename>. Activate <keycap>Next</keycap>.</para> + + </listitem> <listitem><para>Highlight the <guilabel>size field</guilabel> and press <keycap>spacebar</keycap>.</para></listitem> - <listitem><para>At the "::" prompt enter <userinput>100</userinput>. + <listitem><para>At the "::" prompt enter <userinput>100MB</userinput>. Press <keycap>Enter</keycap>. </para> </listitem> -<listitem><para>Check all fields to make sure they were entered appropriately. If the units are displayed as KB, and you desired MB, return to step 7 and enter the value of KB that is equal to the MB value you desired. For example, instead of entering 100 you would enter 102400 (100 x 1024) to convert the KB value to MB. </para></listitem> - - <listitem><para>After all required values have been completed, press <keycap>Enter</keycap> - and a results status message is displayed. </para> </listitem> + <listitem><para>After all required values have been completed, the <guibutton>Create</guibutton> + button becomes available.</para> </listitem> +<listitem><para>Activate <guibutton>Create</guibutton>.</para></listitem> </orderedlist> +<para>Alternatively, you can perform some of the steps to create a segment from the +context sensitive menu:</para> +<orderedlist> +<listitem><para>From the Segments view, press <keycap>Enter</keycap> on <filename>sde_frespace1</filename>.</para> +</listitem> +<listitem><para>Activate <guimenuitem>Create Segment</guimenuitem>.</para> +</listitem> +<listitem><para>Continue beginning with step 4 of the Ncurses instructions.</para> +</listitem> +</orderedlist> </sect2> @@ -158,4 +150,4 @@ </sect1> -</chapter> +</chapter> \ No newline at end of file Index: over-ug.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/over-ug.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- over-ug.xml 16 Feb 2005 17:06:46 -0000 1.1 +++ over-ug.xml 16 Feb 2005 17:13:57 -0000 1.2 @@ -1,5 +1,8 @@ + + + <chapter id="intro"><title>What is EVMS?</title> <para>EVMS brings a new model of volume management to Linux®. @@ -29,9 +32,10 @@ You can also use many types of file systems and manipulate these storage pieces in ways that best meet the needs of your particular work environment.</para> -<para>EVMS provides a choice of user interfaces that allow you to manage -storage space. -</para> +<para>EVMS also provides the capability to manage data on storage that is +physically shared by nodes in a cluster. This shared storage allows data to +be highly available from different nodes in the cluster.</para> + </sect1> <sect1 id="uis"><title>The EVMS user interfaces</title> @@ -105,9 +109,40 @@ <listitem><para>A collection of storage objects. A storage container consumes one set of storage objects and produces new storage objects. One common subset of storage containers is volume groups, - such as AIX® or LVM.</para></listitem> + such as AIX® or LVM.</para> + <para>Storage containers can be either of type private or cluster.</para> + </listitem> </varlistentry> + <varlistentry><term>Cluster storage container</term> + <listitem><para>Specialized storage containers that consume only disk objects + that are physically accessible from all nodes of a cluster.</para> + + <variablelist> + <varlistentry><term>Private storage container</term> + <listitem><para>A collection of disks that are physically accessible from all + nodes of a cluster, managed as a single pool of storage, and owned and accessed + by a single node of the cluster at any given time.</para> + </listitem> + </varlistentry> + + + + <varlistentry><term>Shared storage container</term> + <listitem><para>A collection of disks that are physically accessible from all + nodes of a cluster, managed as a single pool of storage, and owned and accessed + by all noDes of the cluster simultaneously.</para> + </listitem> + </varlistentry> + + <varlistentry><term>Deported storage container</term> + <listitem><para>A shared cluster container that is not owned by any node of the cluster.</para> + </listitem> + </varlistentry> + </variablelist> + + </listitem></varlistentry> + <varlistentry><term>Feature object</term> <listitem><para>A storage object that contains an EVMS native feature, such as bad block relocation. </para> @@ -241,7 +276,7 @@ Block Relocation, and snapshotting. </para> <variablelist> -<varlistentry><term>Drive Llnking</term> +<varlistentry><term>Drive Linking</term> <listitem><para>Drive linking allows any number of objects to be linearly concatenated together into a single object. A drive linked volume can be expanded by @@ -291,6 +326,13 @@ a user can make new file systems and check existing file systems by interacting with the FSIM.</para></listitem> </varlistentry> + + <varlistentry><term>Cluster Manager Interface Modules</term> + <listitem><para>Cluster Manager Interface Modules, also + known as the EVMS Clustered Engine (ECE), interface + with the local cluster manager installed on the system. + The ECE provides a standardized ECE API to the Engine + while hiding cluster manager details from the Engine.</para></listitem></varlistentry> </variablelist> </sect1> --- view_xconfig.png DELETED --- Index: debuglog-ug.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/debuglog-ug.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- debuglog-ug.xml 16 Feb 2005 17:06:46 -0000 1.1 +++ debuglog-ug.xml 16 Feb 2005 17:13:57 -0000 1.2 @@ -1,3 +1,4 @@ + <chapter id="debuglevels"><title>The EVMS log file and error data collection</title> <para>This chapter discusses the EVMS information and error log file and the various logging levels. It also explains how to change the logging level.</para> @@ -12,7 +13,7 @@ <para>There are several possible logging levels that you can choose to be collected in <filename>/var/log/evmsEngine.log</filename>. The "lowest" logging level, <filename>critical</filename>, collects only messages about serious system problems, whereas the "highest" level, <filename>everything</filename>, collects all logging related messages. When you specify a particular logging level, the Engine collects messages for that level and all the levels below it. </para> <para>The following table lists the allowable log levels and the information they provide:</para> -<para><table><title>EVMS logging levels</title><tgroup cols="2"><colspec colnum="1" colname="C1"></colspec><colspec colnum="2" colname="C2"></colspec> +<para><table><title>EVMS logging levels</title><tgroup cols="2"><colspec colnum="1" colname="C1"/><colspec colnum="2" colname="C2"/> <thead><row><entry>Level name</entry> <entry>Description</entry> </row></thead> <tbody> @@ -51,7 +52,7 @@ <guimenuitem>Engine</guimenuitem></menuchoice>. </para></listitem> - <listitem><para>Click on the <guibutton>Level</guibutton> you want. + <listitem><para>Click the <guibutton>Level</guibutton> you want. </para></listitem> </orderedlist></para> @@ -60,4 +61,3 @@ </sect1> </chapter> - --- NEW FILE: containerops-ug.xml --- <chapter id="containerops"><title>Clustering operations</title> <para>This chapter discusses how to configure cluster storage containers (referred to throughout this chapter as "cluster containers"), a feature provided by the eVMS Cluster Segment Manager (CSM).</para> <para>Disks that are physically accessible from all of the nodes of the cluster can be grouped together as a single manageable entity. EVMS storage objects can then be created using storage from these containers.</para> <para>Ownership is assigned to a container to make the container either private or shared. A container that is owned by any one node of the cluster is called a private container. EVMS storage objects and storage volumes created using space from a private container are accessible from only the owning node.</para> <para>A container that is owned by all the nodes in a cluster is called a shared container. EVMS storage objects and storage volumes created using space from a shared container are accessible from all nodes of the cluster simultaneously.</para> <para>EVMS provides the tools to convert a private container to a shared container, and a shared container to a private container. EVMS also provides the flexibility to change the ownership of a private container from one cluster node to another cluster node.</para> <sect1><title>Rules and restrictions for creating cluster containers</title> <para>Note the following rules and limitations for creating cluster containers:</para> <itemizedlist> <listitem><para>Non-shared disks should not be assigned to a cluster container.</para> </listitem> <listitem><para>Storage objects created on a cluster container must not span across multiple cluster containers. Currently, the EVMS Engine cannot enforce this rule, so you need to ensure that objects and volumes created from cluster storage manager segments do not span multiple containers.</para> </listitem> <listitem><para>A disk should not span across cluster containers.</para> </listitem> <listitem><para>RAID, snapshot, and BBR features should not be assigned to storage objects on a cluster container.</para> </listitem> </itemizedlist> </sect1> <sect1><title>Example: Create a private cluster container</title> <para>This section tells how to create a sample private container with EVMS and provides instructions for completing the following task</para> <blockquote><example><title>Create a private cluster container</title> <para>Given a system with three available shared disks (<filename>sdd</filename>, <filename>sde</filename>, and <filename>sdf</filename>), use the EVMS Cluster Segment Manager to combine these disk drives into a container called <filename>Priv1</filename> owned by <filename>node1</filename>. </para> </example> </blockquote> <sect2><title>Using the EVMS GUI</title> <para>To create a container with the EVMS GUI, follow these steps:</para> <orderedlist> <listitem><para>Select <menuchoice><guimenu>Actions</guimenu><guimenuitem>Create</guimenuitem> <guimenuitem>Container</guimenuitem> </menuchoice> to see a list of plug-ins that support container creation. </para> </listitem> <listitem><para>Select the <guimenuitem>Cluster Segment Manager</guimenuitem>.</para> </listitem> <listitem><para>Click <guibutton>Next</guibutton>.</para> <para>The next dialog window contains a list of storage objects that the CSM can use to create a container.</para> </listitem> <listitem><para>Select <filename>sdd</filename>, <filename>sde</filename>, and <filename>sdf</filename> from the list.</para> </listitem> <listitem><para>Click <guibutton>Next</guibutton>.</para> </listitem> <listitem><para>In the first pull-down menu, select the "Node Id" of the cluster node that owns this container as <guimenuitem>node1</guimenuitem>. Select Storage Type as <menuchoice>private</menuchoice> from the second pull-down menu.</para> </listitem> <listitem><para>Enter the name <userinput>Priv1</userinput> for the Container Name.</para> </listitem> <listitem><para>Click <guibutton>Create</guibutton>. A window opens to display the outcome.</para> </listitem> <listitem><para>Commit the changes.</para> </listitem> </orderedlist> </sect2> <sect2><title>Using Ncurses</title> <para>To create the private container with the Ncurses interface, follow these steps: </para> <orderedlist><listitem><para>Scroll down the list using the <keycap>down</keycap> arrow to Create.</para> </listitem> <listitem><para>Press <keycap>Enter</keycap>. A submenu is displayed.</para> </listitem> <listitem><para>Scroll down until Container is highlighted. </para> </listitem> <listitem><para>Press <keycap>Enter</keycap>.</para> <para>A list opens of plug-ins that support container creation.</para> </listitem> <listitem><para>Scroll down with the <keycap>down</keycap> arrow and select Cluster Segment Manager by pressing <keycap>spacebar</keycap>. The plug-in you selected is marked with an "x." </para> </listitem> <listitem><para>Press <keycap>Enter</keycap>.</para> <para>The next submenu contains a list of disks that the Cluster Segment Manager finds acceptable to use for the creation of a container.</para> </listitem> <listitem><para>Use <keycap>spacebar</keycap> to select <filename>sdd</filename>, <filename>sde</filename>, and <filename>sdf</filename> from the list. The disks you select are marked with an "x."</para> </listitem> <listitem><para>Press <keycap>Enter</keycap>.</para> </listitem> <listitem><para>On the Create Storage Container - Configuration Options menu, press <keycap>spacebar</keycap> on the Node Id, which will provide a list of nodes to select from.</para> </listitem> <listitem><para>Press <keycap>spacebar</keycap> on the node <filename>node1</filename> and press <keycap>Enter</keycap>.</para> </listitem> <listitem><para>Scroll down with the <keycap>down</keycap> arrow and press <keycap>spacebar</keycap> on the Storage Type. A list of storage types opens.</para> </listitem> <listitem><para>Scroll down with the <keycap>down</keycap> arrow to <guimenuitem>private entry</guimenuitem> and press <keycap>spacebar</keycap>.</para> </listitem> <listitem><para>Press <keycap>Enter</keycap>.</para> </listitem> <listitem><para>Scroll down with the <keycap>down</keycap> arrow to <guimenuitem>Container Name</guimenuitem> and press <keycap>spacebar</keycap>.</para> <para>The Change Option Value menu opens and asks for the Container Name. Type in the name of the container as <userinput>Priv1</userinput>, and press <keycap>Enter</keycap>.</para> </listitem> <listitem><para>Press <keycap>Enter</keycap> to complete the operation.</para> </listitem> </orderedlist> </sect2> <sect2><title>Using the CLI</title> <para>An operation to create a cluster container with the CLI takes three parameters: the name of the container, the type of the container, and the nodeid to which the container belongs. On the CLI, type the following command to create the private container <filename>Priv1</filename>:</para> <programlisting>create: container,CSM={name="Priv1",type="private",nodeid="node1"},sdd,sde,sdf</programlisting> </sect2> </sect1> <sect1><title>Example: Create a shared cluster container</title> <para>This sections tells how to create a Sample Shared Container with EVMS and provides instructions to help you complete the following task:</para> <blockquote><example><title>Create a shared cluster container</title> <para>Given a system with three available shared disks (<filename>sdd</filename>, <filename>sde</filename>, and <filename>sdf</filename>), use the EVMS Cluster Segment Manager to combine these disk drives into a shared container called <filename>Shar1</filename>. </para> </example> </blockquote> <sect2><title>Using the EVMS GUI</title> <para>To create a shared cluster container with the EVMS GUI, follow these steps:</para> <orderedlist> <listitem><para>Select <menuchoice><guimenu>Actions</guimenu><guimenuitem>Create</guimenuitem> <guimenuitem>Container</guimenuitem> </menuchoice> to see a list of plug-ins that support container creation. </para> </listitem> <listitem><para>Select the <guimenuitem>Cluster Segment Manager</guimenuitem>.</para> </listitem> <listitem><para>Click <guibutton>Next</guibutton>.</para> <para>The next dialog window contains a list of storage objects that the CSM can use to create a container.</para> </listitem> <listitem><para>Select <filename>sdd</filename>, <filename>sde</filename>, and <filename>sdf</filename> from the list.</para> </listitem> <listitem><para>Click <guibutton>Next</guibutton>.</para> </listitem> <listitem><para>You do not need to change the "Node Id" field. Select Storage Type as <menuchoice>shared</menuchoice> from the second pull-down menu.</para> </listitem> <listitem><para>Enter the name <userinput>Shar1</userinput> for the Container Name.</para> </listitem> <listitem><para>Click <guibutton>Create</guibutton>. A window opens to display the outcome.</para> </listitem> <listitem><para>Commit the changes.</para> </listitem> <listitem><para>Run <command>evms_activate</command> on each of the cluster nodes so that the nodes discover the volume. This process will be automated in future releases of EVMS.</para></listitem> </orderedlist> </sect2> <sect2><title>Using Ncurses</title> <para>To create a shared cluster contained with the Ncurses interface, follow these steps:</para> <orderedlist><listitem><para>Scroll down the list using the <keycap>down</keycap> arrow to Create.</para> </listitem> <listitem><para>Press <keycap>Enter</keycap>. A submenu is displayed.</para> </listitem> <listitem><para>Scroll down until Container is highlighted. </para> </listitem> <listitem><para>Press <keycap>Enter</keycap>.</para> <para>A list opens of plug-ins that support container creation.</para> </listitem> <listitem><para>Scroll down with the <keycap>down</keycap> arrow and select Cluster Segment Manager by pressing <keycap>spacebar</keycap>. The plug-in you selected is marked with an "x." </para> </listitem> <listitem><para>Press <keycap>Enter</keycap>.</para> <para>The next submenu contains a list of disks that the Cluster Segment Manager finds acceptable to use for the creation of a container.</para> </listitem> <listitem><para>Use <keycap>spacebar</keycap> to select <filename>sdd</filename>, <filename>sde</filename>, and <filename>sdf</filename> from the list. The disks you select are marked with an "x."</para> </listitem> <listitem><para>Press <keycap>Enter</keycap>.</para> </listitem> <listitem><para>The Create Storage Container - Configuration Options menu open; ignore the "Node Id" menu.</para> </listitem> <listitem><para>Scroll down with the <keycap>down</keycap> arrow and press <keycap>spacebar</keycap> on the Storage Type. A list of storage types opens.</para> </listitem> <listitem><para>Scroll down with the <keycap>down</keycap> arrow to <guimenuitem>shared entry</guimenuitem> and press <keycap>spacebar</keycap>.</para> </listitem> <listitem><para>Press <keycap>Enter</keycap>.</para> </listitem> <listitem><para>Scroll down with the <keycap>down</keycap> arrow to <guimenuitem>Container Name</guimenuitem> and press <keycap>spacebar</keycap>.</para> <para>The Change Option Value menu opens and asks for the Container Name. Type in the name of the container as <userinput>Shar1</userinput>, and press <keycap>Enter</keycap>.</para> </listitem> <listitem><para>Press <keycap>Enter</keycap> to complete the operation.</para> </listitem> </orderedlist> </sect2> <sect2><title>Using the CLI</title> <para>Execute the following command at the CLI prompt to create a shared container <filename>Shar1</filename>:</para> <programlisting>create: container,CSM={name="Shar1",type="shared"},sdd,sde,sdf</programlisting> </sect2> </sect1> <sect1><title>Example: Convert a private container to a shared container</title> <para>This section tells how to convert a sample private container to a shared container and provides instructions for completing the following task:</para> <note><title>NOTE</title> <para>Exercise caution while performing this operation. Ensure that no application is using the volumes on the container on any node of the cluster.</para></note> <blockquote><example><title>Convert a private container to shared</title> <para>Given a system with a private storage container <filename>Priv1</filename> owned by <filename>evms1</filename>, convert <filename>Priv1</filename> to a shared storage container with the same name.</para> </example> </blockquote> <sect2><title>Using the EVMS GUI</title> <para>Follow these steps to convert a private cluster container to a shared cluster container with the EVMU GUI:</para> <orderedlist> <listitem><para>Select <menuchoice><guimenu>Actions</guimenu><guimenuitem>Modify</guimenuitem><guimenuitem>Container</guimenuitem></menuchoice> to see a list of containers.</para> </listitem> <listitem><para>Select the container <guimenuitem>csm/Priv1</guimenuitem> and press <keycap>Next</keycap>.</para> <para>A Modify Properties dialog box opens.</para> </listitem> <listitem><para>Change "Type Field" to "shared" and click <keycap>Modify</keycap>.</para> <para>A window opens that displays the outcome.</para> </listitem> <listitem><para>Commit the changes.</para> </listitem> <listitem><para>Run <command>evms_activate</command> on all the cluster nodes so that the nodes discover all the volumes on the <filename>csm/Priv1</filename> container. This process will be automated in a future release of EVMS.</para></listitem> </orderedlist> </sect2> <sect2><title>Using Ncurses</title> <para>Follow these steps to convert a private cluster container to a shared cluster container with the Ncurses interface:</para> <orderedlist><listitem><para>Scroll down the list using the <keycap>down</keycap> arrow to <guimenuitem>Modify</guimenuitem>.</para> </listitem> <listitem><para>Press <keycap>Enter</keycap>. A submenu is displayed.</para> </listitem> <listitem><para>Scroll down until <guimenuitem>Container</guimenuitem> is highlighted. </para> </listitem> <listitem><para>Press <keycap>Enter</keycap>.</para> <para>The Modify Container Properties dialog opens. Select the container <filename>csm/Priv1</filename> by pressing <keycap>spacebar</keycap>. The container you selected is marked with an "x."</para> </listitem> <listitem><para>Press <keycap>Enter</keycap>.</para> </listitem> <listitem><para>Use <keycap>spacebar</keycap> to select <filename>sdd</filename>, <filename>sde</filename>, and <filename>sdf</filename> from the list. The disks you select are marked with an "x."</para> </listitem> <listitem><para>Press <keycap>Enter</keycap>.</para> </listitem> <listitem><para>The Modify Container Properties - Configuration Options" dialog opens. Scroll down with the <keycap>down</keycap> arrow and press <keycap>spacebar</keycap> on the "Type field".</para> </listitem> <listitem><para>Press <keycap>spacebar</keycap>.</para> </listitem> <listitem><para>The Change Option Value dialog opens. Type <userinput>shared</userinput> and press <keycap>Enter</keycap>.</para> <para>The changed value is now displays in the Modify Container Properties - Configuration Options dialog.</para> </listitem> <listitem><para>Press <keycap>Enter</keycap>.</para> <para>The outcome of the command is displayed at the bottom of the screen.</para> </listitem> <listitem><para>Save the changes by clicking <keycap>Save</keycap> in the <menuchoice>Actions</menuchoice> pulldown menu.</para> </listitem> <listitem><para>Run <command>evms_activate</command> on all the cluster nodes so that the nodes discover all the volumes on the <filename>csm/Priv1</filename> container. This process will be automated in a future release of EVMS.</para></listitem> </orderedlist> </sect2> <sect2><title>Using the CLI</title> <para>The <command>modify</command> command modifies the properties of a container. The first argument of the command is the object to modify, followed by its new properties. The command to convert the private container to a shared container in the example is:</para> <programlisting>modify: csm/Priv1,type=shared</programlisting> <para>Run <command>evms_activate</command> on all the cluster nodes so that the nodes discover all the volumes on the <filename>csm/Priv1</filename> container. This process will be automated in a future release of EVMS.</para> </sect2> </sect1> <sect1><title>Example: Convert a shared container to a private container</title> <para>This section tells how to convert a sample shared container to a private container and provides instructions for completing the following task:</para> <note><title>NOTE</title> <para>Exercise caution while performing this operation. Ensure that no application is using the volumes on the container on any node of the cluster.</para></note> <blockquote><example><title>Convert a shared container to private</title> <para>Given a system with a shared storage container <filename>Shar1</filename>, convert <filename>Shar1</filename> to a private storage container owned by node <filename>node1</filename> (where <filename>node1</filename> is the nodeid of one of the cluster nodes).</para> </example> </blockquote> <sect2><title>Using the EVMS GUI</title> <para>Follow these steps to convert a shared cluster container to a private cluster container with the EVMU GUI:</para> <orderedlist> <listitem><para>Select <menuchoice><guimenu>Actions</guimenu><guimenuitem>Modify</guimenuitem><guimenuitem>Container</guimenuitem></menuchoice> to see a list of containers.</para> </listitem> <listitem><para>Select the container <guimenuitem>csm/Shar1</guimenuitem> and press <keycap>Next</keycap>.</para> <para>A Modify Properties dialog opens.</para> </listitem> <listitem><para>Change "Type Field" to "private" and the "NodeID" field to <filename>node1</filename>. Click <keycap>Modify</keycap>.</para> <para>A window opens that displays the outcome.</para> </listitem> <listitem><para>Commit the changes.</para> </listitem> <listitem><para>Run <command>evms_activate</command> on the other nodes to deactivate the volumes of the shared container on the other nodes. This process will be automated in a future release of EVMS.</para></listitem> </orderedlist> </sect2> <sect2><title>Using Ncurses</title> <para>Follow these steps to convert a shared cluster container to a private cluster container with the Ncurses interface:</para> <orderedlist><listitem><para>Scroll down the list using the <keycap>down</keycap> arrow to <guimenuitem>Modify</guimenuitem>.</para> </listitem> <listitem><para>Press <keycap>Enter</keycap>. A submenu is displayed.</para> </listitem> <listitem><para>Scroll down until <guimenuitem>Container</guimenuitem> is highlighted. </para> </listitem> <listitem><para>Press <keycap>Enter</keycap>.</para> <para>The Modify Container Properties dialog opens. Select the container <filename>csm/Shar1</filename> by pressing <keycap>spacebar</keycap>. The container you selected is marked with an "x."</para> </listitem> <listitem><para>Press <keycap>Enter</keycap>.</para> </listitem> <listitem><para>The Modify Container Properties - Configuration Options" dialog opens. Scroll down with the <keycap>down</keycap> arrow and press <keycap>spacebar</keycap> on the "Type" field.</para> </listitem> <listitem><para>Press <keycap>spacebar</keycap>.</para> </listitem> <listitem><para>The Change Option Value dialog opens. Type <userinput>private</userinput> and press <keycap>Enter</keycap>.</para> </listitem> <listitem><para>The Modify Container Properties - Configuration Options dialog opens. Scroll down the list to <guimenuitem>NodeId</guimenuitem> with the <keycap>down</keycap> arrow and press <keycap>spacebar</keycap>.</para></listitem> <listitem><para>The Change Option Value dialog opens. Enter <userinput>node1</userinput> and press <keycap>Enter</keycap>.</para></listitem> <listitem><para>The changed values now display in the Modify Container Properties - Configuration Options dialog. Press <keycap>Enter</keycap>. </para> <para>The outcome of the command is displayed at the bottom of the screen.</para> </listitem> <listitem><para>Save the changes by clickting <keycap>Save</keycap> in the <menuchoice>Actions</menuchoice> pulldown.</para></listitem> <listitem><para>Run <command>evms_activate</command> on all the cluster nodes to deactivate the volumes of the shared container on all the other nodes. This process will be automated in a future release of EVMS.</para></listitem> </orderedlist> </sect2> <sect2><title>Using the CLI</title> <para>The <command>modify</command> command modifies the properties of a container. The first argument of the command is the object to modify, followed by its new properties. The command to convert the shared container to a private container in the example is:</para> <programlisting>modify: csm/Shar1,type=private,nodeid=node1</programlisting> <para>Run <command>evms_activate</command> on all the cluster nodes to deactivate the volumes of the shared container on all the other nodes. This process will be automated in a future release of EVMS.</para> </sect2> </sect1> <sect1><title>Failover and Failback of a private container on Linux-HA</title> <para>EVMS supports the Linux-HA cluster manager in EVMS V2.0 and later; support for the RSCT cluster manager will be made available in a future release of EVMS.</para> <para><note><title>NOTE</title> <para>Ensure that <command>evms_activate</command> is called in one of the startup scripts before the heartbeat daemon starts (for example, <filename>/etc/kinit.d/heartbeat</filename>). If <command>evms_activate</command> is not called, failover might not work correctly. </para> </note></para> <para>Follow these steps to set up failover and failback of a private container:</para> <orderedlist> <listitem><para>Add an entry in <filename>/etc/ha.d/haresources</filename> for each private container to be failed over. For example, if <filename>container3</filename> and <filename>container4</filename> are to be filled over together to the same node with <filename>node1</filename> as the owning node, add the following entry to <filename>/etc/ha.d/haresources</filename>:</para> <programlisting>node1 evms_failover::container1 evms_failover::container1</programlisting> <para><filename>node1</filename> is the cluster node that owns this resource. The resource is failed over to the other node when <filename>node1</filename> dies.</para> <para>Similarly, if <filename>container3</filename> and <filename>container4</filename> are to be failed over together to the same node with <filename>node2</filename> as the owning node, then add the following entry to <filename>/etc/ha.d/haresources</filename>:</para> <programlisting>node2 evms_failover::container3 evms_failover::container4</programlisting> <para>Refer to the following source for more details on the semantics of resource groups: <ulink url="http://www.linux-ha.org/download/GettingStarted.html">http://www.linux-ha.org/download/GettingStarted.html</ulink>.</para> </listitem> <listitem><para>Validate that the <filename>/etc/ha.d</filename>, <filename>/etc/ha.cf</filename> and <filename>/etc/ha.d/haresources</filename> files are the same on all the nodes of the cluster.</para> </listitem> <listitem><para>The heartbeat cluster manager must be restarted, as follows, after the <filename>/etc/ha.d/haresources</filename> file has been changed:</para> <programlisting>/etc/init.d/heartbeat restart</programlisting> <para><note>NOTE</note> Do not add shared containers to the list of failover resources; doing so causes EVMS to respond unpredictably.</para> </listitem> </orderedlist> </sect1> <sect1><title>Remote configuration management</title> <para>EVMS supports the administration of cluster nodes by any node in the cluster. For example, storage on remote cluster node <filename>node1</filename> can be administered from cluster node <filename>node2</filename>. The following sections show how to set up remote administration through the various EVMS user interfaces.</para> <sect2><title>Using the EVMS GUI</title> <para>To designate node2 as a node administrator, enter this command:</para> <programlisting>evmsgui -n node2</programlisting> </sect2> <sect2><title>Using Ncurses</title> <para>To designate <filename>node2</filename> as a node administrator from Ncurses, follow these steps:</para> <orderedlist> <listitem><para>Go to the <guimenuitem>Setting</guimenuitem> pulldown menu.</para> </listitem> <listitem><para>Scroll down with the <keycap>down</keycap> arrow to the "Node Administered" option and press <keycap>Enter</keycap>.</para> </listitem> <listitem><para>The Administer Remote Node dialog opens. Select <filename>node2</filename> and press <keycap>spacebar</keycap>.</para> <para>The node you selected is marked with an "x."</para> </listitem> <listitem><para>Press <keycap>Enter</keycap>.</para> </listitem> <listitem><para>The "EVMS is examining your system. Please wait" dialog opens. After a while you will be switched over to the node <filename>node2</filename>.</para></listitem> </orderedlist> </sect2> <sect2><title>Using the CLI</title> <para>To designate <filename>node2</filename> as a node administrator from the CLI, issue this command:</para> <programlisting>evms -n node2</programlisting> </sect2> </sect1> </chapter> --- view_evms.png DELETED --- --- evms_config.png DELETED --- Index: appx-drivelink.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/appx-drivelink.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- appx-drivelink.xml 16 Feb 2005 17:06:46 -0000 1.1 +++ appx-drivelink.xml 16 Feb 2005 17:13:52 -0000 1.2 @@ -1,7 +1,10 @@ -<appendix id="appxdrivelink"><title>The Drive link plug-in</title> -<para>The EVMS drive link plug-in is an aggregating plug-in. -It is used to combine storage objects into a singular object. + + +<appendix id="appxdrivelink"><title>The drive link plug-in</title> + +<para>The EVMS drive link plug-in is an aggregating plug-in that +combines storage objects into a single object. The resulting drive link storage object can be made into a compatibility volume, EVMS volume, or even be consumed by higher-level storage objects. @@ -13,78 +16,73 @@ <para>The drive link plug-in consumes storage objects, called link objects, producing a larger drive link object whose address space spans the link objects. -the drive link plug-in knows how to assemble the link objects so as to +The drive link plug-in knows how to assemble the link objects so as to create the exact same address space every time. The information required to do this is kept on each link child as persistent -drive link metadata. +drive-link metadata. During discovery, the drive link plug-in inspects each known storage object for this metadata. The presence of this metadata identifies the storage object as a link object. The information contained in the metadata is sufficient to:</para> - -<orderedlist> +<itemizedlist> <listitem> -<para>Identify the link object itself</para> +<para>Identify the link object itself.</para> </listitem> <listitem> -<para>Identify the drive link storage object that the link object belongs to +<para>Identify the drive link storage object that the link object belongs to. </para> </listitem> <listitem> -<para>Identify all link objects belonging to the drive link storage +<para>Identify all link objects belonging to the drive link storage. object</para> </listitem> <listitem> -<para>Establish the order in which to combine the child link objects</para> +<para>Establish the order in which to combine the child link objects.</para> </listitem> -</orderedlist> +</itemizedlist> + <para>If any link objects are missing at the conclusion of the discovery -process, the drive link storage object will contain gaps where the missing +process, the drive link storage object contains gaps where the missing link objects occur. In such cases, the drive link plug-in attempts to fill in the gap with a substitute link object and construct the drive link storage object in -READ-ONLY mode. -This allows for recovery action. -The missing object might reside on removable storage that has been removed. -Or perhaps a lower layer plug-in failed to produce the missing object. -Whatever the reason, by providing a READ-ONLY drive link storage object and -logging errors, the user can take actions to recover the drive link. +read-only mode, which allows for recovery action. +The missing object might reside on removable storage that has been removed or +perhaps a lower layer plug-in failed to produce the missing object. +Whatever the reason, a read-only drive link storage object, together +logging errors, help you takea the appropriate actions to recover the drive link. </para> </sect1> <sect1 id="createlink"><title>Creating a drive link</title> <para> -The drive link plug-in provides a list of objects that it finds -acceptable for creating a drive link object. -First, when you choose to create an EVMS storage object, and then choose +The drive link plug-in provides a list of acceptable objects from which it can create a drive link object. +When you create an EVMS storage object and choose the drive link plug-in, a list of acceptable objects is provided that you simply choose from. -The ordering is implied by the order in which you pick objects from the list. -Then, providing a name for the new drive link object, the identified link +The ordering of the drive link is implied by the order in which you pick objects from the +provided list. +After you provide a name for the drive link, the identified link objects are consumed and the new drive link object is produced. There are no create options. </para> </sect1> -<sect1 id="expandpartitions"><title>Expanding partitions</title> +<sect1 id="dlexpandpart"><title>Expanding partitions</title> <para> -Because a drive link is an aggregating object, it is easily expanded -by adding an additional storage object to the end of the drive link. -The drive link can also be expanded by expanding the last storage object -in the drive link, if possible. A drive link can therefore be expanded by: -</para> +Drive links are aggregating objects that can be expanded in the following ways:</para> <itemizedlist> <listitem> <para> -adding an additional storage object at the end of the drive link +By adding an additional storage object to the end of the drive link. </para> </listitem> <listitem> <para> -expanding the last storage object in the drive link +Bexpanding the last storage object in the drive link. </para> </listitem> </itemizedlist> @@ -97,10 +95,10 @@ </para> <para> -If the expansion point is a link object, then the expansion is done by the -plug-in that produced the link object. +If the expansion point is a link object, then the +plug-in that produced the link object does the expansion. For example, if the link object was a segment, then the segment manager -plug-in that produced the storage object would expand the link object. +plug-in that produced the storage object expands the link object. Afterward, the drive link storage object is resized to reflect the expansion. </para> <para> @@ -109,19 +107,22 @@ </sect1> -<sect1 id="shrinkdrivelink"><title>Shrinking a drive link</title> +<sect1 id="dlshrink"><title>Shrinking a drive link</title> <para> -You can shrink a drive link by either removing link objects from the end -of the drive link or by shrinking the last storage object in the drive link. -With just one exception, therefore, shrinking is very much like expanding. -The except is that when shrinking by removing link objects, you can only -remove link objects from the end of the drive link. -Removing a link object anywhere else produces a gap in the drive link -address space, similar to missing link objects. +Drive links can be shrunk in the following ways: +<itemizedlist> +<listitem><para>By removing link objects from the end of the drive link.</para> +</listitem> +<listitem><para>By shrinking the last storage object in the drive link.</para> +</listitem> +</itemizedlist> +</para> +<para>Removing +a link object from anywhere other than the end of the drive link produces a gap in the drive link address +space, similar to the gap produced by missing link objects. The drive link plug-in attempts to orchestrate the shrinking of a drive-link storage object by only listing the last link object. -If you select this object, the drive link plug-in then lists the next -to last link object, and so forth, moving backward through the link +If you select this object, the drive link plug-in then lists the next-to-last link object, and so forth, moving backward through the link objects to satisfy the shrink command. </para> <para> @@ -129,15 +130,14 @@ </para> </sect1> -<sect1 id="deletedrivelink"><title>Deleting a drive link</title> +<sect1 id="dldelete"><title>Deleting a drive link</title> <para> -You can delete an existing drive link as long as it is not currently a +A drive link can be deleted as long as it is not currently a compatibility volume, an EVMS volume, or consumed by another EVMS plug-in. </para> <para> -No options are available for deleting drive link storage objects. +No options are available for deleting a drive link storage object. </para> </sect1> -</appendix> - +</appendix> \ No newline at end of file --- linux_config.png DELETED --- Index: appx-snap.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/appx-snap.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- appx-snap.xml 16 Feb 2005 17:06:46 -0000 1.1 +++ appx-snap.xml 16 Feb 2005 17:13:52 -0000 1.2 @@ -1,4 +1,7 @@ -<appendix id="appxsnap"><title>The snapshot plug-in</title> + + + +<appendix id="appxsnapplug"><title>The snapshot plug-in</title> <para>A snapshot represents a frozen image of a volume. The source of a snapshot is called an "original." When a snapshot is created, it looks exactly like the original @@ -9,7 +12,7 @@ backup, which can be a significant inconvenience to users. With snapshots, the volume can be kept online. A snapshot of the volume is created and the backup is taken from the snapshot, while the original remains in active use.</para> -<sect1 id="cando"><title>How snapshotting is implemented</title> +<sect1 id="snapimp"><title>How snapshotting is implemented</title> <para>A snapshot represents a copy of its original volume "frozen" at some point in time. Instead of actually copying all the data from the original to the snapshot, a portion of data is copied only when that portion is being modified on the original. @@ -26,7 +29,7 @@ If the chunk has not been saved, the data is retrieved from the original.</para> </sect1> -<sect1 id="uis"><title>Creating and activating snapshot objects</title> +<sect1 id="snapcreateact"><title>Creating and activating snapshot objects</title> <para>Creating and activating a snapshot is a two-step process. The first step is to create the snapshot object. The snapshot object specifies where the saved data will @@ -44,12 +47,12 @@ <para>Base the size of the snapshot object on the amount of activity that is likely to take place on the original during the lifetime of the snapshot. The more changes that occur on the original and the longer the snapshot is expected to remain active, the larger the snapshot -should be. Clearly, determining this calculation is not simple and requires trial and error to determine the correct snapshot object sizes to use for a particular situation. The goal is +should be. Clearly, determining this calculation is not simple and requires trial and error to determine the correct snapshot object size to use for a particular situation. The goal is to create a snapshot object large enough to prevent the shapshot from being deactivated if it fills up, yet small enough to not waste disk space. If the snapshot object is the same size as the original volume (actually, a little larger, to account for the snapshot mapping tables), the snapshot is never deactivated.</para> -<para>Chapter 12 tells how to create snapshots. The following options are available for +<para><xref linkend="evmscreatesnap"/> tells how to create snapshots. The following options are available for creating snapshot objects through the CLI:</para> <variablelist> @@ -95,7 +98,7 @@ <sect2><title>Reinitializing a snapshot</title> <para>Snapshots can be reinitialized, which causes all of the saved data to be erased and starts the snapshot from the current point in time. A reinitialized snapshot has the same -oriignal, chunk size, and writeable flags as the original snapshot.</para> +original, chunk size, and writeable flags as the original snapshot.</para> <para>To reinitialize a snapshot, delete the EVMS volume from the snapshot without deleting the snapshot object. Then create a new EVMS volume from the snapshot object. </para> @@ -133,5 +136,4 @@ </sect1> -</appendix> - +</appendix> \ No newline at end of file --- NEW FILE: appx-jfs.xml --- <appendix id="jfsfsim"><title>JFS file system interface module</title> <para> The JFS FSIM lets EVMS users create and manage JFS file systems from within the EVMS interfaces. In order to use the JFS FSIM, version 1.0.9 or later of the JFS utilities must be installed on your system. The latest version of JFS can be found at <ulink url="http://oss.software.ibm.com/jfs/">http://oss.software.ibm.com/jfs/</ulink>. </para> <sect1 id="createjfsfsim"><title>Creating JFS file systems</title> <para> JFS file systems can be created with <command>mkfs</command> on any EVMS or compatibility volume (at least 16 MB in size) that does not already have a file system. The following options are available for creating JFS file systems:</para> <variablelist> <varlistentry><term>badblocks</term> <listitem> <para>Perform a read-only check for bad blocks on the volume before creating the file system. The default is false.</para> </listitem> </varlistentry> <varlistentry><term>caseinsensitive</term> <listitem> <para>Mark the file system as case-insensitive (for OS/2 compatibility). The default is false.</para> </listitem> </varlistentry> <varlistentry><term>vollabel</term> <listitem> <para>Specify a volume label for the file system. The default is none. </para> </listitem> </varlistentry> <varlistentry><term>journalvol</term> <listitem> <para>Specify the volume to use for an external journal. This option is only available with version 1.0.20 or later of the JFS utilities. The default is none. </para> </listitem> </varlistentry> <varlistentry><term>logsize</term> <listitem> <para> Specify the inline log size (in MB). This option is only available if the journalvol option is not set. The default is 0.4% of the size of the volume up to 32 MB. </para> </listitem> </varlistentry> </variablelist> </sect1> <sect1 id="check... [truncated message content] |