diff --git a/LDP/guide/docbook/EVMSUG/EVMSUG.xml b/LDP/guide/docbook/EVMSUG/EVMSUG.xml index de20af45..fbed2753 100644 --- a/LDP/guide/docbook/EVMSUG/EVMSUG.xml +++ b/LDP/guide/docbook/EVMSUG/EVMSUG.xml @@ -1,10 +1,9 @@ - + - @@ -23,7 +22,8 @@ - + + @@ -38,18 +38,20 @@ EVMS User Guide -Joy + +Christine +Lorenz +IBM + +Joy Goodreau IBM Kylie Smith IBM -Christine -Lorenz -IBM + - -March 31, 2003 +November 25, 2003 2003 @@ -62,8 +64,9 @@ Windows is a trademark of Microsoft Corporation in the United States, other countries, or both. Linux is a trademark of Linus Torvalds. -Other company, product, and service names may be trademarks or service marks of others. UNIX is a registered trademark of The Open Group in the United States and other countries. +Other company, product, and service names may be trademarks or service marks of others. + This document is provided "AS IS," with no express or implied warranties. Use the information in this document at your own risk. @@ -74,7 +77,6 @@ &evmsugpref; &evmsugchap1; -&evmsuginstall; &evmscmuse; &evmsdebuglog; &evmsmigrate; @@ -93,7 +95,8 @@ &addfeatures; &evmsplugintasks; &evmsdeleterecursive; -&evmsinitram; +&evmsreplaceobjects; +&evmsmovesegs; &evmsdos; &evmsmd; &evmslvm; diff --git a/LDP/guide/docbook/EVMSUG/appx-csm.xml b/LDP/guide/docbook/EVMSUG/appx-csm.xml index b31c7bd6..316e7dfb 100644 --- a/LDP/guide/docbook/EVMSUG/appx-csm.xml +++ b/LDP/guide/docbook/EVMSUG/appx-csm.xml @@ -1,4 +1,3 @@ - The CSM plug-in The Cluster Segment Manager (CSM) is the EVMS plug-in that identifies and @@ -108,7 +107,7 @@ have a choice of using either: ActionsAddSegment Manager. -If the container doesn't exist, it will be created for it. If the container already +If the container doesn't exist, it will be created for the disk. If the container already exists, the disk will be added to it. @@ -130,3 +129,4 @@ disk is removed, the container is also removed. + diff --git a/LDP/guide/docbook/EVMSUG/appx-dos.xml b/LDP/guide/docbook/EVMSUG/appx-dos.xml index b59d8fa9..19553f9a 100644 --- a/LDP/guide/docbook/EVMSUG/appx-dos.xml +++ b/LDP/guide/docbook/EVMSUG/appx-dos.xml @@ -1,6 +1,6 @@ -The DOS link plug-in +The DOS plug-in The DOS plug-in is the most commonly used EVMS segment manager plug-in. The DOS plug-in supports DOS disk partitioning as well as: @@ -322,4 +322,4 @@ EVMS plug-in. No options are available for deleting partitions. - \ No newline at end of file + diff --git a/LDP/guide/docbook/EVMSUG/appx-drivelink.xml b/LDP/guide/docbook/EVMSUG/appx-drivelink.xml index a5e8082a..afeb1b54 100644 --- a/LDP/guide/docbook/EVMSUG/appx-drivelink.xml +++ b/LDP/guide/docbook/EVMSUG/appx-drivelink.xml @@ -1,6 +1,3 @@ - - - The drive link plug-in The EVMS drive link plug-in is an aggregating plug-in that @@ -51,7 +48,7 @@ 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. +logging errors, help you take the appropriate actions to recover the drive link. @@ -82,7 +79,7 @@ By adding an additional storage object to the end of the drive link. -Bexpanding the last storage object in the drive link. +By expanding the last storage object in the drive link. @@ -140,4 +137,5 @@ No options are available for deleting a drive link storage object. - \ No newline at end of file + + diff --git a/LDP/guide/docbook/EVMSUG/appx-lvm.xml b/LDP/guide/docbook/EVMSUG/appx-lvm.xml index 58dc8bd3..d91a3ed5 100644 --- a/LDP/guide/docbook/EVMSUG/appx-lvm.xml +++ b/LDP/guide/docbook/EVMSUG/appx-lvm.xml @@ -1,6 +1,3 @@ - - - The LVM plug-in The LVM plug-in combines storage objects into groups called containers. @@ -194,6 +191,102 @@ compatibility volume, an EVMS volume, or consumed by another EVMS plug-in. No options are available for deleting LVM regions. +Moving LVM regions +The LVM plug-in lets you change the logical-to-physical mapping +for an LVM region and move the necessary data in the process. +This capability is most useful if a PV needs to be removed from a container. +There are currently two LVM plug-in functions for moving regions: +move_pv and move_extent. + +move_pv +When a PV needs to be removed from a container, all PEs on that PV that are +allocated to regions must be moved to other PVs. The move_pv command lets you move PEs to other PVs. +move_pv is targeted at the LVM container and the desired PV is used as +the selected object. The following options are available: + +target_pvs +By default, all remaining PVs in the container are used to find +available extents to move the PEs. You can specify a subset of the PVs with this option. + + +maintain_stripes +When the target PV contains striped regions, there are three choices +for handling moving extents that belong to those regions: + + +no +Don't bother to maintain true striping. This choice allows +extents to be moved to PVs that the region already uses for other stripes. +This means that the performance will not be as optimal as it is with true +striping, but allows the most flexibility in performing the move operation. +This choice is the default for the maintain_stripes option. + + +loose +Ensure that moved extents do not end up on any PVs that the +striped region already uses. However, this does not ensure that all moved +extents end up on the same PV. For example, a region with three stripes may +end up mapping to four or more PVs. + + +strict +Ensure that all moved extents end up on the same PV, thus ensuring +true striping with the same number of PVs that the striped region originally used. +This is the most restricted choice, and may prevent the move_pv operation from +proceeding (depending on the particular configuration of the container). + + + + +If the target PV has no striped regions, the maintain_stripes option is ignored. + + + + + + +move_extent +In addition to moving all the extents from one PV, the LVM plug-in provides +the ability to move single extents. +This allows a fine-grain tuning of the allocation of extents. +This command is targeted at the region owning the extent to move. There are +three required options for the move_extent command: + + +le +The number of the logical extent to move. LE numbers start at 0. + +pv +The target object to move the extent to. + +pe +The target physical extent on the target object. PE numbers +also start at 0. + + +To determine the source LE and target PE, it is often helpful to view the +extended information about the region and container in question. +The following are command-line options that can be used to gather this +information: +To view the map of LEs in the region, enter this command: +query:ei,<region_name>,Extents + +To view the list of PVs in the container, enter this command: +query:ei,<container_name>,Current_PVs + +To view the current PE map for the desired target PV, enter this command: +query:ei,<container_name>,PEMapPV# +# is the number of the target PV in the container. + +This information is also easily obtainable in the GUI and Text-Mode UIs by +using the "Display Details" item in the context-popup menus for the desired +region and container. + + + + + - \ No newline at end of file + + diff --git a/LDP/guide/docbook/EVMSUG/appx-md.xml b/LDP/guide/docbook/EVMSUG/appx-md.xml index 841921e8..89526650 100644 --- a/LDP/guide/docbook/EVMSUG/appx-md.xml +++ b/LDP/guide/docbook/EVMSUG/appx-md.xml @@ -1,4 +1,3 @@ - The MD region manager @@ -19,8 +18,8 @@ member of another Linux RAID device. Whereas there are six standard types of RAID arrays (RAID-0 through RAID-5) in the hardware implementation, the Linux implementation of software RAID has RAID-0, RAID-1, RAID-4, and RAID-5 levels. In addition to these -four levels, Linux also has support for another non-redundant array called -"Linear Mode." +four levels, Linux also has support for other non-redundant arrays called +"Linear Mode" and "MULTIPATH." @@ -46,7 +45,7 @@ chunk size is a power of 2 of the previous value. Consider the intended use of MD region when selecting chunk size. For example, if the MD region contains mostly large files, you might see better performance by having a larger chunk size. The block size of the file system being used is -also an importnat factor when selecting chunk size. +also an important factor when selecting chunk size. This option is available for use with RAID-0 and RAID-4/5. @@ -58,8 +57,8 @@ Otherwise, the MD array operates in a degraded mode. RAID-5 algorithms -There are four RAID-5 parity algorithms: left assymetric, right -assymetric, left symmetric, and right symmetric. The ACCS web +There are four RAID-5 parity algorithms: left asymmetric, right +asymmetric, left symmetric, and right symmetric. The ACCS web page provides examples of what the different parity algorithms do. This option is available for use with the RAID-5 algorithm. @@ -81,30 +80,68 @@ spare disk from the MD region. This is a safe operation because the spare disk not contain any data. -Removing an active object (RAID-1 only) +Reconfiguring MD arrays -Only the MD RAID-1 region plug-in lets you remove an active disk of the -MD region. This option is available for those MD RAID-1 regions that have at least -two active members. +Expanding and shrinking MD arrays (linear and RAID-1) +If the MD region is part of a compatibility volume and the MD region is +the topmost object of the volume, it's possible to expand and shrink the MD region. +Expanding a linear MD region +A linear MD region can be expanded either by expanding the last member +or by adding a new member. + +Shrinking a linear MD region +A linear MD region can be shrunk either by shrinking the last member +or by removing disks from the array (last member first). + +Expanding a RAID-1 MD region +A RAID-1 MD region can only be expanded if all members can be expanded. + + +Shrinking a RAID-1 MD region +A RAID-1 MD region can only be shrunk if all members can be shrunk. + + + + +Adding an active object (RAID-1 only) +Use this option to increase the number of mirrors of the RAID-1 region, from +n-way mirrors to (n+1)-way mirrors. When the operation is committed, the +kernel MD driver performs a resync of the MD array. + + +Removing an active object (RAID-1 only) +Use this option to decrease the number of mirrors of the RAID-1 region, from +n-way mirrors to (n-1)-way mirrors. + Removing a faulty object (RAID-1 and RAID-4/5) When an I/O error occurs on a disk, the disk is marked faulty by the kernel -MD code. Use this function to permanently remove the faulty disk from the MD region. +MD driver. Use this function to permanently remove the faulty disk from the MD region. -Marking an object faulty (RAID-4/5 only) +Marking an object faulty (RAID-1 and RAID-4/5) -This option is available when the RAID-4/5 array has at least one spare disk. -Use this option to swap an active disk with a spare disk. The active disk is marked -faulty and can be later removed, as described in . +There are two scenarios for marking an active disk faulty: + +When the MD region has at least one spare disk, the active disk will +be swapped with a spare disk. + + +When the MD region has no spare disks, the active disk will be marked +faulty and the MD array will operate in degraded mode. + + +When the active disk is successfully marked +faulty, it can be immediately removed from the MD region. Alternatively, the +faulty disk can be later removed, as described in . @@ -423,8 +460,30 @@ Cannot sustain a two-disk simultaneous failure. + + +MULTIPATH +Characteristics: + +Consists of 1 or more disks. +Disks are actually I/O paths to the same physical disk. +Spreads I/O across active disks for simple load balancing. +Like other RAID levels, I/O failures will mark a disk faulty. +Failed I/O will be automatically retried on remaining active disks. + + +Advantages: + +Achieves fault-tolerance through redundant I/O paths. +Possible performance improvements through load balancing. + + +Disadvantages: + +Cannot survive a single disk crash. + diff --git a/LDP/guide/docbook/EVMSUG/appx-snap.xml b/LDP/guide/docbook/EVMSUG/appx-snap.xml index 6b6f677c..6b4e1286 100644 --- a/LDP/guide/docbook/EVMSUG/appx-snap.xml +++ b/LDP/guide/docbook/EVMSUG/appx-snap.xml @@ -1,6 +1,3 @@ - - - The snapshot plug-in A snapshot represents a frozen image of a volume. The source of a snapshot is @@ -20,7 +17,7 @@ This data portion is called a "chunk." When data is written to a chunk on the original volume, the snapshot intercepts the I/O request and determines if that chunk has already been saved. If the chunk has not been saved, the chunk is copied from the original to the -snapshot, and then the write request is allowed to proceed ot the original volume. +snapshot, and then the write request is allowed to proceed to the original volume. If additional data is written to that same chunk on the original, the chunk does not need to be copied again. When data is read from the snapshot, it is the same as when data is read from the original. @@ -41,18 +38,18 @@ object, which is to make an EVMS volume from the object. (disks, segments, regions, or feature objects). The size of this consumed object is the size available to the snapshot object. The snapshot object can be smaller or larger than the original volume. If the object is smaller, the original volume could fill up -as data is copied from the oriignal to the snapshot, given sufficient activity on the original. +as data is copied from the original to the snapshot, given sufficient activity on the original. In this situation, the snapshot is deactivated and additional I/O to the snapshot fails. 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 size to use for a particular situation. The goal is -to create a snapshot object large enough to prevent the shapshot from being +to create a snapshot object large enough to prevent the snapshot 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. - tells how to create snapshots. The following options are available for + tells how to create snapshots. The following options are available for creating snapshot objects through the CLI: @@ -136,4 +133,5 @@ all but the desired snapshot must be deleted before rollback can take place. - \ No newline at end of file + + diff --git a/LDP/guide/docbook/EVMSUG/appx-xfs.xml b/LDP/guide/docbook/EVMSUG/appx-xfs.xml index d0d44964..e12835b3 100644 --- a/LDP/guide/docbook/EVMSUG/appx-xfs.xml +++ b/LDP/guide/docbook/EVMSUG/appx-xfs.xml @@ -1,4 +1,3 @@ - XFS file system interface module @@ -105,3 +104,4 @@ Hence, volumes with XFS file systems cannot be shrunk. + diff --git a/LDP/guide/docbook/EVMSUG/assignseg-ug.xml b/LDP/guide/docbook/EVMSUG/assignseg-ug.xml index 25e5944c..58f317c2 100644 --- a/LDP/guide/docbook/EVMSUG/assignseg-ug.xml +++ b/LDP/guide/docbook/EVMSUG/assignseg-ug.xml @@ -1,18 +1,13 @@ - - - - - - -Assigning a segment manager - This chapter discusses when to use a segment manager, what the different types of segment managers are, and how to assign a segment manager to a disk. -When to assign a segment manager - Assigning a segment manager to a disk allows the disk to be subdivided into +Adding and removing a segment manager + 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. +When to add a segment manager + Adding a segment manager to a disk allows the disk to be subdivided into smaller storage objects called disk segments. The - assign command causes a + add command causes a segment manager to create appropriate metadata and expose freespace that the segment manager - finds on the disk. You need to assign segment managers when you + 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. EVMS displays disk segments as the following types: @@ -27,7 +22,7 @@ Types of segment managers - There are five types of segment managers in EVMS: DOS, GPT, S/390, Cluster, and BSD. + There are seven types of segment managers in EVMS: DOS, GPT, S/390, Cluster, BSD, MAC, and BBR. DOS Segment Manager The most commonly used segment manager is the DOS Segment Manager. This plug-in @@ -87,11 +82,11 @@ 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 assigned or unassigned from a disk. + cannot be added or removed from a disk. Cluster segment manager The cluster segment manager (CSM) supports high availability clusters. When the -CSM is assigned to a shared storage disk, it writes metadata on the disk that: +CSM is added to a shared storage disk, it writes metadata on the disk that: provides a unique disk ID (guid) @@ -123,40 +118,69 @@ The BSD segment manager recognizes such "fully dedicated disks" and pr the BSD partitions. +MAC segment manager +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. + + +BBR segment manager +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: + +reserves replacement blocks +maps bad blocks to reserved blocks + +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. +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. + -Assigning a segment manager to an existing disk - When you assign a segment manager to a disk, the segment manager +Adding a segment manager to an existing disk + 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 assigning a + 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. -Assigning a segment manager to a new disk +Adding a segment manager to a new disk 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 assign a segment manager to the disk so that it + 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. 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 assign a different + 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. -Example: assign a segment manager -This section shows how to assign +Example: add a segment manager +This section shows how to add a segment manager with EVMS. EVMS initially displays the @@ -169,8 +193,8 @@ a segment manager with EVMS. -
Assign the DOS Segment Manager -Assign the DOS Segment Manager to disk sde.
+
Add the DOS Segment Manager +Add the DOS Segment Manager to disk sde.
NOTE In the following example, the DOS Segment @@ -186,7 +210,7 @@ a segment manager with EVMS. Using the EVMS GUI -To assign the DOS Segment Manager to sde, first +To add the DOS Segment Manager to sde, first remove the volume, /dev/evms/sde: @@ -204,7 +228,7 @@ remove the volume, /dev/evms/sde: Click Delete. -After the volume is removed, assign the DOS Segment Manager: +After the volume is removed, add the DOS Segment Manager: Select Actions @@ -219,7 +243,7 @@ remove the volume, /dev/evms/sde: Using Ncurses -To assign the DOS Segment Manager to sde, first remove the +To add the DOS Segment Manager to sde, first remove the volume /dev/evms/sde: Select ActionsDelete @@ -239,7 +263,7 @@ volume /dev/evms/sde: -After the volume is removed, assign the DOS Segment Manager: +After the volume is removed, add the DOS Segment Manager: Select ActionsAdd Segment Manager to Storage Object @@ -254,19 +278,91 @@ volume /dev/evms/sde: Using the CLI -To assign the DOS Segment Manager to sde, first tell EVMS that this disk is not a +To add the DOS Segment Manager to sde, first tell EVMS that this disk is not a volume and is available for use: Delete:/dev/evms/sde -Next, assign the DOS Segment Manager to sde by typing the following: +Next, add the DOS Segment Manager to sde by typing the following: - Assign:DosSegMgr={},sde + Add:DosSegMgr={},sde +Removing a segment manager +When a segment manager is removed from a disk, the disk can be reused by +other plug-ins. The remove 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. +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 remove command. In this case, you should delete the +volume or storage object that is consuming segments from the disk you want to reuse. + + +Example: remove a segment manager +This section shows how to remove +a segment manager with EVMS. + +
Remove the DOS Segment Manager +Remove the DOS Segment Manager from disk sda.
+ + NOTE +In the following example, the DOS Segment + Manager has one primary partition on disk sda. + The segment is a compatibility volume known as + /dev/evms/sda1. + + +Using the EVMS GUI context sensitive menu + +Follow these steps to remove a segment manager with the GUI context sensitive menu: + + +From the Volumes tab, right click /dev/evms/sda1.. +Click Delete. +Select Actions +Remove +Segment Manager from Storage Object. +Select DOS Segment Manager, sda. +Click Remove. + + + + +Using Ncurses +Follow these steps to remove a segment manager with the Ncurses interface: + +Select ActionsDelete +Volume. +Select /dev/evms/sda1. +Click Delete. +Select ActionsRemove +Segment Manager from Storage Object. +Click Remove. + + + + + + +Using the CLI + +Follow these steps to remove a segment manager with the CLI: + + Delete:/dev/evms/sda1 + + Remove: sda + + + + + - \ No newline at end of file diff --git a/LDP/guide/docbook/EVMSUG/clusterops-ug.xml b/LDP/guide/docbook/EVMSUG/clusterops-ug.xml index ae90af56..7e1e887e 100644 --- a/LDP/guide/docbook/EVMSUG/clusterops-ug.xml +++ b/LDP/guide/docbook/EVMSUG/clusterops-ug.xml @@ -1,12 +1,3 @@ - - - - - - - - - Clustering operations 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 @@ -431,7 +422,7 @@ Configuration Options dialog. Press Enter. The outcome of the command is displayed at the bottom of the screen. -Save the changes by clickting Save in the Actions pulldown. +Save the changes by clicking Save in the Actions pulldown. Quit Ncurses and run evms_activate 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. @@ -520,7 +511,7 @@ To deport a container with Ncurses, follow these steps: Modify. Press Enter. -A submeny is displayed. +A submenu is displayed. @@ -609,7 +600,7 @@ will be automated in a future release of EVMS. Deleting a cluster container The procedure for deleting a cluster container is the same for deleting -any container. See +any container. See @@ -619,9 +610,9 @@ any container. See Failover and Failback of a private container on Linux-HA -EVMS supports the Linux-HA cluster manager in EVMS V2.0 and later; support for +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. +manager is also available as of EVMS V2.1, but is not as widely tested. NOTE Ensure that evms_activate is called in one of the startup scripts before the heartbeat startup script is called. If evms_activate is not called, failover @@ -682,7 +673,7 @@ through the various EVMS user interfaces. The discovery of the remote configuration is initiated and the status bar displays the message "Now administering node node2," which indicates -that the GUI is switched over and node node. +that the GUI is switched over to node node2. @@ -784,4 +775,5 @@ Running evms_activate on the node. - \ No newline at end of file + + diff --git a/LDP/guide/docbook/EVMSUG/cmuse-ug.xml b/LDP/guide/docbook/EVMSUG/cmuse-ug.xml index 15db88be..bbfbc14e 100644 --- a/LDP/guide/docbook/EVMSUG/cmuse-ug.xml +++ b/LDP/guide/docbook/EVMSUG/cmuse-ug.xml @@ -1,10 +1,3 @@ - - - - - - - Using the EVMS interfaces This chapter explains how to use the EVMS GUI, Ncurses, and CLI interfaces. This chapter also @@ -97,7 +90,7 @@ Options Window. In the Main Window view, use the following keys to navigate: Accelerator keys in the Main Window - + Left and right arrow keys Navigate between the notebook tabs of the different views. @@ -109,7 +102,7 @@ Options Window. While in a view, use the following keys to navigate:
Accelerator keys in the views - + up and down arrowsAllow movement around the window."+"Opens an object tree. @@ -152,7 +145,7 @@ A selection window typically contains a selection list, plus four to five buttons below it. Use the following keys to navigate in the selection window:
Accelerator keys in the selection window - + TabNavigates (changes keyboard focus) between the list and the buttons.Up and down arrowsNavigates within the selection list. @@ -171,7 +164,7 @@ buttons below it. Use the following keys to navigate in the selection window: Use the following keys to navigate in the configuration options window:
Accelerator keys in the configuration options window - + TabCycles focus between fields and buttonsLeft and right arrowsNavigate the folder tabs if the window has a widget notebook. @@ -185,7 +178,7 @@ Use the following keys to navigate in the configuration options window: For widgets, use the following keys to navigate:
Widget navigation keys in the configuration options window - + TabCycles forward through a set of widgetsShift-TabCycles backward through a set of widgets. @@ -260,7 +253,7 @@ windows. Dialog windows are similar in design to the EVMS GUI -dialogs, which allow a user to navigate forwards and backwards through a series +dialogs, which allow a user to navigate forward and backward through a series of dialogs using Next and Previous. A general guide to dialog windows is listed below: @@ -325,7 +318,7 @@ a list of commands available for a certain object. When invoked, the EVMS CLI prompts for commands. The volume management commands the EVMS CLI understands - are specified in the /usr/src/evms-1.9.0/engine2/ui/cli/grammar.ps + are specified in the /usr/src/evms-2.2.0/engine2/ui/cli/grammar.ps file that accompanies the EVMS package. These commands are described in detail in the EVMS man page, and help on these commands is available from within the EVMS @@ -439,4 +432,5 @@ Volume",compatibility - \ No newline at end of file + + diff --git a/LDP/guide/docbook/EVMSUG/containerops-ug.xml b/LDP/guide/docbook/EVMSUG/containerops-ug.xml index f279e2a2..0b9db4ae 100644 --- a/LDP/guide/docbook/EVMSUG/containerops-ug.xml +++ b/LDP/guide/docbook/EVMSUG/containerops-ug.xml @@ -1,6 +1,6 @@ Clustering operations 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 +this chapter as "cluster containers"), a feature provided by the EVMS Cluster Segment Manager (CSM). 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 @@ -274,7 +274,7 @@ by evms1, convert Using the EVMS GUI Follow these steps to convert a private cluster container to a shared cluster -container with the EVMU GUI: +container with the EVMS GUI: Select ActionsModifyContainer to see a list of containers. @@ -370,7 +370,7 @@ is using the volumes on the container on any node of the cluster. Using the EVMS GUI Follow these steps to convert a shared cluster container to a private cluster -container with the EVMU GUI: +container with the EVMS GUI: Select ActionsModifyContainer to see a list of containers. @@ -429,7 +429,7 @@ Configuration Options dialog. Press Enter. The outcome of the command is displayed at the bottom of the screen. -Save the changes by clickting Save in the Actions pulldown. +Save the changes by clicking Save in the Actions pulldown. Run evms_activate 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. @@ -451,9 +451,9 @@ automated in a future release of EVMS. Failover and Failback of a private container on Linux-HA -EVMS supports the Linux-HA cluster manager in EVMS V2.0 and later; support for +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. +manager is also available as of EVMS V2.1, but is not as widely tested. NOTE Ensure that evms_activate is called in one of the startup scripts before the heartbeat daemon starts (for example, /etc/kinit.d/heartbeat). If evms_activate is not called, failover diff --git a/LDP/guide/docbook/EVMSUG/convertto-ug.xml b/LDP/guide/docbook/EVMSUG/convertto-ug.xml index b77ffc44..b1a24eaa 100644 --- a/LDP/guide/docbook/EVMSUG/convertto-ug.xml +++ b/LDP/guide/docbook/EVMSUG/convertto-ug.xml @@ -1,16 +1,13 @@ - - - Converting volumes This chapter discusses converting compatibility volumes to EVMS volumes and converting EVMS volumes to compatibility volumes. For a discussion -of the differences between compatibility and EVMS volumes, see . +of the differences between compatibility and EVMS volumes, see . When to convert volumes 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. A volume can only be converted when it is offline. This means the volume must -be umounted 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 +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. @@ -22,14 +19,14 @@ is converted, you can remount it using its new name. can be converted to an EVMS volume in the following situations: The compatibility volume has no file system (FSIM) on it. The compatibility volume has a file system, but the file system can be shrunk (if necessary) to make -room for the EMVS metadata. +room for the EVMS metadata.This section provides a detailed explanation of how to convert compatibility volumes to EVMS volumes and provides instructions to help you complete the following task.
Convert a compatibility volume -You have a compatability volume /dev/evms/hda3 +You have a compatibility volume /dev/evms/hda3 that you want to make into an EVMS volume named my_vol.
Using the EVMS GUI @@ -182,4 +179,5 @@ instructions. - \ No newline at end of file + + diff --git a/LDP/guide/docbook/EVMSUG/create-drivelinking.xml b/LDP/guide/docbook/EVMSUG/create-drivelinking.xml index 8ee70fdf..cf063512 100644 --- a/LDP/guide/docbook/EVMSUG/create-drivelinking.xml +++ b/LDP/guide/docbook/EVMSUG/create-drivelinking.xml @@ -7,14 +7,14 @@ and delete a drive link. What is drive linking? Drive linking linearly concatenates objects, allowing you to -create large storage objects and volumes from smaller individual pieces. +create larger storage objects and volumes from smaller individual pieces. For example, say you need a 1 GB volume but do not have contiguous space available of that length. Drive linking lets you link two or more objects together to form the 1 GB volume. The types of objects that can be drive linked include disks, segments, -regions, compatibility volumes, and other feature objects. +regions, and other feature objects. @@ -84,7 +84,7 @@ 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 new drive-link object, the identified link objects are consumed and the new drive-link object is produced. -There are no create objects. +The name for the new object is the only option when creating a drive-link. Only the last object in a drive link @@ -257,7 +257,7 @@ can be selected and added to the drive link. If the expansion point is the last storage object in the drive link, then you expand the drive link by interacting with the plug-in that produced the object. For example, if the link was a segment, then the segment manager plug-in that produced the storage -object expands the link object. Afterwards, the drive link plug-in notices the size +object expands the link object. Afterwords, the drive link plug-in notices the size difference and updates the drive link metadata to reflect the resize of the child object. There are no expand options. @@ -285,7 +285,7 @@ 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. -If the shrink point is the last storage object in th drive link, then you shrink the +If the shrink point is the last storage object in the drive link, then you shrink the drive link by interacting with the plug-in that produced the object. diff --git a/LDP/guide/docbook/EVMSUG/create-reg-ug.xml b/LDP/guide/docbook/EVMSUG/create-reg-ug.xml index 7d11f2dc..27740e6e 100644 --- a/LDP/guide/docbook/EVMSUG/create-reg-ug.xml +++ b/LDP/guide/docbook/EVMSUG/create-reg-ug.xml @@ -1,6 +1,3 @@ - - - Creating regions Regions can be created from containers, but they can also be created from other @@ -17,7 +14,7 @@ a certain region manager or because you want the features provided by that region manager. You can also create regions to be compatible with other volume management technologies, such as MD or LVM. For example, if you wanted to make a volume that is compatible with Linux LVM, -you would create a region out of a Linux LVM container and then a comptibility volume from that region. +you would create a region out of a Linux LVM container and then a compatibility volume from that region. Example: create a region @@ -52,7 +49,7 @@ providing instructions to help you complete the following task. Select the freespace region from the container you created in - . + . Verify that the region is named lvm/Sample Container/Freespace. Click Next. @@ -100,7 +97,7 @@ providing instructions to help you complete the following task. Select the freespace region from the container you created - earlier in . Verify that + earlier in . Verify that the region is named lvm/Sample Container/Freespace. @@ -156,4 +153,5 @@ context sensitive menu: - \ No newline at end of file + + diff --git a/LDP/guide/docbook/EVMSUG/create-seg.xml b/LDP/guide/docbook/EVMSUG/create-seg.xml index fb706c98..3b22c36a 100644 --- a/LDP/guide/docbook/EVMSUG/create-seg.xml +++ b/LDP/guide/docbook/EVMSUG/create-seg.xml @@ -1,6 +1,3 @@ - - - Creating segments This chapter discusses when to use segments and how to create them using @@ -9,7 +6,7 @@ different EVMS interfaces. When to create a segment A disk can be subdivided into smaller storage objects called disk segments. A segment manager plug-in provides this capability. Another reason for creating disk segments is to maintain compatibility on a dual boot system where the other operating system requires disk partitions. Before creating a disk segment, you must choose a segment manager plug-in to manage the disk and assign -the segment manager to the disk. An explanation of when and how to assign segment managers can be found in . +the segment manager to the disk. An explanation of when and how to assign segment managers can be found in . @@ -112,7 +109,7 @@ on sde_freespace1. Alternatively, you can perform some of the steps to create a segment from the context sensitive menu: -From the Segments view, press Enter on sde_frespace1. +From the Segments view, press Enter on sde_freespace1. Activate Create Segment. @@ -150,4 +147,5 @@ context sensitive menu: - \ No newline at end of file + + diff --git a/LDP/guide/docbook/EVMSUG/create-snapshot.xml b/LDP/guide/docbook/EVMSUG/create-snapshot.xml index 2128ee6e..439d19da 100644 --- a/LDP/guide/docbook/EVMSUG/create-snapshot.xml +++ b/LDP/guide/docbook/EVMSUG/create-snapshot.xml @@ -1,7 +1,3 @@ - - - - Creating snapshots This chapter discusses snapshotting and tells how to create @@ -20,15 +16,12 @@ same and looks exactly like the original at the time the snapshot was created. -The snapshot feature is very useful for performing data backups. -In order to perform a consistent backup, the volume that is being backed up -should not change while the -backup is running. -This often means the volume must be taken offline during the -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. + +Snapshotting allows you to keep a volume online while a backup is created. +This method is much more convenient than a data backup where a volume +must be taken offline to perform a consistent backup. +When snapshotting, a snapshot of the volume is created and the backup +is taken from the snapshot, while the original remains in active use. @@ -47,9 +40,8 @@ object, which is to make an EVMS volume from the object. The size of this consumed object is the size available to the snapshot object. The snapshot object can be smaller or larger than the original volume. -If the object is smaller, the original volume could fill up -as data is copied from the original to the snapshot, given sufficient -activity on the original. +If the object is smaller, the snapshot volume could fill up as data is copied +from the original to the snapshot, given sufficient activity on the original. In this situation, the snapshot is deactivated and additional I/O to the snapshot fails. @@ -58,7 +50,7 @@ I/O to the snapshot fails. 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. +the larger the snapshot object 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. @@ -66,8 +58,8 @@ 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 +object is the same size as the original volume, or a little larger, +to account for the snapshot mapping tables, the snapshot is never deactivated. @@ -76,8 +68,10 @@ never deactivated. Activating a snapshot After you create a snapshot, activate it by making an EVMS volume from the object. -After you create the volume and save the changes, the snapshot is active. The only -option for activating snapshots is the name to give the EVMS volume. This name can be +After you create the volume and save the changes, the snapshot is active. +The only option you have to specify for activating snapshots is +the name to give the EVMS volume. +This name can be the same as or different than the name of the snapshot object. @@ -126,7 +120,7 @@ it "snap." context sensitive menu: From the Available Objects tab, right click - lvm/Sample Container/Sample Region. + lvm/Sample Container/Sample Region. Click Create Feature Object... Continue creating the snapshot beginning with step 2 of the GUI instructions. You can skip steps 4 and 5 of the GUI instructions. @@ -203,17 +197,182 @@ instructions. Reinitializing a snapshot -Snapshots can be reinitialized, which causes all of the +Snapshots can be reinitialized. Reinitializing 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 original, chunk size, and writeable flags as the original snapshot. -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. +To reinitialize a snapshot, use the Reset +command on the snapshot object +(not the snapshot volume). +This command reinitializes the snapshot without requiring you to +manually delete and recreate the volume. +The snapshot volume must be unmounted for it to be reinitialized. + +This section continues the example from the previous section, +where a snapshot object and volume were created. +The snapshot object is called "snap" and the volume +is called "/dev/evms/snap." + +Using the EVMS GUI or Ncurses +To reinitialize a snapshot, follow these steps: + + Select + + Actions + Other + Storage Object Tasks + + + Select the volume "snap." + Click Next. + Select Reset. + + Click Next. + + Click Reset on the action panel. + + Click Reset on the warning panel. + + + + +Alternatively, you can perform these same steps with the context sensitive menus: + + +From the Feature Objects panel, right click (or press Enter on) +the object snap. + + +Click Reset on the popup menu. +Click Reset on the action panel. +Click Reset on the warning panel. + + + + + +Using the CLI +Follow these steps to reinitialize a snapshot with the CLI: + +Issue the following command to the CLI: +task:reset,snap + +Press Enter to select "Reset" (the default choice) at the warning message. + + + + + + +Expanding a snapshot + +As mentioned in the , as data is +copied from the original volume to the snapshot, the space available +for the snapshot might fill up, causing the snapshot to be invalidated. +This situation might cause your data backup to end prematurely, as the +snapshot volume begins returning I/O errors after it is invalidated. + + + +To solve this problem, EVMS now has the ability to expand the storage +space for a snapshot object while the snapshot volume is active and mounted. +This feature allows you to initially create a small snapshot object and expand +the object as necessary as the space begins to fill up. + + + +In order to expand the snapshot object, the underlying object must +be expandable. +Continuing the example from the previous sections, the object "snap" is +built on the LVM region lvm/Sample Container/Sample Region. +When we refer to expanding the "snap" object, the region +lvm/Sample Container/Sample Region is the +object that actually gets +expanded, and the object "snap" simply makes use of the new space on +that region. +Thus, to have expandable snapshots, you will usually want to build +your snapshot objects on top of LVM regions that have extra freespace +available in their LVM container. DriveLink objects and some disk +segments also work in certain situations. + + + +One notable quirk about expanding snapshots is that the snapshot +object and volume do not actually appear to expand after the operation +is complete. +Because the snapshot volume is supposed to be a frozen image of the original +volume, the snapshot volume always has the same size as the original, +even if the snapshot has been expanded. +However, you can verify that the snapshot object is using the +additional space by displaying the details for the snapshot object +and comparing the percent-full field before and after the expand operation. + +Using the EVMS GUI or Ncurses + +To create the snapshot using the GUI or Ncurses, follow these steps: + + Select + + Actions + Expand + Volume + + to see a list of EVMS feature objects. + + Select the volume /dev/evms/snap. + Click Next. + Select lvm/Sample Container/Sample Region. + This object is the object that will actually be expanded. + + Click Next. + + Select the options for expanding the LVM region, + including the amount of extra space to add to the region. + + + Click Expand. + + + + +Alternatively, you can perform the same steps using the context sensitive menus. + + +From the Volumes panel, right click (or press Enter on) +/dev/evms/snap. + + +Select Expand from the popup menu. +Click Next. +Select the region lvm/Sample Container/Sample Region. This is the object that will +actually be expanded. +Click Next. +Select the options for expanding the LVM region, including the +amount of extra space to add to the region. + +Click Expand. + + + +Using the CLI +The CLI expands volumes by targeting the object to be +expanded. +The CLI automatically handles expanding the volume and other objects above the volume +in the volume stock. As with a regular expand operation, the options are determined +by the plug-in that owns the object being expanded. +Issue the following command to determine the expand options for the +region lvm/Sample Container/Sample Region: +query:region,region="lvm/Sample Container/Sample Region",lo +The option to use for expanding this region is called "add_size." +Issue the following command to expand the snapshot by 100 MB: +expand:"lvm/Sample Container/Sample Region", add_size=100MB + + + Deleting a snapshot @@ -239,12 +398,75 @@ snapshot. If the testing is successful, you can then roll back the snapshot to original and effectively install the software on the regular system. If there is a problem during the testing, you can simply delete the snapshot without harming the original volume. -Rollback can only be performed when both the snapshot and the original volumes -are unmounted and otherwise not in use. Rollback can also be performed only when -there is only a single snapshot of an original. If an original has multiple snapshots, -all but the desired snapshot must be deleted before rollback can take place. +You can perform a rollback when the following conditions are met: + + + + +Both the snapshot and the original volumes +are unmounted and otherwise not in use. + + + + +There is only a single snapshot of an original. + +If an original has multiple snapshots, +all but the desired snapshot must be deleted before rollback can take place. + + + + No options are available for rolling back snapshots. + +Using the EVMS GUI or Ncurses +Follow these steps to roll back a snapshot with the EVMS GUI or Ncurses: + + +Select +Actions +Other +Storage Object Tasks. + +Select the object "snap." +Click Next. +Select Rollback. +Click Next. +Click Rollback on the action panel. + +Click Rollback on the warning panel. + + + +Alternatively, you can perform these same steps with the context sensitive menus: + +From the Feature Objects panel, right click (or press +Enter on) the object "snap." + +Click Rollback on the popup menu. + +Click Rollback on the action panel. + +Click Rollback on the warning panel. + + + + + +Using the CLI +Follow these steps to roll back a snapshot with the CLI: + +Issue the following command to the CLI: +task:rollback,snap + +Press Enter to select "Rollback" (the default choice) at the warning message. + + + + + - \ No newline at end of file + + diff --git a/LDP/guide/docbook/EVMSUG/createvol-ug.xml b/LDP/guide/docbook/EVMSUG/createvol-ug.xml index 2139783b..6c85c1d6 100644 --- a/LDP/guide/docbook/EVMSUG/createvol-ug.xml +++ b/LDP/guide/docbook/EVMSUG/createvol-ug.xml @@ -1,7 +1,3 @@ - - - - Creating volumes This chapter discusses when and how to create volumes. @@ -21,13 +17,13 @@ become a volume; it must be made into a volume. EVMS native volumes contain EVMS-specific information to identify the name and minor number. After this volume information is - applied, the volume is no longer fully backwards compatible + applied, the volume is no longer fully backward compatible with existing volume types. Instead of adding EVMS metadata to an existing object, you can tell EVMS to make an object directly available as a volume. This type of volume is known as a compatibility volume. Using this method, the final product is fully - backwards-compatible with the desired system. + backward-compatible with the desired system. Example: create an EVMS native volume @@ -37,7 +33,7 @@ become a volume; it must be made into a volume.
Create an EVMS native volume -Create an EVMS native volume called "Sample Volume" from the region, /lvm/Sample Container/Region, you created in .
+Create an EVMS native volume called "Sample Volume" from the region, /lvm/Sample Container/Region, you created in . Using the EVMS GUI @@ -116,7 +112,7 @@ from the context sensitive menu:
Create a compatibility volume Create a compatibility volume called "Sample Volume" from - the region, /lvm/Sample Container/Region, you created in .
+ the region, /lvm/Sample Container/Region, you created in . Using the GUI To create a compatibility volume, follow these steps: @@ -179,7 +175,7 @@ the context sensitive menu: Using the CLI To create a volume, use the Create command. The arguments - the Create cocmmand accepts vary depending on what is being created. In + the Create command accepts vary depending on what is being created. In the case of the example, the first argument is the key word that specifies what is being created. The second argument is the object being made into a volume, in this case . @@ -192,4 +188,5 @@ the context sensitive menu: - \ No newline at end of file + + diff --git a/LDP/guide/docbook/EVMSUG/deleterecurs-ug.xml b/LDP/guide/docbook/EVMSUG/deleterecurs-ug.xml index dc151aba..5eb93aea 100644 --- a/LDP/guide/docbook/EVMSUG/deleterecurs-ug.xml +++ b/LDP/guide/docbook/EVMSUG/deleterecurs-ug.xml @@ -1,9 +1,9 @@ -Destroying EVMS objects +Deleting objects -This chapter tells how to destroy EVMS objects through the delete and +This chapter tells how to delete EVMS objects through the delete and delete recursive operations. @@ -162,4 +162,4 @@ continuing with these steps) enter the following to destroy the container and ev - \ No newline at end of file + diff --git a/LDP/guide/docbook/EVMSUG/displaydetails-ug.xml b/LDP/guide/docbook/EVMSUG/displaydetails-ug.xml index ddafd794..aabee4f3 100644 --- a/LDP/guide/docbook/EVMSUG/displaydetails-ug.xml +++ b/LDP/guide/docbook/EVMSUG/displaydetails-ug.xml @@ -1,6 +1,3 @@ - - - Obtaining interface display details The EVMS interfaces let you view more detailed information about an EVMS object than @@ -22,7 +19,7 @@ to volume /dev/evms/Sample Volume. Alternatively, look at Right click lvm/Sample Container/Sample Region. -Point at Display Details... and left click. A new window opens +Point at Display Details... and click. A new window opens with additional information about the selected region. Click More by the Logical Extents box. Another window opens that displays the mappings of logical extents to physical extents. @@ -84,4 +81,5 @@ by commas. For example, if you wanted additional information about logical exte query: extended info, "lvm/Sample Container/Sample Region", Extents - \ No newline at end of file + + diff --git a/LDP/guide/docbook/EVMSUG/fsimops-ug.xml b/LDP/guide/docbook/EVMSUG/fsimops-ug.xml index 3cb51db5..9f1356fb 100644 --- a/LDP/guide/docbook/EVMSUG/fsimops-ug.xml +++ b/LDP/guide/docbook/EVMSUG/fsimops-ug.xml @@ -1,6 +1,3 @@ - - - FSIMs and file system operations 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. @@ -23,8 +20,7 @@ The JFS module supports the IBM journaling file system (JFS). Current support includes mkfs, unmkfs, -fsck, and online file system expansion. -Support for external logging will be added in a future release of EVMS. +fsck, and online file system expansion. 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 @@ -32,7 +28,7 @@ from the JFS for Linux site. -For more information on the JFS FSIM, refer to . +For more information on the JFS FSIM, refer to . @@ -45,7 +41,7 @@ Command support includes mkfs, unmkfs, -For more information on the XFS FSIM, refer to . +For more information on the XFS FSIM, refer to . @@ -61,7 +57,7 @@ System Venture (Namesys) web site. -For more information on the ReiserFS FSIM, refer to . +For more information on the ReiserFS FSIM, refer to . @@ -73,7 +69,7 @@ The FSIM supports mkfs, unmkfs, -For more information on the Ext2/3 FSIM, refer to . +For more information on the Ext2/3 FSIM, refer to . @@ -282,7 +278,7 @@ use, look at the results of the following query: Scroll down using the down arrow until - Vebose Output is highlighted. + Verbose Output is highlighted. Press Spacebar to change Verbose Output to Yes. @@ -324,3 +320,4 @@ instructions. + diff --git a/LDP/guide/docbook/EVMSUG/install-ug.xml b/LDP/guide/docbook/EVMSUG/install-ug.xml index 8fca1438..17bab528 100644 --- a/LDP/guide/docbook/EVMSUG/install-ug.xml +++ b/LDP/guide/docbook/EVMSUG/install-ug.xml @@ -1,7 +1,3 @@ - - - - Downloading and installing EVMS This chapter tells how to obtain and install EVMS, and offers guidelines to help you make decisions about your EVMS installation. If you are setting up EVMS to work in a cluster, execute the steps described in this chapter on each of the nodes in the cluster. @@ -91,14 +87,14 @@ patch -p1 < /src/src/evms-2.0.0/kernel/2.4.20/7-vfs-lock.patchIf you are using an Xwindow system, the following window opens.
xconfig Window - + xconfig Window
To enable the kernel components that EVMS needs, select Multi-device support (RAID and LVM). The following window opens.
Multi-device Support (RAID and LVM) Window - + MD Support (RAID and LVM) Window
NOTE @@ -115,7 +111,8 @@ patch -p1 < /src/src/evms-2.0.0/kernel/2.4.20/7-vfs-lock.patch NOTE -The options you select in this step are the ones you selected in . +The options you select in this step are the ones you selected in +. @@ -175,7 +172,7 @@ patch -p1 < /src/src/evms-2.0.0/kernel/2.4.20/7-vfs-lock.patchNOTE If you installed your kernel as modules, skip to - . + . Reboot your machine and choose the new kernel image to run with EVMS support. @@ -445,7 +442,7 @@ An initial ramdisk is a ram-based device that acts as a temporary root file system at boot time. The initial ramdisk lets EVMS run programs and load modules that are necessary to activate the true root file system. -For instructions on building an init-ramdisk for use with EVMS, see . +For instructions on building an init-ramdisk for use with EVMS, see . Setting up clustered EVMS The following steps show how to set up EVMS clustering. Perform these steps on @@ -461,7 +458,7 @@ line to configure CCM: channel, create the following fifo with administrative privileges: mkfifo /var/lib/heartbeat/api/evms.req mkfifo /var/lib/heartbeat/api/evms.rsp -chgrp haclient /var/lib/heartbeate/api/evms.req +chgrp haclient /var/lib/heartbeat/api/evms.req chgrp haclient /var/lib/heartbeat/api/evms.rsp chmod 200 /var/lib/heartbeat/api/evms.req chmod 600 /var/lib/heartbeat/api/evms.rsp @@ -477,7 +474,7 @@ the command. -See for information about clustering +See for information about clustering operations. @@ -486,4 +483,5 @@ operations. - \ No newline at end of file + + diff --git a/LDP/guide/docbook/EVMSUG/over-ug.xml b/LDP/guide/docbook/EVMSUG/over-ug.xml index c500b1a8..b5d76ffb 100644 --- a/LDP/guide/docbook/EVMSUG/over-ug.xml +++ b/LDP/guide/docbook/EVMSUG/over-ug.xml @@ -1,8 +1,3 @@ - - - - - What is EVMS? EVMS brings a new model of volume management to Linux®. @@ -42,11 +37,11 @@ be highly available from different nodes in the cluster. There are currently three user interfaces available for EVMS: graphical (GUI), text mode (Ncurses), and the Command Line Interpreter (CLI). Additionally, you can use the EVMS Application Programming Interface to implement your own customized user interface. - tells more about each of the EVMS user interfaces. + tells more about each of the EVMS user interfaces.
EVMS user interfaces - + User interface Typical user Types of use @@ -131,7 +126,7 @@ Additionally, you can use the EVMS Application Programming Interface to implemen Shared storage container 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. + by all nodes of the cluster simultaneously. @@ -148,7 +143,7 @@ Additionally, you can use the EVMS Application Programming Interface to implemen bad block relocation. An EVMS Native Feature is a function of volume management designed and implemented by - EVMS. These features are not intended to be backwards compatible with other + EVMS. These features are not intended to be backward compatible with other volume management technologies. @@ -336,4 +331,5 @@ other volume management systems. - \ No newline at end of file + + diff --git a/LDP/guide/docbook/EVMSUG/pref-ug.xml b/LDP/guide/docbook/EVMSUG/pref-ug.xml index a18d2295..ffce81de 100644 --- a/LDP/guide/docbook/EVMSUG/pref-ug.xml +++ b/LDP/guide/docbook/EVMSUG/pref-ug.xml @@ -1,8 +1,5 @@ - - - Preface -This guide tells how to install, configure, and manage Enterprise +This guide tells how to configure and manage Enterprise Volume Management System (EVMS). EVMS is a storage management program that provides a single framework for managing and administering your system's storage. @@ -19,63 +16,64 @@ web site.
Organization of the EVMS User Guide - + Chapter or appendix title Contents1. What is EVMS? Discusses general EVMS concepts and terms. -2. Downloading and installing EVMS -Tells how to access and install EVMS and configure it for use on your system. -3. Using the EVMS interfaces +2. Using the EVMS interfaces Describes the three EVMS user interfaces and how to use them. -4. The EVMS log file and error data collection +3. The EVMS log file and error data collection Discusses the EVMS information and error log file and explains how to change the logging level. -5. Viewing compatibility volumes after migrating +4. Viewing compatibility volumes after migrating Tells how to view existing files that have been migrated to EVMS. -6. Obtaining interface display details +5. Obtaining interface display details Tells how to view detailed information about EVMS objects. -7. Assigning a segment manager -Discusses segments and explains how to assign a segment manager. -8. Creating segments +6. Adding and removing a segment manager +Discusses segments and explains how to add and remove a segment manager. +7. Creating segments Explains when and how to create segments. -9. Creating containers +8. Creating containers Discusses containers and explains when and how to create them. -10. Creating regions +9. Creating regions Discusses regions and explains when and how to create them. -11. Creating drive links +10. Creating drive links Discusses the drive linking feature and tells how to create a drive link. -12. Creating snapshots +11. Creating snapshots Discusses snapshotting and tells how to create a snapshot. -13. Creating volumesExplains when and how to create volumes. -14. FSIMS and file system operations +12. Creating volumesExplains when and how to create volumes. +13. FSIMs and file system operations Discusses the standard FSIMs shipped with EVMS and provides examples of adding file systems and coordinating file checks with the FSIMs. -15. Clustering operationsDescribes EVMS clustering and how to create private and shared containers. -16. Converting volumes +14. Clustering operationsDescribes EVMS clustering and how to create private and shared containers. +15. Converting volumes Explains how to convert EVMS native volumes to compatibility volumes and compatibility volumes to EVMS native volumes. -17. Expanding and shrinking volumesTells how to expand and shrink EVMS volumes with the various EVMS user interfaces. -18. Adding features to an existing volume +16. Expanding and shrinking volumesTells how to expand and shrink EVMS volumes with the various EVMS user interfaces. +17. Adding features to an existing volume Tells how to add additional features, such as drive linking and bad block relocation, to an existing volume. -19. Plug-in operations tasks +18. Plug-in operations tasks Discusses the plug-in tasks that are available within the context of a particular plug-in. -20. Destroying EVMS objectsTells how to safely destroy EVMS objects. -A. Building an init-ramdisk to use with EVMS -Explains the steps necessary to build a ram-based device that acts a temporary root file system at boot time. -B. The DOS link plug-in +19. Deleting objectsTells how to safely delete EVMS objects. +20. Replacing objectsTells how to change the +configuration of a volume or storage object. +21. Moving segment storage objectsDiscusses how to use +the move function for moving segments. +A. The DOS link plug-in Provides details about the DOS link plug-in, which is a segment manager plug-in. -C. The MD region manager +B. The MD region manager Explains the Multiple Disks (MD) support in Linux that is a software implementation of RAID. -D. The LVM plug-in +C. The LVM plug-in Tells how the LVM plug-in is implemented and how to perform container operations. -E. The CSM plug-in +D. The CSM plug-in Explains how the Cluster Segment Manager (CSM) plug-in is implemented and how to perform CSM operations. -F. JFS file system interface module +E. JFS file system interface module Provides information about the JFS FSIM. -G. XFS file system interface module +F. XFS file system interface module Provides information about the XFS FSIM. -H. ReiserFS file system interface module +G. ReiserFS file system interface module Provides information about the ReiserFS FSIM. -I. Ext-2/3 file system interface module +H. Ext-2/3 file system interface module Provides information about the Ext-2/3 FSIM.
- \ No newline at end of file + +