Menu
▾
▴
[Evms-cvs-commits] Documentation/user_guide addremseg-ug.xml,NONE,1.1 appx-opengfs.xml,NONE,1.1 EVMSUG.xml,1.3,1.4 appx-csm.xml,1.2,1.3 appx-ext23.xml,1.1,1.2 appx-lvm.xml,1.3,1.4 clusterops-ug.xml,1.2,1.3 convertto-ug.xml,1.3,1.4 createvol-ug.xml,1.3,1.4 debuglog-ug.xml,1.2,1.3 expandshrink.xml,1.2,1.3 fsimops-ug.xml,1.3,1.4 over-ug.xml,1.3,1.4 pref-ug.xml,1.3,1.4 assignseg-ug.xml,1.3,NONE
|
From: Kevin C. <kc...@us...> - 2005-02-16 17:42:25
|
Update of /cvsroot/evms/Documentation/user_guide In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23746 Modified Files: EVMSUG.xml appx-csm.xml appx-ext23.xml appx-lvm.xml clusterops-ug.xml convertto-ug.xml createvol-ug.xml debuglog-ug.xml expandshrink.xml fsimops-ug.xml over-ug.xml pref-ug.xml Added Files: addremseg-ug.xml appx-opengfs.xml Removed Files: assignseg-ug.xml Log Message: Update for the EVMS User-Guide for version 2.3. Index: fsimops-ug.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/fsimops-ug.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -r1.3 -r1.4 --- fsimops-ug.xml 16 Feb 2005 17:33:19 -0000 1.3 +++ fsimops-ug.xml 16 Feb 2005 17:41:17 -0000 1.4 @@ -1,10 +1,10 @@ <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> +<para>This chapter discusses the six 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> <sect1 id="FSIMsuppevms"><title>The FSIMs supported by EVMS</title> -<para>EVMS currently ships with five FSIMs. These file system modules allow EVMS to interact with file system utilities such as <command>mkfs</command> and <command>fsck</command>. Additionally, the FSIMs ensure that EVMS safely performs operations, such as expanding and shrinking file systems, by coordinating these actions with the file system. </para> +<para>EVMS currently ships with six FSIMs. These file system modules allow EVMS to interact with file system utilities such as <command>mkfs</command> and <command>fsck</command>. Additionally, the FSIMs ensure that EVMS safely performs operations, such as expanding and shrinking file systems, by coordinating these actions with the file system. </para> <para>You can invoke operations such as <command>mkfs</command> and <command>fsck</command> through the various EVMS user interfaces. Any actions you initiate through an FSIM are not committed to disk until the changes are saved in the user interface. Later in this chapter we provide examples of creating a new file system and coordinating file system checks through the EVMS GUI, Ncurses, and command-line interfaces.</para> <para>The FSIMs supported by EVMS are:</para> @@ -14,6 +14,7 @@ <listitem><para>ReiserFS</para></listitem> <listitem><para>Ext2/3</para></listitem> <listitem><para>SWAPFS</para></listitem> +<listitem><para>OpenGFS</para></listitem> </itemizedlist> <sect2 id="fsimjfs"><title>JFS</title> @@ -53,7 +54,7 @@ expansion and offline shrinkage. You need version 3.x.1a or higher of the ReiserFS utilities for use with the EVMS FSIM modules. You can download the ReiserFS utilities from <ulink url="http://www.namesys.com">The Naming -System Venture (Namesys) </ulink> web site. +System Venture (Namesys) </ulink> Web site. </para> <para> @@ -86,6 +87,20 @@ </para> </sect2> +<sect2 id="fsimopengfs"><title>OpenGFS</title> +<para> +The OpenGFS module supports the OpenGFS clustered journaling file system. +This module supports <command>mkfs</command>, <command>unmkfs</command>, +<command>fsck</command>, and online expansion. +You need the OpenGFS utilities for use with the EVMS FSIM module. +You can download the OpenGFS utilities from the +<ulink url="http://sourceforge.net/projects/opengfs">OpenGFS project on SourceForge</ulink>. +</para> + +<para> +For more information on the OpenGFS FSIM, refer to <xref linkend="gfsfsim"></xref>. +</para> +</sect2> </sect1> <sect1 id="fsimmkfs"><title>Example: add a file system to a volume</title> --- NEW FILE: addremseg-ug.xml --- <chapter id="evmsassignseg"><title>Adding and removing a segment manager</title> <para> This chapter discusses when to use a segment manager, what the different types of segment managers are, how to add a segment manager to a disk, and how to remove a segment manager. </para> <sect1 id="whenassign"><title>When to add a segment manager</title> <para>Adding a segment manager to a disk allows the disk to be subdivided into smaller storage objects called disk segments. The <command>add</command> command causes a segment manager to create appropriate metadata and expose freespace that the segment manager finds on the disk. You need to add segment managers when you have a new disk or when you are switching from one partitioning scheme to another. </para> <para>EVMS displays disk segments as the following types: </para> <itemizedlist><listitem><para>Data: a set of contiguous sectors that has been allocated from a disk and can be used to construct a volume or object.</para></listitem> <listitem><para>Freespace: a set of contiguous sectors that are unallocated or not in use. Freespace can be used to create a segment.</para></listitem> <listitem><para>Metadata: a set of contiguous sectors that contain information needed by the segment manager.</para></listitem> </itemizedlist> </sect1> <sect1 id="smtypes"><title>Types of segment managers</title> <para>There are seven types of segment managers in EVMS: DOS, GPT, S/390, Cluster, BSD, MAC, and BBR. </para> <sect2 id="defaultseg"><title>DOS Segment Manager</title> <para>The most commonly used segment manager is the DOS Segment Manager. This plug-in provides support for traditional DOS disk partitioning. The DOS Segment Manager also recognizes and supports the following variations of the DOS partitioning scheme: <itemizedlist><listitem><para>OS/2: an OS/2 disk has additional metadata sectors that contain information needed to reconstruct disk segments.</para></listitem> <listitem><para>Embedded partitions: support for BSD, SolarisX86, and UnixWare is sometimes found embedded in primary DOS partitions. The DOS Segment Manager recognizes and supports these slices as disk segments.</para></listitem></itemizedlist></para> </sect2> <sect2 id="gptseg"><title>GUID Partitioning Table (GPT) Segment Manager</title> <para>The GUID Partitioning Table (GPT) Segment Manager handles the new GPT partitioning scheme on IA-64 machines. The Intel <citetitle>Extensible Firmware Interface Specification</citetitle> requires that firmware be able to discover partitions and produce logical devices that correspond to disk partitions. The partitioning scheme described in the specification is called GPT due to the extensive use of Globally Unique Identifier (GUID) tagging. GUID is a 128 bit long identifier, also referred to as a Universally Unique Identifier (UUID). As described in the Intel <citetitle>Wired For Management Baseline Specification</citetitle>, a GUID is a combination of time and space fields that produce an identifier that is unique across an entire UUID space. These identifiers are used extensively on GPT partitioned disks for tagging entire disks and individual partitions. GPT partitioned disks serve several functions, such as:</para> <itemizedlist> <listitem><para>keeping a primary and backup copy of metadata</para> </listitem> <listitem><para>replacing msdos partition nesting by allowing many partitions</para> </listitem> <listitem><para>using 64 bit logical block addressing</para> </listitem> <listitem><para>tagging partitions and disks with GUID descriptors</para> </listitem> </itemizedlist> <para>The GPT Segment Manager scales better to large disks. It provides more redundancy with added reliability and uses unique names. However, the GPT Segment Manager is not compatible with DOS, OS/2, or Windows®. </para></sect2> <sect2 id="s390sm"><title>S/390 Segment Manager</title> <para>The S/390 Segment Manager is used exclusively on System/390 mainframes. The S/390 Segment Manager has the ability to recognize various disk layouts found on an S/390 machine, and provide disk segment support for this architecture. The two most common disk layouts are Linux Disk Layout (LDL) and Common Disk Layout (CDL). </para> <para>The principle difference between LDL and CDL is that an LDL disk cannot be further subdivided. An LDL disk will produce a single metadata disk segment and a single data disk segment. There is no freespace on an LDL disk, and you cannot delete or re-size the data segment. A CDL disk can be subdivided into multiple data disk segments because it contains metadata that is missing from an LDL disk, specifically the Volume Table of Contents (vtoc) information.</para> <para>The S/390 Segment Manager is the only segment manager plug-in capable of understanding the unique S/390 disk layouts. The S/390 Segment Manager cannot be added or removed from a disk. </para></sect2> <sect2><title>Cluster segment manager</title> <para>The cluster segment manager (CSM) supports high availability clusters. When the CSM is added to a shared storage disk, it writes metadata on the disk that:</para> <itemizedlist> <listitem><para>provides a unique disk ID (guid)</para></listitem> <listitem><para>names the EVMS container the disk will reside within</para></listitem> <listitem><para>specifies the cluster node (nodeid) that owns the disk</para></listitem> <listitem><para>specifies the cluster (clusterid)</para></listitem> </itemizedlist> <para>This metadata allows the CSM to build containers for supporting failover situations. It does so by constructing an EVMS container object that consumes all shared disks discovered by the CSM and belonging to the same container. These shared storage disks are consumed by the container and a single data segment is produced by the container for each consumed disk. A failover of the EVMS resource is accomplished by simply reassigning the CSM container to the standby cluster node and having that node re-run its discovery process.</para> <para>Adding disks to CSM containers implies that only disk storage objects are acceptable to the CSM. This is an important aspect of the CSM. Other segment managers can be embedded within storage objects and used to further subdivide them. However, the CSM cannot add any other kind of storage object to a CSM container because the container is meant to be a disk group and the entire disk group is reassigned during a failover. So, the CSM only accepts disks when constructing containers. This is important to remember when adding the CSM to a disk. If you choose <command>Add</command> and the CSM does not appear in the list of selectable plug-ins when you know you have a disk, you should look at the Volume list and see if the disk has already been listed as a compatibility volume. If you simply delete the volume, the disk will become an available object and the CSM will then appear in the list of plug-ins because it now has an available disk that it can add to a container.</para> </sect2> <sect2><title>BSD segment manager</title> <para>BSD refers to the Berkeley Software Distribution UNIX® operating system. The EVMS BSD segment manager is responsible for recognizing and producing EVMS segment storage objects that map BSD partitions. A BSD disk may have a slice table in the very first sector on the disk for compatibility purposes with other operating systems. For example, a DOS slice table might be found in the usual MBR sector. The BSD disk would then be found within a disk slice that is located using the compatibility slice table. However, BSD has no need for the slice table and can fully dedicate the disk to itself by placing the disk label in the very first sector. This is called a "fully dedicated disk" because BSD uses the entire disk and does not provide a compatibility slice table. The BSD segment manager recognizes such "fully dedicated disks" and provides mappings for the BSD partitions.</para> </sect2> <sect2><title>MAC segment manager</title> <para>Apple-partitioned disks use a disk label that is recognized by the MAC segment manager. The MAC segment manager recognizes the disk label during discovery and creates EVMS segments to map the MacOS disk partitions.</para> </sect2> <sect2><title>BBR segment manager</title> <para>The bad block replacement (BBR) segment manager enhances the reliability of a disk by remapping bad storage blocks. When BBR is added to a disk, it writes metadata on the disk that:</para> <itemizedlist> <listitem><para>reserves replacement blocks</para></listitem> <listitem><para>maps bad blocks to reserved blocks</para></listitem> </itemizedlist> <para>Bad blocks occur when an I/O error is detected for a write operation. When this happens, I/O normally fails and the failure code is returned to the calling program code. BBR detects failed write operations and remaps the I/O to a reserved block on the disk. Afterward, BBR restarts the I/O using the reserve block.</para> <para>Every block of storage has an address, called a logical block address, or LBA. When BBR is added to a disk, it provides two critical functions: remap and recovery. When an I/O operation is sent to disk, BBR inspects the LBA in the I/O command to see if the LBA has been remapped to a reserve block due to some earlier I/O error. If BBR finds a mapping between the LBA and a reserve block, it updates the I/O command with the LBA of the reserve block before sending it on to the disk. Recovery occurs when BBR detects an I/O error and remaps the bad block to a reserve block. The new LBA mapping is saved in BBR metadata so that subsequent I/O to the LBA can be remapped.</para> </sect2> </sect1> <sect1 id="assignsegex"><title>Adding a segment manager to an existing disk</title> <para>When you add a segment manager to a disk, the segment manager needs to change the basic layout of the disk. This change means that some sectors are reserved for metadata and the remaining sectors are made available for creating data disk segments. Metadata sectors are written to disk to save information needed by the segment manager; previous information found on the disk is lost. Before adding a segment manager to an existing disk, you must remove any existing volume management structures, including any previous segment manager.</para> </sect1> <sect1 id="assignsegnew"><title>Adding a segment manager to a new disk</title> <para>When a new disk is added to a system, the disk usually contains no data and has not been partitioned. If this is the case, the disk shows up in EVMS as a compatibility volume because EVMS cannot tell if the disk is being used as a volume. To add a segment manager to the disk so that it can be subdivided into smaller disk segment objects, tell EVMS that the disk is not a compatibility volume by deleting the volume information.</para> <para>If the new disk was moved from another system, chances are good that the disk already contains metadata. If the disk does contain metadata, the disk shows up in EVMS with storage objects that were produced from the existing metadata. Deleting these objects will allow you to add a different segment manager to the disk, and you lose any old data. </para> </sect1> <sect1 id="assignex"><title>Example: add a segment manager</title> <para>This section shows how to add a segment manager with EVMS.</para> <para>EVMS initially displays the physical disks it sees as volumes. Assume that you have added a new disk to the system that EVMS sees as <filename>sde</filename>. This disk contains no data and has not been subdivided (no partitions). EVMS assumes that this disk is a compatibility volume known as <filename>/dev/evms/sde</filename>. </para> <blockquote><example><title>Add the DOS Segment Manager</title> <para>Add the DOS Segment Manager to disk <filename>sde</filename>.</para></example></blockquote> <note><title>NOTE</title> <para>In the following example, the DOS Segment Manager creates two segments on the disk: a metadata segment known as <filename>sde_mbr</filename>, and a segment to represent the available space on the drive, <filename>sde_freespace1</filename>. This freespace segment (<filename>sde_freespace1</filename>) can be divided into other segments because it represents space on the drive that is not in use.</para></note> <sect2 id="assignseggui"><title>Using the EVMS GUI</title> <para>To add the DOS Segment Manager to <filename>sde</filename>, first remove the volume, <filename>/dev/evms/sde</filename>:</para> <orderedlist> <listitem><para>Select <menuchoice><guimenu>Actions</guimenu> <guimenuitem>Delete</guimenuitem> <guimenuitem>Volume</guimenuitem></menuchoice>.</para></listitem> <listitem><para>Select <filename>/dev/evms/sde</filename>.</para></listitem> <listitem><para>Click <guibutton>Delete</guibutton>.</para></listitem> </orderedlist> <para>Alternatively, you can remove the volume through the GUI context sensitive menu:</para> <orderedlist> <listitem><para>From the <guimenuitem>Volumes tab</guimenuitem>, right click <filename>/dev/evms/sde</filename>.</para></listitem> <listitem><para>Click <guibutton>Delete</guibutton>.</para></listitem> </orderedlist> <para>After the volume is removed, add the DOS Segment Manager:</para> <orderedlist> <listitem><para>Select <menuchoice><guimenu>Actions</guimenu> <guimenuitem>Add</guimenuitem> <guimenuitem>Segment Manager to Storage Object</guimenuitem></menuchoice>.</para></listitem> <listitem><para>Select <guilabel>DOS Segment Manager</guilabel>.</para></listitem> <listitem><para>Click <guibutton>Next</guibutton>.</para></listitem> <listitem><para>Select <guilabel>sde</guilabel></para></listitem> <listitem><para>Click <guibutton>Add</guibutton></para></listitem> </orderedlist> </sect2> <sect2 id="assignsegncur"><title>Using Ncurses</title> <para>To add the DOS Segment Manager to <filename>sde</filename>, first remove the volume <filename>/dev/evms/sde</filename>:</para> <orderedlist> <listitem><para>Select <menuchoice><guimenu>Actions</guimenu><guimenuitem>Delete</guimenuitem> <guimenuitem>Segment Manager to Storage Object</guimenuitem></menuchoice>.</para></listitem> <listitem><para>Select <filename>/dev/evms/sde</filename>.</para></listitem> <listitem><para>Activate <guibutton>Delete</guibutton>.</para></listitem> </orderedlist> <para>Alternatively, you can remove the volume through the context sensitive menu:</para> <orderedlist> <listitem><para>From the Logical Volumes view, press <keycap>Enter</keycap> on <filename>/dev/evms/sde</filename>.</para> </listitem> <listitem><para>Activate <guibutton>Delete</guibutton>.</para> </listitem> </orderedlist> <para>After the volume is removed, add the DOS Segment Manager:</para> <orderedlist> <listitem><para>Select <menuchoice><guimenu>Actions</guimenu><guimenuitem>Add</guimenuitem> <guimenuitem>Segment Manager to Storage Object</guimenuitem></menuchoice></para></listitem> <listitem><para>Select <guilabel>DOS Segment Manager</guilabel>.</para></listitem> <listitem><para>Activate <guibutton>Next</guibutton>.</para></listitem> <listitem><para>Select <guilabel>sde</guilabel>. </para></listitem> <listitem><para>Activate <guibutton>Add</guibutton>.</para></listitem> </orderedlist> </sect2> <sect2 id="assignsegcli"><title>Using the CLI</title> <para>To add the DOS Segment Manager to sde, first tell EVMS that this disk is not a volume and is available for use:</para> <programlisting>Delete:/dev/evms/sde</programlisting> <para>Next, add the DOS Segment Manager to sde by typing the following:</para> <programlisting>Add:DosSegMgr={},sde</programlisting> </sect2> </sect1> <sect1 id="removeseg"><title>Removing a segment manager</title> <para>When a segment manager is removed from a disk, the disk can be reused by other plug-ins. The <command>remove</command> command causes the segment manager to remove its partition or slice table from the disk, leaving the raw disk storage object that then becomes an available EVMS storage object. As an available storage object, the disk is free to be used by any plug-in when storage objects are created or expanded. You can also add any of the segment managers to the available disk storage object to subdivide the disk into segments.</para> <para>Most segment manager plug-ins check to determine if any of the segments are still in use by other plug-ins or are still part of volumes. If a segment manager determines that there are no disks from which it can safely remove itself, it will not be listed when you use the <command>remove</command> command. In this case, you should delete the volume or storage object that is consuming segments from the disk you want to reuse.</para> </sect1> <sect1 id="rmvex"><title>Example: remove a segment manager</title> <para>This section shows how to remove a segment manager with EVMS.</para> <blockquote><example><title>Remove the DOS Segment Manager</title> <para>Remove the DOS Segment Manager from disk <filename>sda</filename>.</para></example></blockquote> <note><title>NOTE</title> <para>In the following example, the DOS Segment Manager has one primary partition on disk <filename>sda</filename>. The segment is a compatibility volume known as <filename>/dev/evms/sda1</filename>.</para></note> <sect2 id="removeseggui"><title>Using the EVMS GUI context sensitive menu</title> <para>Follow these steps to remove a segment manager with the GUI context sensitive menu:</para> <orderedlist> <listitem><para>From the <guimenuitem>Volumes</guimenuitem> tab, right click <filename>/dev/evms/sda1</filename>..</para></listitem> <listitem><para>Click <guibutton>Delete</guibutton>.</para></listitem> <listitem><para>Select <menuchoice><guimenu>Actions</guimenu> <guimenuitem>Remove</guimenuitem> <guimenuitem>Segment Manager from Storage Object</guimenuitem></menuchoice>.</para></listitem> <listitem><para>Select <guimenuitem>DOS Segment Manager, sda</guimenuitem>.</para></listitem> <listitem><para>Click <guibutton>Remove</guibutton>.</para></listitem> </orderedlist> </sect2> <sect2 id="removesegcur"><title>Using Ncurses</title> <para>Follow these steps to remove a segment manager with the Ncurses interface:</para> <orderedlist> <listitem><para>Select <menuchoice><guimenu>Actions</guimenu><guimenuitem>Delete</guimenuitem> <guimenuitem>Volume</guimenuitem></menuchoice>.</para></listitem> <listitem><para>Select <filename>/dev/evms/sda1</filename>.</para></listitem> <listitem><para>Click <guibutton>Delete</guibutton>.</para></listitem> <listitem><para>Select <menuchoice><guimenu>Actions</guimenu><guimenuitem>Remove</guimenuitem> <guimenuitem>Segment Manager from Storage Object</guimenuitem></menuchoice>.</para></listitem> <listitem><para>Click <guibutton>Remove</guibutton>.</para></listitem> </orderedlist> </sect2> <sect2 id="removesegcli"><title>Using the CLI</title> <para>Follow these steps to remove a segment manager with the CLI:</para> <programlisting>Delete:/dev/evms/sda1</programlisting> <programlisting>Remove: sda</programlisting> </sect2> </sect1> </chapter> Index: over-ug.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/over-ug.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -r1.3 -r1.4 --- over-ug.xml 16 Feb 2005 17:33:20 -0000 1.3 +++ over-ug.xml 16 Feb 2005 17:41:17 -0000 1.4 @@ -3,7 +3,8 @@ <para>EVMS brings a new model of volume management to Linux®. EVMS integrates all aspects of volume management, such as disk partitioning, Linux logical volume manager (LVM) and -multi-disk (MD) management, OS2 and AIX volume managers, and file system operations into a single +multi-disk (MD) management, OS2 and AIX volume managers, and +file system operations into a single cohesive package. With EVMS, various volume management technologies are accessible through one interface, and new technologies can be added as plug-ins as they are developed.</para> @@ -23,7 +24,8 @@ framework while ensuring your system still interacts correctly with stored data. With EVMS, you are can use bad block relocation, shrink and expand volumes, -create snapshots of your volumes, and set up RAID (redundant array of independent devices) features for your system. +create snapshots of your volumes, and set up RAID +(redundant array of independent devices) features for your system. 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> Index: clusterops-ug.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/clusterops-ug.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- clusterops-ug.xml 16 Feb 2005 17:33:08 -0000 1.2 +++ clusterops-ug.xml 16 Feb 2005 17:41:17 -0000 1.3 @@ -17,20 +17,29 @@ 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> +<para>Note the following rules and limitations for creating cluster containers: +</para> + <itemizedlist> -<listitem><para>Do not assign non-shared disks 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 must ensure that objects and volumes created from cluster storage manager -segments do not span multiple containers.</para> +<listitem> +<para>Do not assign non-shared disks to a cluster container. +</para> </listitem> -<listitem><para>A disk should not span cluster containers.</para> + +<listitem> +<para>Storage objects and volumes created on a cluster container must not +span across multiple cluster containers. +The EVMS Engine enforces this rule by disallowing such configurations. +</para> </listitem> -<listitem><para>Do not assign RAID, snapshot, and BBR features to storage -objects on a cluster container.</para> + +<listitem> +<para>Do not assign RAID-1, RAID-5, BBR, or snapshotting +to storage objects on a shared cluster container. These plug-ins +can be used on private cluster containers. +</para> </listitem> + </itemizedlist> </sect1> @@ -194,9 +203,6 @@ </listitem> <listitem><para>Commit the changes.</para> </listitem> -<listitem><para>Quit the GUI and 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> @@ -255,7 +261,6 @@ <para>On the CLI, type the following command to create shared container <filename>Shar1</filename>:</para> <programlisting>create: container,CSM={name="Shar1",type="shared"},sdd,sde,sdf</programlisting> -<para>Run <command>evms_activate</command> on each node of the cluster. This process will be automated in future releases of EVMS.</para> </sect2> </sect1> @@ -282,17 +287,14 @@ <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> +<listitem><para>Select the container <guimenuitem>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> +<listitem><para>Change "Type" 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>Quit the GUI and 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> @@ -304,7 +306,7 @@ </listitem> <listitem><para>The Modify Container Properties dialog opens. Select the container -<filename>csm/Priv1</filename> by +<filename>Priv1</filename> by pressing <keycap>spacebar</keycap>. The container you selected is marked with an "x."</para> <para>Press <keycap>Enter</keycap>.</para> </listitem> @@ -314,13 +316,13 @@ </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><para>The Modify Container Properties - Configuration Options" dialog opens. Scroll down with the <keycap>down</keycap> arrow and press <keycap>spacebar</keycap> on "Type".</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 - +<para>The changed value now displays in the Modify Container Properties - Configuration Options dialog.</para> </listitem> @@ -329,10 +331,6 @@ </listitem> <listitem><para>Save the changes by clicking <keycap>Save</keycap> in the <guimenuitem>Actions</guimenuitem> pulldown menu.</para> </listitem> -<listitem><para>Quit Ncurses and 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> @@ -341,10 +339,8 @@ <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> +<programlisting>modify: Priv1,type=shared</programlisting> + </sect2> </sect1> @@ -371,17 +367,14 @@ <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> +<listitem><para>Select the container <guimenuitem>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> +<listitem><para>Change "Type" to "private" and the "Node" 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>Quit the GUI and 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> @@ -396,7 +389,7 @@ <listitem> <para>The Modify Container Properties dialog opens. Select the container -<filename>csm/Shar1</filename> by +<filename>Shar1</filename> by pressing <keycap>spacebar</keycap>. The container you selected is marked with an "x."</para> <para>Press <keycap>Enter</keycap>.</para> </listitem> @@ -407,7 +400,7 @@ <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><para>The Change Option Value dialog opens. Select <userinput>private</userinput> and press <keycap>Enter</keycap>.</para> </listitem> <listitem><para>The Modify Container Properties - @@ -415,7 +408,7 @@ 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 Change Option Value dialog opens. Select <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> @@ -423,8 +416,6 @@ </listitem> <listitem><para>Save the changes by clicking <keycap>Save</keycap> in the <guimenuitem>Actions</guimenuitem> pulldown.</para></listitem> -<listitem><para>Quit Ncurses and 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> @@ -434,10 +425,7 @@ <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> +<programlisting>modify: Shar1,type=private,node=node1</programlisting> </sect2> </sect1> @@ -471,7 +459,7 @@ </para> </listitem> <listitem> -<para>Select the container <filename>csm/c1</filename> and press +<para>Select the container <filename>c1</filename> and press <keycap>Next</keycap>. </para> <para> @@ -479,7 +467,7 @@ </para> </listitem> <listitem> -<para>Change "Type Field" to "deported." Click <keycap>Modify</keycap>. +<para>Change "Type" to "deported." Click <keycap>Modify</keycap>. </para> <para> A window opens that displays the outcome. @@ -490,13 +478,6 @@ </para> </listitem> </orderedlist> -<note><title>NOTE</title> -<para> -If the deported container was a shared container, quit the GUI and then -run <command>evms_activate</command> on each cluster node. This operation -will be automated in a future release of EVMS. -</para> -</note> </sect2> @@ -568,14 +549,6 @@ </orderedlist> -<note><title>NOTE</title> -<para> -If the deported container was a shared container, quit Ncurses and then -run <command>evms_activate</command> on each cluster node. This operation -will be automated in a future release of EVMS. -</para> -</note> - </sect2> <sect2><title>Using the CLI</title> @@ -584,17 +557,9 @@ at the CLI prompt: </para> <programlisting> -modify: csm/c1,type="deported" +modify: c1,type=deported </programlisting> -<note><title>NOTE</title> -<para> -If the deported container was a shared container, -run <command>evms_activate</command> on each cluster node. This operation -will be automated in a future release of EVMS. -</para> -</note> - </sect2> </sect1> <sect1><title>Deleting a cluster container</title> @@ -633,8 +598,9 @@ 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> +<para>Refer to +<ulink url="http://www.linux-ha.org/download/GettingStarted.html">http://www.linux-ha.org/download/GettingStarted.html</ulink> for more details on the +semantics of resource groups.</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> @@ -671,7 +637,8 @@ </listitem> </orderedlist> <para> -The discovery of the remote configuration is initiated and the status +The GUI gathers information about the objects, containers, and volumes on +the other node. The status bar displays the message "Now administering node node2," which indicates that the GUI is switched over to node node2. </para> @@ -694,8 +661,8 @@ </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> +<listitem><para>After a while, you will be switched over to +the node <filename>node2</filename>.</para></listitem> </orderedlist> </sect2> @@ -731,8 +698,7 @@ <para> Similarly, a shared container and its objects are made active on a node if the node currently has quorum. However, the administrator can force the -importation of private and shared containers by overriding these rules, as -follows: +importation of private and shared containers by overriding these rules. </para> <note><title>NOTE</title> @@ -747,8 +713,9 @@ <orderedlist> <listitem> <para> -Enabling the maintenance mode in the <command>evms.conf</command> file. -The option to modify in the <command>evms.conf</command> file is the following: +Enabling maintenance mode in the <filename>/etc/evms.conf</filename> file. +The option to modify in the <filename>/etc/evms.conf</filename> file is the +following: </para> <programlisting> # cluster segment manager section Index: debuglog-ug.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/debuglog-ug.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- debuglog-ug.xml 16 Feb 2005 17:13:57 -0000 1.2 +++ debuglog-ug.xml 16 Feb 2005 17:41:17 -0000 1.3 @@ -23,9 +23,9 @@ <row><entry>Warning</entry><entry>An error has occurred that the system might or might not be able to work around.</entry></row> <row><entry>Default</entry><entry>An error has occurred that the system has already worked around.</entry></row> <row><entry>Details</entry><entry>Detailed information about the system.</entry></row> +<row><entry>Entry_Exit</entry><entry>Traces the entries and exits of functions.</entry></row> <row><entry>Debug</entry><entry>Information that helps the user debug a problem.</entry></row> <row><entry>Extra</entry><entry>More information that helps the user debug a problem than the "Debug" level provides.</entry></row> -<row><entry>Entry_Exit</entry><entry>Traces the entries and exits of functions.</entry></row> <row><entry>Everything</entry><entry>Verbose output.</entry></row> </tbody></tgroup></table></para> @@ -58,6 +58,18 @@ <para>The CLI command, <command>probe</command>, opens and closes the Engine, which causes a new log to start. The log that existed before the <command>probe</command> command was issued is renamed <filename>/var/log/evmsEngine.1.log</filename> and the new log is named <filename>/var/log/evmsEngine.log</filename>.</para> +<para> +If you will be frequently using a different log level than the default, +you can specify the default logging level in +<filename>/etc/evms.conf</filename> rather than +having to use the <command>-d</command> option when starting the user interface. +The "debug_level" option in the "engine" section sets the default +logging level for when the Engine is opened. +Using the <command>-d</command> option +during the command invocation overrides the setting in +<filename>/etc/evms.conf</filename>. +</para> + </sect1> </chapter> --- NEW FILE: appx-opengfs.xml --- <appendix id="gfsfsim"><title>OpenGFS file system interface module</title> <para> The OpenGFS FSIM lets EVMS users create and manage OpenGFS file systems from within the EVMS interfaces. In order to use the OpenGFS FSIM, the OpenGFS utilities must be installed on your system. Go to <ulink url="http://sourceforge.net/projects/opengfs">http://sourceforge.net/projects/opengfs</ulink> for the OpenGFS project. </para> <sect1 id="createopengfsfsim"><title>Creating OpenGFS file systems</title> <para> OpenGFS file systems can be created with <command>mkfs</command> on any EVMS or compatibility volume that does not already have a file system and that is produced from a shared cluster container. The following options are available for creating OpenGFS file systems:</para> <variablelist> <varlistentry><term>blocksize</term> <listitem> <para>Set the file system block size. The block size is in bytes. The block size must be a power of 2 between 512 and 65536, inclusive. The default block size is 4096 bytes. </para> </listitem> </varlistentry> <varlistentry><term>journals</term> <listitem> <para>The names of the journal volumes, one for each node. </para> </listitem> </varlistentry> <varlistentry><term>protocol</term> <listitem> <para>Specify the name of the locking protocol to use. The choices are "memexp" and "opendlm." </para> </listitem> </varlistentry> <varlistentry><term>lockdev</term> <listitem> <para>Specify the shared volume to be used to contain the locking metadata. </para> </listitem> </varlistentry> </variablelist> <para> The OpenGFS FSIM only takes care of file system operations. It does not take care of OpenGFS cluster and node configuration. Before the volumes can be mounted, you must configure the cluster and node separately after you have made the file system and saved the changes. </para> </sect1> <sect1 id="checkopengfsfsim"><title>Checking OpenGFS file systems</title> <para> The OpenGFS utility for checking the file system has no additional options. </para> </sect1> <sect1 id="removeopengfsfsim"><title>Removing OpenGFS file systems</title> <para> An OpenGFS file system can be removed from its volume if the file system is unmounted. This operation involves erasing the superblock from the volume, erasing the log headers for the journal volumes, and erasing the control block on the cluster configuration volume associated with the file system volume so that the file system will not be recognized in the future. There are no options available for removing file systems. </para> </sect1> <sect1 id="expandshrinkopengfsfsim"><title>Expanding and shrinking OpenGFS file systems</title> <para> OpenGFS only allows a volume to be expanded. OpenGFS only allows a volume to expanded when the volume is mounted. An OpenGFS file system is automatically expanded when its volume is expanded. </para> </sect1> </appendix> Index: EVMSUG.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/EVMSUG.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -r1.3 -r1.4 --- EVMSUG.xml 16 Feb 2005 17:33:06 -0000 1.3 +++ EVMSUG.xml 16 Feb 2005 17:41:13 -0000 1.4 @@ -1,14 +1,14 @@ <?xml version="1.0"?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "/usr/share/sgml/docbook/xml-dtd-4.2/docbookx.dtd" [ -<!ENTITY evers "2.2.0"> +<!ENTITY evers "2.3.0"> <!ENTITY evmsugchap1 SYSTEM "over-ug.xml"> <!ENTITY evmsugpref SYSTEM "pref-ug.xml"> <!ENTITY evmscmuse SYSTEM "cmuse-ug.xml"> <!ENTITY evmsdebuglog SYSTEM "debuglog-ug.xml"> <!ENTITY evmsmigrate SYSTEM "migrateto-ug.xml"> <!ENTITY evmsdisplaydetails SYSTEM "displaydetails-ug.xml"> -<!ENTITY evmsassignseg SYSTEM "assignseg-ug.xml"> +<!ENTITY evmsaddremseg SYSTEM "addremseg-ug.xml"> <!ENTITY evmscreateseg SYSTEM "create-seg.xml"> <!ENTITY evmscreatecont SYSTEM "create-cont.xml"> <!ENTITY evmscreatereg SYSTEM "create-reg-ug.xml"> @@ -34,6 +34,7 @@ <!ENTITY evmsxfsfsim SYSTEM "appx-xfs.xml"> <!ENTITY evmsreiserfsim SYSTEM "appx-reiserfs.xml"> <!ENTITY evmsext23fsim SYSTEM "appx-ext23.xml"> +<!ENTITY evmsopengfsfsim SYSTEM "appx-opengfs.xml"> ]> <book id="evmsug"> <bookinfo><title>EVMS User Guide</title> @@ -51,10 +52,10 @@ <affiliation><orgname>IBM</orgname></affiliation></author> </authorgroup> -<pubdate>November 25, 2003</pubdate> +<pubdate>April 9, 2004</pubdate> -<copyright><year>2003</year> +<copyright><year>2004</year> <holder>IBM</holder></copyright> @@ -81,7 +82,7 @@ &evmsdebuglog; &evmsmigrate; &evmsdisplaydetails; -&evmsassignseg; +&evmsaddremseg; &evmscreateseg; &evmscreatecont; &evmscreatereg; @@ -105,5 +106,6 @@ &evmsxfsfsim; &evmsreiserfsim; &evmsext23fsim; +&evmsopengfsfsim; </book> Index: appx-csm.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/appx-csm.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- appx-csm.xml 16 Feb 2005 17:33:06 -0000 1.2 +++ appx-csm.xml 16 Feb 2005 17:41:17 -0000 1.3 @@ -86,10 +86,11 @@ </varlistentry> <varlistentry><term>Container Name</term> -<listitem><para>The name for the container. Currently, you need to keep this name unique +<listitem><para>The name for the container. You need to keep this name unique across the cluster to prevent name-in-conflict errors should the container fail over to -another node that has a container with the same name. Later releases of EVMS will assist -you with this. </para></listitem> +another node that has a container with the same name. +</para> +</listitem> </varlistentry> <varlistentry><term>Storage Type</term> Index: convertto-ug.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/convertto-ug.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -r1.3 -r1.4 --- convertto-ug.xml 16 Feb 2005 17:33:08 -0000 1.3 +++ convertto-ug.xml 16 Feb 2005 17:41:17 -0000 1.4 @@ -5,10 +5,21 @@ <sect1><title>When to convert volumes</title> -<para>There are several different scenarios that might help you determine what type of volumes you need. For example, if you wanted persistent names or to make full use of EVMS features, such as BBR, Drive Linking, or Snapshotting, you would convert your compatibility volumes to EVMS volumes. In another situation, you might decide that a volume needs to be read by a system that understands the underlying volume management scheme. In this case, you would convert your EVMS volume to a compatibility volume.</para> -<para>A volume can only be converted when it is offline. This means the volume must -be unmounted and otherwise not in use. The volume must be unmounted because the conversion operation changes both the name and the device number of the volume. Once the volume -is converted, you can remount it using its new name.</para> +<para>There are several different scenarios that might help you determine +what type of volumes you need. +For example, if you wanted persistent names or to make full use of +EVMS features, such as Drive Linking or Snapshotting, you would convert +your compatibility volumes to EVMS volumes. +In another situation, you might decide that a volume needs to be +read by a system that understands the underlying volume management scheme. +In this case, you would convert your EVMS volume to a +compatibility volume.</para> + +<para>A volume can only be converted when it is offline. +This means the volume must be unmounted and otherwise not in use. +The volume must be unmounted because the conversion operation changes both +the name and the device number of the volume. +Once the volume is converted, you can remount it using its new name.</para> </sect1> Index: appx-ext23.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/appx-ext23.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- appx-ext23.xml 16 Feb 2005 17:13:52 -0000 1.1 +++ appx-ext23.xml 16 Feb 2005 17:41:17 -0000 1.2 @@ -97,7 +97,7 @@ </sect1> -<sect1 id="removereiserfsim"><title>Removing Ext-2/3 file systems</title> +<sect1 id="removeext23fsim"><title>Removing Ext-2/3 file systems</title> <para> An Ext-2/3 file system can be removed from its volume if the file system is Index: expandshrink.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/expandshrink.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- expandshrink.xml 16 Feb 2005 17:13:57 -0000 1.2 +++ expandshrink.xml 16 Feb 2005 17:41:17 -0000 1.3 @@ -28,7 +28,49 @@ <entry>Expands</entry> </row> </thead> -<tbody><row><entry>JFS</entry><entry>No</entry><entry>Online only</entry></row><row><entry>XFS</entry><entry>No</entry><entry>Online only</entry></row><row><entry>ReiserFS</entry><entry>Offline only</entry><entry>Offline and online</entry></row><row><entry>ext2/3</entry><entry>Offline only</entry><entry>Offline only</entry></row><row><entry>SWAPFS</entry><entry>Offline only</entry><entry>Offline only</entry></row></tbody></tgroup></table></para> +<tbody> +<row> +<entry>JFS</entry> +<entry>No</entry> +<entry>Online only</entry> +</row> + +<row> +<entry>XFS</entry> +<entry>No</entry> +<entry>Online only</entry> +</row> + +<row> +<entry>ReiserFS</entry> +<entry>Offline only</entry> +<entry>Offline and online</entry> +</row> + +<row> +<entry>ext2/3</entry> +<entry>Offline only</entry> +<entry>Offline only</entry> +</row> + +<row> +<entry>SWAPFS</entry> +<entry>Offline only</entry> +<entry>Offline only</entry> +</row> + +<row> +<entry>OpenGFS</entry> +<entry>No</entry> +<entry>Online only</entry> +</row> + +</tbody> +</tgroup> +</table> + +</para> + <para>You can perform all of the supported shrink and expand operations with each of the EVMS user interfaces.</para></sect1> <sect1 id="exshrink"><title>Example: shrink a volume</title> @@ -289,4 +331,4 @@ </sect2> </sect1> -</chapter> \ No newline at end of file +</chapter> Index: pref-ug.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/pref-ug.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -r1.3 -r1.4 --- pref-ug.xml 16 Feb 2005 17:33:20 -0000 1.3 +++ pref-ug.xml 16 Feb 2005 17:41:17 -0000 1.4 @@ -57,8 +57,8 @@ configuration of a volume or storage object.</entry></row> <row><entry>21. Moving segment storage objects</entry><entry>Discusses how to use the move function for moving segments.</entry></row> -<row><entry>A. The DOS link plug-in</entry> -<entry>Provides details about the DOS link plug-in, which is a segment manager plug-in.</entry></row> +<row><entry>A. The DOS plug-in</entry> +<entry>Provides details about the DOS plug-in, which is a segment manager plug-in.</entry></row> <row><entry>B. The MD region manager</entry> <entry>Explains the Multiple Disks (MD) support in Linux that is a software implementation of RAID.</entry></row> <row><entry>C. The LVM plug-in</entry> @@ -73,6 +73,8 @@ <entry>Provides information about the ReiserFS FSIM.</entry></row> <row><entry>H. Ext-2/3 file system interface module</entry> <entry>Provides information about the Ext-2/3 FSIM.</entry></row> +<row><entry>I. OpenGFS file system interface module</entry> +<entry>Provides information about the OpenGFS FSIM.</entry></row> </tbody></tgroup> </table> </preface> Index: appx-lvm.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/appx-lvm.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -r1.3 -r1.4 --- appx-lvm.xml 16 Feb 2005 17:33:08 -0000 1.3 +++ appx-lvm.xml 16 Feb 2005 17:41:17 -0000 1.4 @@ -1,4 +1,4 @@ -<appendix id="appxsnap"><title>The LVM plug-in</title> +<appendix id="appxlvm"><title>The LVM plug-in</title> <para>The LVM plug-in combines storage objects into groups called containers. From these containers, new storage objects can be created, with a variety of Index: createvol-ug.xml =================================================================== RCS file: /cvsroot/evms/Documentation/user_guide/createvol-ug.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -r1.3 -r1.4 --- createvol-ug.xml 16 Feb 2005 17:33:19 -0000 1.3 +++ createvol-ug.xml 16 Feb 2005 17:41:17 -0000 1.4 @@ -15,8 +15,8 @@ EVMS equipped system. Volumes are mountable and can contain file systems.</para> - <para>EVMS native volumes contain EVMS-specific information - to identify the name and minor number. After this volume information is + <para>EVMS native volumes contain EVMS-specific information to identify + the volume name. After this volume information is applied, the volume is no longer fully backward compatible with existing volume types.</para> --- assignseg-ug.xml DELETED --- |