diff --git a/LDP/guide/docbook/EVMSUG/EVMSUG.xml b/LDP/guide/docbook/EVMSUG/EVMSUG.xml index e0d5bed7..de20af45 100644 --- a/LDP/guide/docbook/EVMSUG/EVMSUG.xml +++ b/LDP/guide/docbook/EVMSUG/EVMSUG.xml @@ -1,30 +1,41 @@ - + - + + - + + + + + + + + + + + + + + + + + + + ]> - + EVMS User Guide Joy @@ -32,13 +43,16 @@ IBM Kylie Smith +IBM +Christine +Lorenz IBM -October 21, 2002 +March 31, 2003 -2002 +2003 IBM @@ -46,9 +60,10 @@ The following terms are registered trademarks of International Business Machines corporation in the United States and/or other countries: AIX, OS/2, System/390. A full list of U.S. trademarks owned by IBM may be found at http://www.ibm.com/legal/copytrade.shtml. Intel is a trademark or registered trademark of Intel Corporation in the United States, other countries, or both. -Windows is a trademark of Microsoft Corporation in the United States, other countries or both. +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. This document is provided "AS IS," with no express or implied warranties. Use the information in this document at your own risk. @@ -57,31 +72,35 @@ &evmsugpref; + &evmsugchap1; &evmsuginstall; -&evmsuglocating; &evmscmuse; +&evmsdebuglog; &evmsmigrate; +&evmsdisplaydetails; &evmsassignseg; &evmscreateseg; &evmscreatecont; &evmscreatereg; +&evmsdrivelinking; +&evmssnapshotting; &evmscreatevol; +&evmsfsimops; +&evmsclusterops; &evmsconvert; - +&evmsexpandshrink; +&addfeatures; +&evmsplugintasks; +&evmsdeleterecursive; +&evmsinitram; +&evmsdos; +&evmsmd; +&evmslvm; +&evmscsm; +&evmsjfsfsim; +&evmsxfsfsim; +&evmsreiserfsim; +&evmsext23fsim; - - - - - - - - - - - - - - diff --git a/LDP/guide/docbook/EVMSUG/assignseg-ug.xml b/LDP/guide/docbook/EVMSUG/assignseg-ug.xml index e96d8ac6..25e5944c 100644 --- a/LDP/guide/docbook/EVMSUG/assignseg-ug.xml +++ b/LDP/guide/docbook/EVMSUG/assignseg-ug.xml @@ -1,11 +1,20 @@ -Assigning a Segment Manager + + + + + + +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 +When to assign a segment manager Assigning a segment manager to a disk allows the disk to be subdivided into - smaller storage objects called disk segments. The assign command causes a - segment manager to create appropriate metadata and expose freespace that the segment manager - finds on the disk. You will need to assign segment managers when you have a new disk or - when you are switching from one partitioning sheme to another. + smaller storage objects called disk segments. The + assign 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 + have a new disk or + when you are switching from one partitioning scheme to another. EVMS displays disk segments as the following types: Data: a set of contiguous sectors that has been allocated from a disk and can be used to construct a volume or object. @@ -17,8 +26,8 @@ information needed by the segment manager. -Types of Segment Managers - There are three types of segment managers in EVMS: DOS, GPT, and S/390. +Types of segment managers + There are five types of segment managers in EVMS: DOS, GPT, S/390, Cluster, and BSD. DOS Segment Manager The most commonly used segment manager is the DOS Segment Manager. This plug-in @@ -80,62 +89,105 @@ capable of understanding the unique S/390 disk layouts. The S/390 Segment Manager cannot be assigned or unassigned 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: -Assigning a Segment Manager to an Existing Disk - When you assign a segment manager to a disk, the segment manager will need to change the basic - layout of the disk. This change means that some sectors will be reserved for metadata and the remaining sectors will - be 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 - segment manager to an existing disk, you must remove any existing volume management structures including any - previous segment manager. + +provides a unique disk ID (guid) +names the EVMS container the disk will reside within +specifies the cluster node (nodeid) that owns the disk +specifies the HA cluster (clusterid) + + +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 objects +discovered by the CSM and belonging to the same container. These shared storage +objects are consumed by the container. A single segment object is produced by the +container for each consumed storage object. A failover of the EVMS resource is then +accomplished by simply reassigning the container to the standby cluster node and +having that node re-run its discovery process. + + +BSD segment manager +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. + -Assigning a Segment Manager to a New Disk +Assigning a segment manager to an existing disk + When you assign 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 + 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 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 will show up in EVMS as a compatibility volume because + 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 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 will show up in EVMS with storage objects that + 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 - segment manager to the disk, and you will lose any old data. + segment manager to the disk, and you lose any old data. -Working through an Example -This section provides a detailed explanation of how to assign a segment manager with EVMS by -working through the scenario below. +Example: assign a segment manager +This section shows how to assign +a segment manager with EVMS. 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 sde. This disk contains no data and has not been subdivided (no partitions). EVMS assumes that this + physical disks it sees as volumes. Assume that you have added a new + disk to the system that EVMS + sees as sde. + This disk contains no data and has not been subdivided + (no partitions). EVMS assumes that this disk is a compatibility volume known as /dev/evms/sde.
Assign the DOS Segment Manager -Assign the DOS Segment Manager to disk sde.
+Assign the DOS Segment Manager to disk sde. NOTE -In the example above, the DOS Segment +In the following example, the DOS Segment Manager creates two segments on the disk: - a metadata segment known as sde_mbr, and a + a metadata segment known as sde_mbr, and a segment to represent the available space on - the drive, sde_freespace1. This freespace - segment (sde_freespace1) can be divided into + the drive, sde_freespace1. This freespace + segment (sde_freespace1) can be + divided into other segments because it represents space on - the drive that is not in use. + the drive that is not in use. Using the EVMS GUI -To assign the DOS Segment Manager to sde, you will first need to remove the volume, /dev/evms/sde: +To assign the DOS Segment Manager to sde, first +remove the volume, /dev/evms/sde: Select Actions @@ -145,8 +197,14 @@ working through the scenario below. Click Delete. +Alternatively, you can remove the volume through the GUI context sensitive menu: -Once the volume is removed, assign the DOS Segment Manager: + +From the Volumes tab, right click /dev/evms/sde. +Click Delete. + + +After the volume is removed, assign the DOS Segment Manager: Select Actions @@ -161,26 +219,35 @@ working through the scenario below. Using Ncurses -To assign the DOS Segment Manager to sde, you will first need to remove the volume, /dev/evms/sde. -Press 2 to view volumes. -Highlight /dev/evms/sde by using the up -and down arrow keys. Press the Enter key. -Highlight Delete Volume. Press the Enter key. -Highlight Delete. Press the Enter key. +To assign the DOS Segment Manager to sde, first remove the +volume /dev/evms/sde: + +Select ActionsDelete +Segment Manager to Storage Object. +Select /dev/evms/sde. +Activate Delete. -Once the volume is removed, assign the DOS Segment Manager: +Alternatively, you can remove the volume through the context sensitive menu: -Press 4 to switch views. -Highlight Logical Disk. Press the Enter key. -Press the Enter key to see the context sensitive menu. -Highlight Assign Segment Manager to Disk. -Press the Enter key. -Highlight DOS Segment Manager. Press the Enter key. -Highlight sde. Press the spacebar -to select then press the Enter key to continue. -Press the Enter key to select the default settings. +From the Logical Volumes view, press Enter on +/dev/evms/sde. + +Activate Delete. + + + + +After the volume is removed, assign the DOS Segment Manager: + +Select ActionsAdd +Segment Manager to Storage Object +Select DOS Segment Manager. +Activate Next. +Select sde. + +Activate Add. @@ -197,29 +264,9 @@ volume and is available for use: Assign:DosSegMgr={},sde - - - - - - - - - - - - - - - - - - - - - + \ 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 e95a2547..15db88be 100644 --- a/LDP/guide/docbook/EVMSUG/cmuse-ug.xml +++ b/LDP/guide/docbook/EVMSUG/cmuse-ug.xml @@ -1,15 +1,26 @@ -Using the EVMS Interfaces -The following chapter explains how to use the EVMS GUI, Ncurses, CLI interfaces, and the EVMS emulation of the Linux LVM command set . This section includes basic navigation and commands. + + + + + + + +Using the EVMS interfaces +This chapter explains how to use the EVMS GUI, Ncurses, and CLI interfaces. +This chapter also +includes information about basic navigation and commands available through +the CLI. EVMS GUI - The EVMS GUI provides you with a flexible and easy-to-use - interface to administer volumes and storage objects. Many users will find the EVMS GUI easy to use because it checks which - storage objects, actions, and plug-ins are acceptable for each - task. + The EVMS GUI is a flexible and easy-to-use + interface for administering volumes and storage objects. + Many users find the EVMS GUI easy to use because it displays which + storage objects, actions, and plug-ins are acceptable for a + particular task. - Using Context Sensitive and Action Menus - In the EVMS GUI you can accomplish most - tasks in one of two ways: context sensitive menus and the + Using context sensitive and action menus + The EVMS GUI lets you accomplish most + tasks in one of two ways: context sensitive menus or the Actions menu. Context sensitive menus are available from any @@ -17,26 +28,28 @@ page in a notebook widget located on the EVMS GUI main window. These views are made up of different trees or lists that visually represent the organization of - different object types, such as volumes, + different object types, including volumes, feature objects, regions, containers, segments, or disks. You can view the context sensitive menu for an object by right-clicking on that object. The actions that are available - for that object will appear on - the screen. The GUI will present only actions that are acceptable - for that object at that point in the process. These actions will not always be a complete set. + for that object display on + the screen. The GUI will only present actions that are + acceptable for the selected object at that point in the + process. These actions are not always a complete set. - To use the Actions menu + To use the Actions menu, choose Action <the action you want to accomplish> <options>. - The Actions menu provides a more guided path to - completing a task than context sensitive menus do. The - Actions option is similar to the popular wizard or druid - approach used by many GUI applications. + The Actions menu + provides a more guided path for + completing a task than do context sensitive menus. The + Actions option is similar to the + wizard or druid approach used by many GUI applications. All of the operations you need to perform as an administrator are available through @@ -45,108 +58,248 @@ - Saving Changes - All changes you make while in the EVMS + Saving changes + All of the changes that you make while in the EVMS GUI are only in memory until you save the changes. In order to make your changes permanent, you must save all changes before exiting. If you forget to save the changes and decide to exit or close the - EVMS GUI, you will be reminded about - saving any pending changes. + EVMS GUI, you are reminded to save any + pending changes. - To explicitly save all changes you + To explicitly save all the changes you made, select Action Save, and click the Save button. -Refreshing Changes -The Refresh button updates the view but does not cause a rediscover. Clicking -the Refresh button allows you to see changes, like mount points, that you might have mounted outside of the GUI. +Refreshing changes +The Refresh button updates the view and allows +you to see changes, like mount points, that might have changed outside of +the GUI. + +Using the GUI "+" +Along the left hand side of the panel views in the GUI is a "+" that resides +beside each item. When you click the "+," the objects that are included +in the item are displayed. If any of the objects that display also have a "+" beside them, you can expand them further by clicking on the "+" next to each object name. + + +Using the accelerator keys + +You can avoid using a mouse for navigating the EVMS GUI by using a series of +key strokes, or "accelerator keys," instead. The following sections tell how to use +accelerator keys in the EVMS Main Window, the Selection Window, and the Configuration +Options Window. + +Main Window accelerator keys + +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. +Down arrow and Spacebar +Bring keyboard focus into the view.
+ + + +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. +"-"Collapses an object tree. +ENTERBrings up the context menu (on a row). +ArrowsNavigate a context menu. +ENTERActivates an item. +ESCDismisses the context menu. +TabGets you out of the view and moves you back up to the notebook tab. + +
+ + + + +To access the action bar menu, press Alt and +then the underlined +accelerator key for the menu choice (for example, "A" for the +Actions +dropdown menu). + + +In a dropdown menu, you can use the up and down arrows +to navigate. You could also just type the accelerator key for the menu +item, which is the character with the underscore. For example, to initiate +a command to delete a container, type Alt + "A" + "D" + "C." + + +Ctrl-S is a shortcut to initiate saving changes. +Ctrl-Q is a shortcut to initiate quitting the EVMS GUI. + + + + + + +Accelerator keys in the selection window + +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. +SpacebarSelects and deselects items in the selection list. +Enter on the button or type the accelerator character (if one exists)Activates a button + +
+ + + + + +Configuration options window accelerator keys + + +Use the following keys to navigate in the configuration options window: + +Accelerator keys in the configuration options window + + +TabCycles focus between fields and buttons +Left and right arrowsNavigate the folder tabs if the window has a widget notebook. +Spacebar or the down arrowSwitches focus to a different notebook page. +Enter or type the accelerator character (if one exists)Activates a button + +
+ + + +For widgets, use the following keys to navigate: + +Widget navigation keys in the configuration options window + + +TabCycles forward through a set of widgets +Shift-TabCycles backward through a set of widgets. + +
+ + + + +The widget navigation, selection, and activation is the same in all dialog +windows. + + + + + + + + - EVMS Ncurses Interface - The EVMS Ncurses (evmsn) user interface provides a menu driven - interface with similar characteristics to the EVMS GUI. Like the EVMS GUI, - evmsn can accommodate new plug-ins and features without requiring any code + EVMS Ncurses interface + The EVMS Ncurses (evmsn) user interface is a menu-driven + interface with characteristics similar to those of the EVMS GUI. + Like the EVMS GUI, + evmsn can accommodate new plug-ins and features without requiring any code changes. - The availability of an EVMS Ncurses user interface + The EVMS Ncurses user interface allows you to manage volumes on systems that do not have the X and GTK+ libraries that are required by the EVMS GUI. Navigating through EVMS Ncurses The EVMS Ncurses user interface initially displays a list of logical volumes similar to the - logical volumes view in the EVMS GUI. + logical volumes view in the EVMS GUI. Ncurses also provides + a menu bar similar to the menu bar in the EVMS GUI. A general guide to navigating through the layout of the - Ncurses screen is listed below: + Ncurses window is listed below: - A menu of key-to-action mappings is - listed at the bottom of the screen. + Tab cycles you through the available + views. - The 2 key returns you to the - volumes view. + Status messages and tips are displayed on + the last line of the screen. - The 4 key displays a menu of - other views you could switch - to. + Typing the accelerator character (the + letter highlighted in red) for any menu item activates + that item. For example, typing A in any view brings + down the Actions menu. - The 5 key saves changes made - during an evmsn session. + Typing A + Q in a view + quits the application. - The 9 key exits Ncurses. + Typing A + S in a view + saves changes + made during an evmsn session. - Status messages and user - prompts appear on a line located - between the window frame for the current view and the action - keys menu line. + Use the up and down + arrows to highlight an object in a view. Pressing + Enter while an object in a view is + highlighted presents a context popup menu. - You can select which actions to - perform by using the up and - down arrow keys to highlight - an object within the current view. After the - correct item is highlighted, press the Enter - key. Ncurses will typically provide a context - sensitive sub-menu of available actions. - - When navigating from one menu - to another, the Esc (escape) key will return - you to the previous menu. + Dismiss a context popup menu by pressing + Esc or by selecting a menu item with the + up and down arrows and pressing + Enter to + activate the menu item. - Ncurses allows you to create new - objects based on your current view. For example, a container can be created - in the Storage Containers view by selecting any - container. If the view - is empty, you can still create a container by pressing the - Enter key on the - "No Storage Containers found" row. - - In order to change or set an option value - within the configuration options menu, use the spacebar key to - select the value. Press - Enter when you are finished. In order to - complete most operations you must press Enter. + Dialog windows are similar in design to the EVMS GUI +dialogs, which allow a user to navigate forwards and backwards through a series +of dialogs using Next and Previous. A general +guide to dialog windows is listed below: + +Tab cycles you through the available buttons. Note +that some buttons might not be available until a valid selection is made. + +The left and right arrows can also be used +to move to an available button. + +Navigate a selection list with the up and +down arrows. + +Toggle the selection of an item in a list with spacebar. + +Activate a button that has the current focus with Enter. If the button has +an accelerator character (highlighted in red), you can also activate the button +by typing the accelerator character regardless of whether the button has the current +focus. + + +The EVMS Ncurses user interface, like the EVMS GUI, provides context menus +for actions that are available only to the selected object in a view. Ncurses also provides +context menus for items that are +available from the Actions menu. These context menus present +a list of commands available for a certain object. - Saving Changes + Saving changes All changes you make while in the EVMS Ncurses are only in memory until you save the changes. - In order to make your changes permanent, you must save + In order to make the changes permanent, save all changes before exiting. If you - forget to save the changes and decide to exit or close the - EVMS Ncurses, you will be reminded about - saving any pending changes. + forget to save the changes and decide to exit the EVMS Ncurses + interface, you will be reminded of the unsaved changes and + be given the chance to save or discard the changes before exiting. - To explicitly save all changes you - made, press the 5 key and confirm + To explicitly save all changes, press A + S and confirm that you want to save changes. @@ -156,54 +309,60 @@ the Refresh button allows you to see changes, like mount EVMS Command Line Interpreter The EVMS Command Line Interpreter (EVMS CLI) provides a - command-driven user interface for EVMS. The EVMS CLI is - designed to help automate volume management tasks. For - situations where the EVMS GUI is not available, the EVMS CLI - provides an interactive mode. + command-driven user interface for EVMS. The EVMS CLI + helps automate volume management tasks + and provides an interactive mode in situations where the + EVMS GUI is not available. Because the EVMS CLI is an interpreter, it operates differently than command line utilities for the operating system. The options you specify - on the EVMS CLI command line used to invoke the EVMS + on the EVMS CLI command line to invoke the EVMS CLI control how the EVMS CLI operates. For example, the - command line options tell the CLI where to go for commands to interpret and how - often the EVMS CLI should commit changes to disk. + command line options tell the CLI where to go for commands to + interpret and how + often the EVMS CLI must commit changes to disk. When invoked, the EVMS CLI prompts for commands. The volume management commands the EVMS CLI understands - are specified in the /usr/src/evms-1.2.0/engine/UserInterface/commandline/grammar.ps + are specified in the /usr/src/evms-1.9.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 the EVMS - CLI itself. + man page, and help on these commands is available from within the EVMS + CLI. Using the EVMS CLI Use the evms command to start the EVMS CLI. If you do not enter an option with - evms, the EVMS CLI will start in + evms, the EVMS CLI starts in interactive mode. In interactive mode, the EVMS CLI prompts - you for commands. The results of each command are saved - to disk immediately. The EVMS CLI will exit when you type exit. + you for commands. The result of each command is immediately saved + to disk. The EVMS CLI exits when you type exit. You can modify this behavior by using the following options with evms: - + -b + This option indicates that you are running in + batch mode and anytime there is a prompt for input from the user, + the default value is accepted automatically. This is the + default behavior with the -f option. -c This option commits changes to disk only when EVMS CLI exits, not after - each command. + each command. -f filename This option tells the EVMS CLI to use filename as the source of - commands. The EVMS CLI will exit, when it reaches the + commands. The EVMS CLI exits when it reaches the end of filename. -p - This option parses commands only, - which means that the commands are not actually - executed. When combined with the -f option, the -p option - can be used to catch syntax errors in command files. + This option only parses commands; it does + not execute them. + When combined with the -f option, the + -p option detects syntax errors in + command files. -h This option displays help information for options used with the evms @@ -221,41 +380,41 @@ the Refresh button allows you to see changes, like mount numbers (starting with 1) as they are encountered on the command line. Substitutions are not made within comments or quoted strings. - An example would be : + An example would be: evms -c -f testcase -rl sda sdb - where is the replacement for parameter1 and + + + is the replacement for parameter1 and is the replacement for parameter2 NOTE - Information on less commonly used options is available in the EVMS man - page. + Information on less commonly used options is available + in the EVMS man page. - When the EVMS CLI has been invoked, it processes - the commands or command file you provide. - Notes on Commands and Command Files + Notes on commands and command files - The EVMS CLI allows multiple commands to appear - on a command line. When using multiple commands on a - single command line, the commands must be separated by - a colon ( : ) . This is + The EVMS CLI allows multiple commands to be displayed + on a command line. When you specify multiple commands on a + single command line, separate the commands with + a colon ( : ). This is important for command files because the EVMS CLI sees a command file as a single long command line. The EVMS CLI has no concept of lines in the file and ignores spaces. These features allow a command in a command file to span several lines and use whatever - indentation, or margins that are convenient. The only - requirement is that the command separator (the colon) appear + indentation or margins that are convenient. The only + requirement is that the command separator (the colon) be present between commands. - The EVMS CLI ignores spaces unless the spaces - appear within quote marks. Any name that contains - spaces or other non-printable or control characters - should be placed in quotation marks. If the name + The EVMS CLI ignores spaces unless they + occur within quote marks. Place in quotation marks a name that contains + spaces or other non-printable or control characters. If the name contains a quotation mark as part of the name, the - quotation mark must be "doubled" as in the following example: + quotation mark must be "doubled," as shown in the following + example: "This is a name containing ""embedded"" quote marks." @@ -264,7 +423,7 @@ the Refresh button allows you to see changes, like mount Finally, C programming language style comments are supported by the EVMS CLI. Comments can begin and - end anywhere except within a quoted string, as in the + end anywhere except within a quoted string, as shown in the following example: /* This is a comment */ @@ -276,166 +435,8 @@ Volume",compatibility - -Linux LVM IEmulation Tools - You can administer - Linux LVM volumes through a set of command line utilities that emulate the Linux LVM - command set, using the EVMS Engine APIs. - - The Linux LVM is based on the concept of volume groups. A volume group (VG) is - a collection of physical volumes (PVs). All PVs in one group have their storage - space subdivided into small, fixed-sized sections called physical extents (PEs). - The default size for a PE is 4 MB. Logical volumes (LVs) are created by - allocating one or more PEs to the new LV. When I/O requests come in for a - volume, the LVM code determines which PV and which PE the request lies - on, and passes the request down the stack to the appropriate device. - - As noted in , EVMS uses different terms than those used - in Linux LVM. However, the two sets of terms are comparable. Volume groups (VGs) - from Linux LVM are called containers in EVMS. Because the LVM plug-in is an EVMS - Region Manager, its output objects (LVs in LVM) are called regions. The input - objects (PVs in LVM) are called segments, even though region - managers can actually take disks and other regions as inputs as well. These - command line utilities will often use the Linux LVM and EVMS terminology interchangeably. - - The options for the EVMS emulation of the Linux LVM command set are the same as the - options for the Linux LVM commands. However, some options now have slightly - different meanings. For instance, the verbose option (-v) displays additional - information about the command to the user, but also opens the Engine with DEBUG - level messaging, so that additional information is written to the Engine log - (/var/log/evmsEngine.log). The debug option (-d) displays the - same amount of info to the user as the verbose option, but opens the Engine with - ENTRY_EXIT level messaging, which causes detailed trace information to be - written to the Engine log. Also, some options are currently silently ignored, - because their functionality has not been implemented yet, or because that - functionality is not necessary in EVMS. For instance, the auto-backup option () - is ignored because the LVM plug-in - does not yet make metadata backups. - - The following commands are available - in the command line utilities. The - options are generally identical to those available from - the Linux LVM commands. Use the option for each - command to learn more about that command. - - - evms_vgcreate - Creates a new LVM volume group - with the given list of PVs. VG commands no longer require the user to prepare objects - with evms_pvcreate. Any available object in EVMS can now - be used directly by these commands. Similarly, the - evms_pvremove command is no longer necessary to release - PVs back to available EVMS - objects. - - evms_vgremove - Deletes an existing volume - group. - - evms_vgextend - Adds new PVs to an existing - volume group. - - evms_vgreduce - Takes PVs out of an existing - volume group. - - evms_vgscan - Lists all current LVM - VGs. This command also contains a new option - (-c) to force a commit, and the creation of - all necessary device files in - /dev. This creation of - files is necessary for existing LVM setups - that have not created any new LVs using the - EVMS tools (unless devfs is enabled). The same - results can also be accomplished by by saving in any of the EVMS interfaces. - - evms_vgdisplay -Displays extra information - about the specified VG. - - - evms_lvcreate - Creates a new LVM logical - volume. evms_lvcreate supports creating normal (linear) LVs as - well as striped LVs. Linear LVs can be specified as being contiguous. The LVM - plug-in defines contiguous to mean the LV must reside on a - single PV in a contiguous run of PEs. - - - evms_lvremove - Deletes an LVM logical - volume. - - evms_lvextend - Expands an existing LV by - adding extents. You must expand the file system - after expanding the LV. This command currently - does not support expanding snapshots or - snapshot originals. The Engine will coordinate the expanding and shrinking of the file system - if the FSIM (file system interface module) for the file system is installed. - - evms_lvreduce - Shrinks an existing LV by - removing extents. You must shrink the file - system before shrinking the LV. Do not shrink - the LV first, or you will risk losing data - from the file system. This command does not currently - support shrinking snapshots or snapshot - originals. The Engine will coordinate the expanding and shrinking of the file system - if the FSIM (file system interface module) for the file system is installed. - - evms_lvscan - Lists all current LVM - LVs. When an LV is listed as inactive that LV does not appear as a - compatibility volume in EVMS, and it is not - available for use through EVMS. The - only way this can occur is if the LV was - created in the EVMS GUI and a compatibility - volume was not added. Use - the GUI to perform the task of adding a - compatibility volume to an inactive LV. - - evms_lvdisplay - Displays extra information - about the specified LV. - - evms_pvscan - Lists all current LVM - PVs. This command also lists all other EVMS - disks, segments, and regions, and marks each - as "available" or "unavailable." Available - objects can be used directly to create or - extend volume groups. - - evms_pvdisplay - Displays extra information about the - specified PV. - - - - Two commands have been removed from the set of LVM utilities. - evms_pvcreate and - evms_pvremove are no longer - necessary. The evms_pvscan command - will now display all LVM PVs as well as all other - disks, segments, and regions in EVMS, and label them - as available or unavailable. Objects that are marked as - available can be used by evms_vgcreate - without needing to call evms_pvcreate. - - - - - - - - - - - + \ No newline at end of file diff --git a/LDP/guide/docbook/EVMSUG/convertto-ug.xml b/LDP/guide/docbook/EVMSUG/convertto-ug.xml index 492b7b6a..b77ffc44 100644 --- a/LDP/guide/docbook/EVMSUG/convertto-ug.xml +++ b/LDP/guide/docbook/EVMSUG/convertto-ug.xml @@ -1,32 +1,39 @@ -Converting Volumes + + + +Converting volumes This chapter discusses converting compatibility volumes to EVMS volumes and converting EVMS volumes to compatibility volumes. For a discussion -of the difference between compatibility and EVMS volumes see . +of the differences between compatibility and EVMS volumes, see . -When to Convert Volumes -There are a 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. +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 +is converted, you can remount it using its new name. -Working through an Example of Converting Compatibility Volumes to EVMS Volumes +Example: convert compatibility volumes to EVMS volumes A compatibility volume can be converted to an EVMS volume in the following situations: -The compatibility volume has no filesystem (FSIM) on it. -The compatibility volume has a filesystem, but the filesystem has been shrunk (if necessary) to make +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. This section provides a detailed explanation of how to convert compatibility - volumes to EVMS volumes by providing instructions to help you complete the following task. + 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 - that you want to make an EVMS volume named my_vol.
+ that you want to make into an EVMS volume named my_vol. Using the EVMS GUI + Follow these steps to convert a compatibility volume with the EVMS GUI: Choose Action Convert @@ -38,25 +45,53 @@ room for the EMVS metadata. Click the Convert button to convert the volume. + +Alternatively, you can perform some of the steps to convert the volume from the GUI +context sensitive menu: + + + From the Volumes tab, right click + on /dev/evms/hda3. + + Click Convert to EVMS Volume... + Continue to convert the volume beginning with step 3 of the GUI + instructions. + Using Ncurses + Follow these instructions to convert a compatibility volume to an EVMS volume + with the Ncurses + interface: - Press the 2 key to see the volume view. - Highlight /dev/evms/hda3 by - using the up and down arrow keys to scroll through the volumes.Press the - Enter key. - Highlight Convert to EVMS Volume. Press the - Enter key. - Type my_vol at the "::" prompt. - Press the Enter key. + Choose Actions + ConvertCompatibility Volume to EVMS Volume + Select /dev/evms/hda3 from the list + of available volumes. + + Type my_vol when prompted for the name. + Press Enter. + Activate Convert. + +Alternatively, you can perform some of the steps to convert the volume from the +context sensitive menu: + + +From the Volumes view, press Enter on /dev/evms/hda3. + +Activate the Convert to EVMS Volume menu item. + +Continue to convert the volume beginning with step 3 of the Ncurses +instructions. + + Using the CLI - To convert a volume use the Convert command. + To convert a volume, use the Convert command. The Convert command takes the name of a volume as its first argument, and then for what you want to name the new volume as the second argument. To complete the example and convert a volume, type the @@ -65,19 +100,21 @@ room for the EMVS metadata. -Working through an Example of Converting EVMS Volumes to Compatibility Volumes +Example: convert EVMS volumes to compatibility volumes An EVMS volume can be converted to a compatibility volume only if the volume does not have EVMS features on it. This section provides a detailed explanation of how to convert EVMS volumes to compatibility volumes by providing instructions to help you complete the following task. -
Convert an EVMS Volume -You have an EVMS volume, /dev/evms/my_vol +
Convert an EVMS volume +You have an EVMS volume, /dev/evms/my_vol, that you want to make a compatibility volume.
Using the EVMS GUI + Follow these instructions to convert an EVMS volume to a compatibility + volume with the EVMS GUI: Choose Action Convert @@ -88,18 +125,48 @@ room for the EMVS metadata. Click the Convert button to convert the volume. + + Alternatively, you can perform some of the steps to convert the volume through + the GUI context sensitive menu: + + From the Volumes tab, right click + /dev/evms/my_vol. + + Click Convert to Compatibility Volume... + + Continue converting the volume beginning with step 3 of the + GUI instructions. + Using Ncurses +Follow these instructions to convert an EVMS volume to a compatibility volume +with the Ncurses interface: - Press the 2 key to see the volume view. - Highlight /dev/evms/my_vol. - Press the Enter key. - Highlight Convert to Compatibility Volume - . Press the Enter key. - Highlight Convert to confirm. - Press the Enter key. - + Choose Actions + ConvertEVMS Volume to + Compatibility Volume + Select /dev/evms/my_vol from the + list of available volumes. + + Activate Convert. + + + +Alternatively, you can perform some of the steps to convert the volume through +the context sensitive menu: + + +From the Volumes view, press Enter on /dev/evms/my_vol. + +Activate the Convert to Compatibility Volume menu item. + +Continue to convert the volume beginning with step 3 of the Ncurses +instructions. + + + + Using the CLI To convert a volume use the Convert command. @@ -115,14 +182,4 @@ room for the EMVS metadata. - - - - - - - - - - - + \ No newline at end of file diff --git a/LDP/guide/docbook/EVMSUG/create-cont.xml b/LDP/guide/docbook/EVMSUG/create-cont.xml index 5e4633a6..11a6a3f4 100644 --- a/LDP/guide/docbook/EVMSUG/create-cont.xml +++ b/LDP/guide/docbook/EVMSUG/create-cont.xml @@ -1,11 +1,17 @@ -Creating a Container - -The following chapter discusses when and how to create a container. -When to Create a Container -Segments and disks may be combined to form a container. Containers allow you to combine - storage objects and then subdivide those combined storage objects into new storage objects. You can + + +Creating a container + +This chapter discusses when and how to create a container. + + +When to create a container +Segments and disks can be combined to form a container. Containers allow + you to combine + storage objects and then subdivide those combined storage objects + into new storage objects. You can combine storage objects to implement the volume group concept as found in the AIX and Linux logical volume managers. Containers are the beginning of more flexible @@ -13,19 +19,21 @@ volume management. You might want to create a container in order to account for need to add additional disks when your applications or users need more storage. -Working through an Example +Example: create a container This section provides a detailed explanation of how to create a container with EVMS by providing instructions to help you complete the following task.
Create "Sample Container" -Given a system with three available disk drives (sdc, sdd, hdc), use the EVMS LVM Region Manager to - combine these disk drives into a container called "Sample Container" with a PE size of 16 MB.
+Given a system with three available disk drives +(sdc, sdd, hdc), + use the EVMS LVM Region Manager to combine these disk drives into a +container called "Sample Container" with a PE size of 16 MB.
Using the EVMS GUI - To create a container using the EVMS GUI, follow the steps below: + To create a container using the EVMS GUI, follow these steps: Select @@ -43,16 +51,16 @@ to help you complete the following task. Select sdc, sdd, and hdc from the list. Click - Next + Next. Enter the name Sample Container for the container and 16MB in the PE size field. - Click the - Create - button. A window that displays the - outcome appears. + Click + Create. + A window opens to display the + outcome. @@ -63,103 +71,65 @@ to help you complete the following task. Using Ncurses - To create a container using the Ncurses interface, follow the steps below: + To create a container using the Ncurses interface, follow these +steps: - Press the - 4 key to switch - views. + Select Actions + CreateContainer + to see a list of plug-ins that support container creation. - Scroll down the list - using the down arrow key to the - Storage - Containers. Press the - Enter key. + Select the + LVM Region Manager. Activate + Next. + The next dialog window contains a list + of storage objects that the LVM Region Manager can use to + create the container. - Press the Enter key again to - display a sub menu. + Select sdc, sdd, and + hdc from the list. Activate + Next. - Scroll down until you highlight Create a New Container. - Press the Enter key. You should see a list of plug-ins that support container - creation. + Press spacebar to select the field for + the container name. - Select - LVM Region Manager. Press the - Enter key. - - The next sub menu contains a - list of storage objects, such as - segments, disks, or regions the - LVM Region Manager finds acceptable to - use for the creation of a - container. - - Use the - spacebar to select sdc, - sdd, and hdc from - the list. Press the Enter key. Selected disks will be marked with - an x. - - Press the - spacebar key to - select the field for the container - name. - - Type Sample Container at the "::" prompt. Press the - Enter key. + Type Sample Container at the "::" prompt. Press + Enter. -Scroll down until PE Size is highlighted. Press the spacebar. + Scroll down until PE Size is highlighted. + Press spacebar. -Scroll down until 32768 is highlighted. Press the spacebar. -NOTE -In Ncurses PE Size is listed in sectors, so 16MB = 32768 (512B) sectors. + Scroll down until 16MB is highlighted. + Press spacebar. - Press the Enter key to complete - the operation. + Activate OK. + + Activate Create. Using the CLI - The Create command is - used to create containers. The first argument + The Create command + creates containers. The first argument in the Create command is the type of object to produce, in this case a container. The Create command then accepts the following arguments: the region manager to use along with any parameters it might need, and the segments or disks to create the container - from. The command to complete the example - above is: + from. The command to complete the previous example is: - -Create:Container,LvmRegMgr={name="Sample Container",pe_size=16KB},sdc,sdd,hdc +Create:Container,LvmRegMgr={name="Sample Container",pe_size=16MB},sdc,sdd,hdc - The example above accepts the default values for all options you don't specify. To see the options for this command type: + The previous example accepts the default values for all options +you don't specify. To see the options for this command type: query:plugins,plugin=LvmRegMgr,list options -Using Linux LVM Emulation Tools -To create a container using the Linux LVM emulation tools, type the following at the command prompt: -evms_vgcreate --verbose --physicalextentsize 16MB "Sample Container" sdc sdd hdc - -For a listing of other options used with the evms_vgcreate command type: - -evms_vgcreate -h - - - - - - - - - - - - + \ No newline at end of file diff --git a/LDP/guide/docbook/EVMSUG/create-reg-ug.xml b/LDP/guide/docbook/EVMSUG/create-reg-ug.xml index 3d433aa7..7d11f2dc 100644 --- a/LDP/guide/docbook/EVMSUG/create-reg-ug.xml +++ b/LDP/guide/docbook/EVMSUG/create-reg-ug.xml @@ -1,184 +1,159 @@ -Creating Regions + + + +Creating regions Regions can be created from containers, but they can also be created from other -regions, segments, or disks. Most region managers that support containers will create one or more +regions, segments, or disks. Most region managers that support containers create one or more freespace regions to represent the freespace within the container. This function is analogous to the way a segment manager creates a freespace segment to represent unused disk space. -When to Create Regions +When to create regions -You can create regions because you want the features provided by 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 can create regions because you want the features provided by +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. -Working through an Example -This section provides a detailed explanation of how to create a region with EVMS by +Example: create a region +This section tells how to create a region with EVMS by providing instructions to help you complete the following task.
Create "Sample Region" -Given the container "Sample Container," which has a freespace region of 8799 MB -create a data region 1000 MB in size named "Sample Region."
+Given the container "Sample Container," which has a freespace region of +8799 MB, create a data region 1000 MB in size named "Sample Region." Using the EVMS GUI - To create a region, follow the steps below: + To create a region, follow these steps: Select Actions - Create - Region - to see a list of region - manager plug-ins. + CreateRegion + Select the LVM Region Manager. Click Next. NOTE -You may +You might see additional region managers that were not in the selection list when you were creating the storage container because not all region managers are required to support containers. Select the freespace region from - the container you created in . - The region should be named + the container you created in + . + Verify that the region is named lvm/Sample Container/Freespace. Click Next. The fields in the next window are the options for the - LVM Region Manager plug-in,the options marked with an "*" are required. + LVM Region Manager plug-in, the options marked with an "*" are required. - Fill in the name,Sample Region. + Fill in the name, Sample Region. Enter 1000MB in the size field. Click the Create button to complete the - operation. A window that displays the - outcome appears. + operation. A window opens to display the outcome. + +Alternatively, you can perform some of the steps for creating a region with the GUI context sensitive menu: + +From the Regions tab, right click + lvm/Sample Container/Freespace. + + Click Create Region. + + Continue beginning with step 4 of the GUI instructions. + Using Ncurses - To create a region, follow the steps below: + To create a region, follow these steps: - Press the - 4 key to switch - views. - - Scroll down the - list using the down arrow key until - Storage - Regions is - highlighted. Press the - Enter key. - - Press the - Enter key again to - display a submenu. - - Press the - Enter key when - Create a New - Region is - highlighted. You will be presented - with a list of region manager - plug-ins. + Select + Actions + Create + Region. Select the LVM Region - Manager. Press the Enter key. - - NOTE - You might see additional region - managers that were not in the - selection list when you created - the storage container. This absence of - region managers occurs - because not all region managers are - required to support - containers. + Manager. Activate Next. + Select the freespace region from the container you created - earlier in . The region should be - named + earlier in . Verify that + the region is named lvm/Sample Container/Freespace. - Use the spacebar - key to select it. Press the - Enter key to - continue. The configuration options - submenu should - appear. - + Scroll to the Name field, and press - spacebar + spacebar. Type Sample Region at the "::" prompt. Press Enter. - Scroll to the size field, and press - the spacebar + Scroll to the size field, + and press spacebar. - Type 1000 at the "::" prompt. + Type 1000MB at the "::" prompt. Press Enter. - Check all fields to make sure they were entered appropriately. - If the units are displayed as KB and you desired MB, return to the previous step, - and enter the value of KB that is equal to the MB value you desired. + Activate Create. + +Alternatively, you can perform some of the steps for creating a region with the +context sensitive menu: + + +From the Storage Regions view, press Enter on +lvm/Sample Container/Freespace. + +Activate the Create Region menu item. + +Continue beginning with step 4 of the Ncurses instructions. + + Using the CLI - Regions are created using the Create + Create regions with the Create command. Arguments to the Create command are the following: keyword Region, the name of the region manager to use, the region managers options, and the objects to consume. The form of this command is: -Create:region, LvmRegMgr={name="Sample Region"; size=1000MB},"lvm/Sample Container/freespace" +Create:region, LvmRegMgr={name="Sample Region", size=1000MB}, +"lvm/Sample Container/Freespace" The LVM Region Manager supports many options for creating regions. To see the available options for creating regions and - containers, use the Query command as follows: + containers, use the following Query: query:plugins,plugin=LvmRegMgr,list options -Using Linux LVM Emulation Tools - The command that creates a region in LVM also creates an EVMS compatibility volume. Details on creating regions with the Linux LVM emulation tools can be found in the . - - - - - - - - - - - - - - - + \ 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 1961e921..fb706c98 100644 --- a/LDP/guide/docbook/EVMSUG/create-seg.xml +++ b/LDP/guide/docbook/EVMSUG/create-seg.xml @@ -1,22 +1,25 @@ -Creating Segments -The following chapter discusses when to use segments and how to create segments using + + +Creating segments + +This chapter discusses when to use segments and how to create them using different EVMS interfaces. -When to Create a Segment +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 . -Working through an Example +Example: create a segment This section provides a detailed explanation of how to create a segment with EVMS by providing instructions to help you complete the following task: -
Create a 100MB egment +
Create a 100MB segment Create a 100MB segment from the freespace segment sde_freespace1. This freespace segment lies on a drive controlled by the DOS Segment Manager.
@@ -61,65 +64,61 @@ segment with EVMS by providing instructions to help you complete the following t fields, the Create button becomes available. - Click the - Create - button. A window that displays the - outcome appears. + Click + Create. + A window opens to display the + outcome. +Alternatively, you can perform some of the steps to create a segment from the GUI context sensitive menu: +From the Segments tab, right click +on sde_freespace1. + +Click Create Segment... +Continue beginning with step 4 of the GUI instructions. + Using Ncurses - To create a segment using the Ncurses, follow the steps below: + To create a segment using Ncurses, follow these steps: - Press the 4 key - to switch views. + Select ActionsCreateSegment to see a list of segment manager plug-ins. - Scroll down using the - down arrow key until Disk Segments is highlighted. - Press the Enter key. - - Press the Enter key - again to display a sub menu on the - current selection. - - Select Create a - New Segment. Press the - Enter key. You should see a list of segment - manager plug-ins. - - Select DOS Segment Manager. Press the Enter - key. - - The next dialog window - will present a list of free space + Select DOS Segment Manager. + Activate Next. +The next dialog window + lists free space storage objects suitable for creating a new segment. - Select sde_freespace1 by moving to it with the arrow - keys and then using the spacebar key - to select it. After the storage object is selected (it - is marked by an "X"), press the Enter key. - The last dialog window displays the selected freespace object and configuration options - available from the plug-in manager. Required fields are denoted by the "*" in front of the field - description. The DOS Segment Manager provides default values, but you might want to change some of these - values. + Select sde_freespace1. Activate Next. - Highlight the size field and press the spacebar key. + - At the "::" prompt enter 100. - Press the Enter key. + Highlight the size field and press spacebar. + + At the "::" prompt enter 100MB. + Press Enter. -Check all fields to make sure they were entered appropriately. If the units are displayed as KB, and you desired MB, return to step 7 and enter the value of KB that is equal to the MB value you desired. For example, instead of entering 100 you would enter 102400 (100 x 1024) to convert the KB value to MB. - - Once all required values have been completed, press the Enter key - and a results status message will be displayed. + After all required values have been completed, the Create + button becomes available. +Activate Create. +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. + +Activate Create Segment. + +Continue beginning with step 4 of the Ncurses instructions. + + @@ -145,20 +144,10 @@ segment with EVMS by providing instructions to help you complete the following t NOTE -The Allocate command will also work to create a segment. -The example above accepts the default values for all options you don't specify. To see the options for this command type:query:plugins,plugin=DosSegMgr,list options +The Allocate command also works to create a segment. +The previous example accepts the default values for all options you don't specify. To see the options for this command type:query:plugins,plugin=DosSegMgr,list options - - - - - - - - - - - + \ 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 08b96007..2139783b 100644 --- a/LDP/guide/docbook/EVMSUG/createvol-ug.xml +++ b/LDP/guide/docbook/EVMSUG/createvol-ug.xml @@ -1,17 +1,22 @@ -Creating Volumes - -This following chapter discusses when and how to create volumes. -When to Create a Volume - EVMS treats volumes and storage objects as separate. A storage object does not automatically -become a volume. Instead, a storage object must be made into a volume. + + +Creating volumes + +This chapter discusses when and how to create volumes. + + +When to create a volume + EVMS treats volumes and storage objects separately. +A storage object does not automatically +become a volume; it must be made into a volume. Volumes are created from storage objects. Volumes are either EVMS native volumes or compatibility volumes. Compatibility volumes are intended to be compatible with a volume manager other than EVMS, such as the Linux LVM, MD, OS/2 or AIX. Compatibility volumes might have restrictions on what EVMS can do with - them. EVMS native volumes have no such restrictions, but they can only be used by an - EVMS equipped system. Volumes are mountable and can contain filesystems. + them. EVMS native volumes have no such restrictions, but they can be used only by an + EVMS equipped system. Volumes are mountable and can contain file systems. EVMS native volumes contain EVMS-specific information @@ -20,12 +25,12 @@ become a volume. Instead, a storage object must be made into a volume. with existing volume types. Instead of - adding EVMS metadata to an existing object, we can tell EVMS to make an object directly available as a volume. This type 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. -Working through an Example of Creating an EVMS Native Volume +Example: create an EVMS native volume This section provides a detailed explanation of how to create an EVMS native volume with EVMS by providing instructions to help you complete the following task. @@ -36,40 +41,52 @@ become a volume. Instead, a storage object must be made into a volume. Using the EVMS GUI - Follow the instructions below to create an EVMS volume: + Follow these instructions to create an EVMS volume: Select Actions Create - EVMS Volume + EVMS Volume. Choose lvm/Sample Container/Sample Region. Type Sample Volume in the name field. - Click Create - + Click Create. + Alternatively, you can perform some of the steps to create an EVMS +volume from the GUI context sensitive menu: + +From the Available Options tab, right click + lvm/Sample Container/Sample Region. + + Click Create EVMS Volume... + Continue beginning with step 3 of the GUI instructions. + + Using Ncurses - To create a volume, follow the steps below: + To create a volume, follow these steps: - Press the 4 key to switch views. - Scroll down the list using the down arrow key to the - available topmost storage object. Press the Enter key - Highlight lvm/Sample Container/Storage Region. - Press the Enter key. - Select Create EVMS Volume from - the Storage Object. Press the - Enter key. - - Confirm the creation - of the volume. - Enter Sample Volume at the "::" prompt. - Press the - Enter key to complete - the operation. + Select Actions + CreateEVMS Volume. + + Enter Sample Volume at the "name" prompt. + Press Enter. + Activate Create. - If you look at the volumes view - (2), you should see your new volume. +Alternatively, you can perform some of the steps to create an EVMS volume +from the context sensitive menu: + + +From the Available Objects view, press Enter on +lvm/Sample Container/Sample Region. + +Activate the Create EVMS Volume menu item. + +Continue beginning with step 3 of the Ncurses instructions. + + + + @@ -79,7 +96,8 @@ become a volume. Instead, a storage object must be made into a volume. 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 . - The third argument is type specific for an EVMS volume we need and what + The third argument is type specific for an EVMS + volume, , followed by what you want to call the volume, in this case . The following command creates the volume from the example. Create: Volume, "lvm/Sample Container/Sample Region", Name="Sample Volume" @@ -90,9 +108,9 @@ become a volume. Instead, a storage object must be made into a volume. -Working through an Example of Creating a Compatibility Volume +Example: create a compatibility volume This section provides a detailed explanation of how to create a compatibility - volume with EVMS by providing instructions to help you complete the followint task. + volume with EVMS by providing instructions to help you complete the following task. @@ -101,7 +119,7 @@ become a volume. Instead, a storage object must be made into a volume. the region, /lvm/Sample Container/Region, you created in .
Using the GUI - To create a compatibility volume, follow the steps below: + To create a compatibility volume, follow these steps: Select @@ -111,35 +129,57 @@ become a volume. Instead, a storage object must be made into a volume. Choose the region lvm/Sample Container/Sample Region - from the list + from the list. Click the Create button. - Click on the Volume tab in the GUI to + Click the Volume tab in the GUI to see a volume named /dev/evms/lvm/Sample Container/Sample Region. This volume is your compatibility volume. + +Alternatively, you can perform some of the steps to create a compatibility volume from +the GUI context sensitive menu: + + From the Available Objects tab, right click + lvm/Sample Container/Sample Region. + + Click Create Compatibility Volume... + + Continue beginning with step 3 of the GUI instructions. Using Ncurses - To create a compatibility volume, follow the steps below: + To create a compatibility volume, follow these steps: - Press the 4 key to switch views. - Scroll down the list using the down arrow key to the - available topmost storage object. Press the Enter key - Highlight lvm/Sample Container/Storage Region. - Press the Enter key. + Select Actions + CreateCompatibility Volume. + + Choose the region lvm/Sample Container/Storage Region from the list.. + - Select Create Compatibility Volume from Storage Object. - Press the Enter key. - Confirm the creation of the volume. + + Activate Create. + +Alternatively, you can perform some of the steps to create a compatibility volume from +the context sensitive menu: + + +From the Available Objects view, press Enter on +lvm/Sample Container/Sample Region. + +Activate the Create Compatibility Volume menu item. + +Continue beginning with step 3 of the Ncurses instructions. + + Using the CLI To create a volume, use the Create command. The arguments - the Create accepts vary depending on what is being created. In + the Create cocmmand 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 . @@ -147,34 +187,9 @@ become a volume. Instead, a storage object must be made into a volume. volume and should be named as such. Create:Volume,"lvm/Sample Container/Sample Region",compatibility - - Using Linux LVM Emulation Tools - Using Linux LVM emulation tools, you can create only an EVMS compatibility volume, not an EVMS native volume. To create a region and a corresponding EVMS compatibility volume, type the following: - -evms_lvcreate --verbose --size 1000M --name "Sample Region" "Sample Container" - - For help and additional options available with evms_lvcreate type the following: - -evms_lvcreate -h - - - - - - - - - - - - - - - - - + \ No newline at end of file diff --git a/LDP/guide/docbook/EVMSUG/install-ug.xml b/LDP/guide/docbook/EVMSUG/install-ug.xml index 2e8d613c..8fca1438 100644 --- a/LDP/guide/docbook/EVMSUG/install-ug.xml +++ b/LDP/guide/docbook/EVMSUG/install-ug.xml @@ -1,274 +1,125 @@ -Downloading and Installing EVMS -This chapter helps you make informed decisions about how you want to install and configure your EVMS system. In order to get the best understanding of the different options and steps for installing EVMS, read this chapter in its entirety before you begin the process. - -Preparing Your System -You will need to make several - choices when installing EVMS, such as how you want to build EVMS and which - capabilities you want to enable. You will also need you will need to make sure - that you have a kernel source tree. The following sections explain these choices and - guide you through the installation process. - - Choosing Capabilities - EVMS has many capabilities. Certain options you choose during install - allow EVMS to be compatible with logical volumes from Linux - LVM, AIX LVM, and OS/2 LVM, as well as Linux MD/Software - RAID. EVMS also has unique features, - such as bad block relocation. If - you do not know which capabilities you want to use, turn - on kernel support for all the options. You can decide - which ones to use after the Engine and user-space - administration tools are installed. - - MD Support - If you choose to turn - on EVMS MD support, do not enable native MD support (in the - Multi-device Support menu). MD - rewrites its metadata from within the kernel, and if both - systems recognize the same volume, it could cause metadata - corruption. - - - EVMS Linux LVM - If you choose to - turn on EVMS Linux LVM support, you can enable native Linux - LVM support. Avoid mounting the same volume through - both systems at the same time, or you could cause volume data - corruption. Also, if you use one system to make a change to - a volume or group configuration, you might need to reboot for - the other system to fully recognize the changes. - - - - - Selecting Building Options - You have the option of building EVMS as kernel - modules instead of compiling EVMS directly into the kernel. - However, if you choose to build EVMS as modules, EVMS will not automatically - perform discovery at kernel boot time. You will need to load the - necessary kernel modules from user-space using insmod - or modprobe. Then, use the - evms_rediscover utility to tell EVMS to - discover the logical volumes. +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. - If you decide to build EVMS as kernel modules, and you - want your root file-system on an EVMS volume, you must use an - init-ramdisk during boot. See for instructions on adding - EVMS support to your init-ramdisk . - +Preparing your system +Before you install EVMS, decide whether to implement certain kernel capabilities and ensure that you have a Linux kernel source tree. EVMS 2.0 is built on top of the already existing components MD and Device Mapper (DM). If you are using Linux kernel 2.5 or later, the MD and DM components are already available, but you need to apply some patches for bug fixes because the 2.5 kernel is still stabilizing. If you are using Linux kernel 2.4, you need to obtain all the DM patches from the Sistina website and then apply the bug fixes. Steps for performing these tasks are included later in this chapter. + + Choosing capabilities + In order to run EVMS, you need to configure the Device Mapper in your kernel either as a module or as a component built directly into the kernel. If you want to use the RAID functions of EVMS, turn on MD and the appropriate RAID personalities in the kernel. + + + Obtaining the Device Mapper and a kernel source tree + EVMS 2.0 is built on top of the already existing components MD and Device Mapper. If you are using Linux kernel 2.5 or later, the MD and DM components are already available; however, you need to apply some patches for bug fixes because the 2.5 kernel is still stabilizing. If you are using Linux kernel 2.4, you need to patch the DM in from the Sistina website and then apply the bug fixes. The DM patches for the kernel are included in the EVMS package on the EVMS project website. The current EVMS package contains a patch for both the 2.4 and 2.5 kernel series. NOTE - If you choose to build EVMS as - kernel modules, you will need to compile all EVMS plug-ins as - modules. If you compile some plug-ins as modules and some - plug-ins directly into the kernel, the plug-ins that are in the - kernel will perform automatic boot-time discovery, without the - remaining plug-ins being active. This inconsistency could produce - incorrect volumes. It is strongly recommended that you not build EVMS as modules without - adding support to your EVMS ramdisk. EVMS configurations built as modules that do not - have support in the ramdisk do not allow EVMS to offer the usual protections against corrupting - data - - If you have built the plug-ins as - modules, and do not wish to mount your root - file system - using EVMS, simply add entries in your - init scripts to - load all the necessary EVMS modules and run the - evms_rediscover - utility. You should run the rediscover early in - the boot scripts before the /etc/fstab file is - processed. - - Kernel Source Tree - To install EVMS, you will need to add EVMS support to your Linux - kernel. Currently, - EVMS support is not included in the main Linux kernel. - EVMS patches for the kernel are included in the EVMS package on the - EVMS project website. The current - EVMS package contains a patch against both the 2.4 and - 2.5 kernel series. - - NOTE - EVMS will not work with 2.3, 2.2, or earlier kernel series. + EVMS does not work with Linux kernels 2.3, 2.2, or earlier. If you do not have a Linux kernel source tree, you can obtain one from The Linux Kernel Archives . The current recommended - kernel to use is 2.4.19, but most 2.4 series kernels will - work. + kernel is 2.4.20, but earlier 2.4 series kernels might + work. - - - Downloading EVMS - To install EVMS, download the latest version EVMS - (evms-1.2.0.tar.gz) from the + To install EVMS, download the latest version of EVMS + (evms-2.0.0.tar.gz) from the EVMS project homepage. This file contains source code patches for the Linux kernel and source code for all necessary user-space administration tools. After downloading the file, - untar it in the appropriate - place, using the following command: + use the tar command to extract the files in the + appropriate place. In the following example, the files are + extracted in /usr/src. You can substitute + another directory. +cd /usr/src +tar xvzf evms-2.0.0.tar.gz - - - - - NOTE - The command - above assumes the file will be untarred in - /usr/src. You can substitute another directory. - Patching the Kernel - You must apply three patches to your kernel tree - to include EVMS support: - - a patch specific to - your version of the kernel. + Patching the kernel + In addition to the base MD and Device Mapper support, EVMS requires a few + patches for the EVMS engine to work correctly with these drivers. These + patches are provided in the EVMS package, in the kernel/2.4.20/ + subdirectory. See the INDEX files in the kernel/2.4.20 directory + for descriptions of the patches. + - a patch that includes - all the EVMS specific source code. +NOTEIf you are currently using the Sistina LVM2 tools, + the patches provided here are not compatible with the LVM2 tools. + EVMS has made some changes to the kernel ioctl packets so that they + work correctly on ppc-64 and sparc-64 architectures. These changes + have not yet been accepted by Sistina. Thus, for the time being, you + need to use separate kernels for running EVMS and LVM2. - a patch that adds - code to allow the filesystems to perform flushing and - locking when certain volume configuration changes take - place. This third patch is necessary only when - you want to take SnapShot volumes of journaling - filesystems, such as JFS, ReiserFS, ext3, and XFS. - - - - To apply the patches to the kernel, complete the following steps: - - Determine which kernel version - you are using. - - Find the appropriate patch in the - kernel directory of the EVMS - package. This example will use a system running kernel - 2.4.19, and a - kernel source tree in /usr/src/linux. - NOTE -If your kernel source tree is in a different location, - you will need to make the appropriate changes to these instructions. - - - Apply the first patch to your - kernel tree by typing the following commands: - - - - - - - From the same directory as the - previous step, type the following command to - apply the actual EVMS code to any 2.4 kernel tree: - - - - - - - If you are running a 2.5 kernel, substitute - evms-1.2.0-linux-2.5.patch - in the command above. - - - To apply the optional VFS Locking Patch, remain in the - /usr/src/linux directory, and type the following command: - - - - - - Distributions make modifications to the Linux kernel - that are sometimes incompatible with the code in EVMS. - If you are patching a kernel from a - distribution, the above commands might produce patch - failures, and you might need to manually patch the - affected files. To make the installation easier, it is - recommended that you start with a clean kernel from - kernel.org. + Apply each of the patches for 2.4.20 to your kernel as follows: +cd /usr/src/linux-2.4.20 +patch -p1 < /src/src/evms-2.0.0/kernel/2.4.20/1-dm-base.patch +patch -p1 < /src/src/evms-2.0.0/kernel/2.4.20/2-syncio.patch +patch -p1 < /src/src/evms-2.0.0/kernel/2.4.20/3-dm-bbr.patch +patch -p1 < /src/src/evms-2.0.0/kernel/2.4.20/4-dm-sparse.patch +patch -p1 < /src/src/evms-2.0.0/kernel/2.4.20/5-md.c.patc +patch -p1 < /src/src/evms-2.0.0/kernel/2.4.20/6-vsprintf.c.patch +patch -p1 < /src/src/evms-2.0.0/kernel/2.4.20/7-vfs-lock.patch - Configuring the Kernel + Configuring the kernel After patching the kernel, configure it with EVMS support. To configure the kernel, complete the following steps: - Type the following command: -make xconfig + Type the following command: + make xconfig NOTE -You can also use config or - menuconfig if you don't have an Xwindow system. +You can also use config or menuconfig if you don't have an Xwindow system. - - - If you are using an Xwindow system, the following window appears. + If you are using an Xwindow system, the following window opens.
xconfig Window - + xconfig Window
 - To enable EVMS support, select - Enterprise Volume Management - System. The following window appears. -
Linux Kernel Configuration Window - - Linux Kernel Configuration 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 - If you are configuring EVMS as + If you are configuring the components as modules, you can click the Help button beside each - module to see the name of each kermel module. + module to see the name of each kernel module. - Select for the first three - options: , , and - . These options are the bare minimum for EVMS. + Select for Multi-device support (RAID and LVM). + Select (to build in the kernel) or (to build + modules) + for Device Mapper support. + These options are the minimum required for EVMS. The remaining options add additional capabilities to EVMS. NOTE The options you select in this step are the ones you selected in . - + - Select for all additional options - you want to configure for EVMS. - NOTE - - If you are configuring EVMS as modules, - select for the first three options and all remaining - capabilities you wish to add. - + Continue configuring your kernel as required for your system and hardware. For general instructions on configuring @@ -281,69 +132,101 @@ patch -p1 < /usr/src/evms-1.2.0/kernel/linux-2.4.19-VFS-lock.patch -Building and Installing the New Kernel +Building and installing the new kernel - After you have configured the kernel, you will need to - build and install a new kernel image. There are slight variations for different architectures, - but the general steps are the same. For example, on Intel® machines you could run - lilo to install the new kernel image. However , on S/390 machines, you - would run zipl to install the new kernel image. The following instructions + After you have configured the kernel, build and install a new kernel image. + There are slight variations for different architectures, + but the general steps are the same. + For example, on Intel® machines you might run + lilo to install the new kernel image. + On S/390 machines, you might + run zipl to install the new kernel image. + The following instructions are based on an installation using an Intel machine. - Build the kernel : - - - - + Build the kernel: + + make dep clean bzImage modules modules_install + Copy the new kernel to the /boot directory. - - - + cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-evms NOTE - The command above assumes the file will be named + The previous command assumes the file to be named vmlinuz-evms, you can substitute another name. -Open the file for the boot loader with your favorite editor. - The LILO boot loader information is in etc/lilo.conf. - The GRUB boot loader information is in boot/menu.list. +Open the file for the boot loader. + The LILO boot loader information is in /etc/lilo.conf. + The GRUB boot loader information is in /boot/menu.list. - Update the boot loader information as follows: - - - + Update the boot loader information as follows: +image=/boot/vmlinuz-evms + label=EVMS - - NOTE - In order to have your boot partition on an EVMS controlled volume and use LILO, - you must have an EVMS patched version of - LILO or a version since 22.3.2. - +NOTE + Currently, LILO does not support placing the /boot filesystem on a Device Mapper device. Thus, /boot must be mounted through the traditional partition device. + Run your boot loader to install the new kernel image. NOTE - If you installed your kernel as modules skip to - . You will also need to - complete after building the engine. + If you installed your kernel as modules, skip to + . - Re-boot your machine and choose the new + Reboot your machine and choose the new kernel image to run with EVMS support. + + +Installing the cluster manager +Skip this section if you do not require high-availability features. +EVMS currently supports the Linux-HA cluster manager, commonly known as +Heartbeat. You can download the latest version of the Linux-HA software from +http://www.linux-ha.org/download/. EVMS works +with Heartbeat V1.0.1 and later. For instructions on setting up a two-node cluster, see +http://www.linux-ha.org/download/GettingStarted.html. For additional information and a list of frequently asked questions, see +http://www.linux-ha.org/download/faqntips.html. + +Linux-HA provides the following sub-packages: + +heartbeat-xxx.arch.rpm + +heartbeat-stonith-xxx.arch.rpm + +heartbeat-pils-xxx.arch.rpm + +heartbeat-ldirectord-xxx.arch.rpm + + + + +"xxx" is the version of heartbeat; "arch" is the architecture of the target nodes. +You do not need to install heartbeat-ldirectord-xxx.arch.rpm because EVMS does not depend on its service. +NOTE +The download page also contains tarballs and source rpms. + + + +To install the package, execute the following command on each cluster node: +rpm -i heartbeat-pils-xxx.arch.rpm heartbeat-stonith-xxx.rpm \ +heartbeat-xxx.arch.rpm +NOTE +It is highly recommended that you configure the STONITH package on a two-node cluster because +data integrity on shared disks is at risk if STONITH is not configured. Although EVMS +operates even when STONITH is not configured (EVMS is not restricted to a two-node +cluster), EVMS's failover capability is limited by the support provided by the native +cluster manager. +Refer to the STONITH device manual for instructions on how to configure the +STONITH device. + + + Installing the Engine @@ -351,194 +234,256 @@ cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-evms The EVMS Engine consists of the user-space plug-ins and interfaces as well as a stand-alone library, dlist, that the Engine uses for linked-list management. - Installing from Source + Installing from source - To build and install the Engine from source, type the following commands: + To build and install the Engine from source, first type the following command to change to the /usr/src/evms-2.0.0 directory: - -cd /usr/src/evms-1.2.0/engine -autoconf +cd /usr/src/evms-2.0.0 - - - NOTE - The command autoconf - is necessary only for code taken directly from CVS. - However, using this command will not affect the build or - installation if your code is not taken directly from CVS. - + - Select the appropriate options for your configuration. - NOTE - A list of options can be found by typing - ./configure -h - + Select the appropriate options for your configuration. +NOTE + A list of options can be found by typing: + +./configure -h Configure your engine: - -./configure [--options] - +./configure [--options] + - Type the following commands: - -make + Type the following commands: + +make make install ldconfig - - Unless you specified other directories in Step 3, the + Unless you specified other directories when you configured the engine, the following list describes where files will be installed on your system: - The core Engine library will be installed in - /usr/local/lib. + The core Engine library is installed in + /lib. -The core dlist library will be installed in - /usr/local/lib. +The core dlist library is installed in + /lib. - All plug-in libraries will be installed in - /usr/local/lib/evms. + All plug-in libraries is installed in + /lib/evms. - All user interface binaries will be installed - in /usr/local/sbin. + All user interface binaries are installed + in /sbin. + All header files are installed in + /usr/include/evms. + All manual pages are installed in /usr/man. + + Add the Engine library path to your + LD_LIBRARY_PATH environment variable, or to + your /etc/ld.so.conf file. Do not add the + plug-in library path because the Engine dynamically loads + these libraries directly. + + - Add the Engine library path to your - LD_LIBRARY_PATH environment variable, or to - your /etc/ld.so.conf file. Do not add the - plug-in library path because the Engine will dynamically load - these libraries directly. + Examine the EVMS configuration file (evms.conf). This file contains settings to control how EVMS operates. + For example, the logging level, the location of the engine + log, and the list of disk devices to examine can all be + controlled through settings in the configuration file. + The sample file is well commented and advises you of appropriate + values for each setting. + + The evms.conf file is normally installed in + /etc/evms.conf. However, if you already have a configuration + file, it is installed as /etc/evms.conf.sample. Examine the + new sample + to see if your existing file should be updated. + + -Begin using EVMS by typing evmsgui +You can now begin using EVMS by typing evmsgui to start the GUI, evmsn to start the Ncurses UI, or evms to start the command line interpreter. + - Installing the Engine RPM - You can download an RPM with the latest compiled engine - binaries and libraries. This RPM is available on the project - web site along with the - source code package. The RPM is a - generic i386 RPM that should install on any system that uses - the RPM. - - If you install the EVMS RPM, you will still need to - patch your kernel with EVMS support. - - - Installing the EVMS Debian Packages + Installing the EVMS Debian packages Debian packages of EVMS are maintained by Matt Zimmerman at the Debian website. You can download these packages for the Woody (testing) release, or for the Sid (unstable) release. - For the Debian package you should patch and recompile your kernel in order to use - EVMS. Debian has a packaged version of the EVMS kernel patches, + For the Debian package, patch and recompile your kernel in order to use + EVMS. Debian has a packaged version of the EVMS kernel patches that includes instructions for patching and building your kernel. + Installing from CVS +If you would like to use the most recently developed version of EVMS, you can get +the code directly from the CVS tree. + + + + To download the code, type the + following commands: + +mkdir /usr/src/evms_cvs +cd /usr/src/evms_cvs +cvs -d:pserver:anonymous@cvs.evms.sf.net:/cvsroot/evms login + (press Enter when prompted for a password) +cvs -z3 -d:pserver:anonymous@cvs.evms.sf.net:/cvsroot/evms co engine2 + + +Alternatively, if you already have a copy of the CVS code checked out, you can update +to the latest code with the following commands: + + +cd /usr/src/evms_cvs/engine2 +cvs update -d -P + +The EVMS Engine can be built directly into the CVS tree. To start, change +directory to /usr/src/evms_cvs/engine2: + + +cd /usr/src/evms_cvs/engine2 +autoconf +NOTEThe autoconf command is necessary only for code taken directly from CVS. + +Select the appropriate options for your configuration. + NOTE + You can find the list of options by typing: + ./configure -h + + + +Configure your engine: + +./configure [--options] + + Type the following commands: + +make +make install +ldconfig + Unless you specified other directories in Step 5, the + following list describes where files are installed + on your system: + + The core Engine library is installed in + /lib. + +The core dlist library is installed in + /lib. + + All plug-in libraries is installed in + /lib/evms. + + All user interface binaries are installed + in /sbin. + All header files are installed in + /usr/include/evms. + All manual pages are installed in /usr/man. + + + +Add the Engine library path to your + LD_LIBRARY_PATH environment variable, or to + your /etc/ld.so.conf file. Do not add the + plug-in library path because the Engine dynamically loads + these libraries directly. + + + - - -Loading Modules with an Init-Ramdisk - If you built your EVMS kernel - plug-ins as modules and want your root - file system mounted on an EVMS volume (the only recommended way of using EVMS - built as kernel modules), you must add EVMS support - to your init-ramdisk. If you do not have an - init-ramdisk, general instructions for creating one are in the kernel source - tree in the file Documentation/initrd.txt. Some distributions include utilities for creating init-ramdisks. (See your distribution - for details.) If you do not want to use an - init-ramdisk but want your root filesystem on an EVMS volume, you should - compile all EVMS support directly into the kernel. - - To modify your init-ramdisk, - decompress it using gunzip and mount it through a loopback - device. The following steps walk you through modifying your - init-ramdisk. The following commands are based on - the assumption that the init-ramdisk is mounted on /mnt/loop. - - - Once the init-ramdisk is mounted, copy the EVMS kernel modules - to it. - - - - NOTE - In the previous code, 2.4.19 is the - recommended version of the kernel. You can replace this version number with your kernel version. - - - Copy the - evms_rediscover - utility to the init-ramdisk. If you - are not using devfs, copy the - evms_devnode_fixup utility - as well. - - - - - NOTE - evms_rediscover and evms_devnode_fixup - are statically linked with the necessary libraries and will not need any additional dynamic - libraries added to the init-ramdisk. - - - Edit the - linuxrc script on your - init-ramdisk so that it loads all of the EVMS kernel - modules and calls evms_rediscover, - followed by evms_ devnode_fixup (if you are not - running devfs). - - Add the following lines to the - linuxrc script. These - lines should be added to the - linuxrc script before the - root file system is mounted, so the root volume - will be discovered and available. - -insmod evms -insmod evms_passthru -insmod ldev_mgr -insmod dos_part -# Add insmod commands for all EVMS modules copied in the step above. -evms_rediscover -evms_devnode_fixup # If not running devfs - - +Activating EVMS volumes +In the previous EVMS design (releases 1.2.1 and earlier), volume discovery +was performed in the kernel, and all volumes were immediately activated at boot time. +With the current EVMS design, volume discovery is performed in user-space, and +volumes are activated by communicating with the kernel. Thus, in order to activate +your volumes, you must open one of the EVMS user interfaces and perform a save, +which will activate all inactive volumes. +For example, start the GUI by running evmsgui. You should see all empty +checkboxes in the "Active" column. Press Save, which +activates all of the volumes and fills in each of the checkboxes. +In addition to manually starting one of the EVMS user interfaces, there is a new +utility called evms_activate. +The evms_activate utility simply opens the EVMS Engine +and issues a commit command. +You might want to add a call to evms_activate to your +boot scripts in order to automatically activate your volumes at boot time. If +you have volumes listed in your /etc/fstab file, +you need to call evms_activate before the +fstab is processed. NOTE -For the 2.5 kernel replace insmod dos_part with -insmod dos in the script above. - - - - - - - - +EVMS requires /proc to be mounted in order +to find the Device Mapper driver. If you run evms_activate +before processing the fstab file, you might need +to manually mount and unmount /proc around the call +to evms_activate. + + +After the volumes are activated, you can mount them in the normal way with the dev-nodes in the /dev/evms directory. +The root filesystem on an EVMS volume +After volume discovery and activation are done in user space, there is an +issue with having your system's root file system on an EVMS volume. +In order for the root file system's volume to be activated, the EVMS tools must +run. However, in order to get to the EVMS tools, the root file system must be mounted. +The solution to this dilemma is to use an initial ramdisk (initrd). +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 . + +Setting up clustered EVMS +The following steps show how to set up EVMS clustering. Perform these steps on +each cluster node: + + +Because EVMS depends on the CCM services offered by Heartbeat, the +Linux-HA CCM service must be configured on the system. Execute the following +line to configure CCM: +echo 'respawn haclient /usr/lib/heartbeat/ccm' >> /etc/ha.d/ha.cf + +Because Linux-HA expects its consumers to set up a private communication +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.rsp +chmod 200 /var/lib/heartbeat/api/evms.req +chmod 600 /var/lib/heartbeat/api/evms.rsp + +To ensure that clustered EVMS is activated whenever Linux-HA starts, +execute the following line: +echo 'respawn root /sbin/evmsd' >> /etc/ha.d/ha.cf +This step assumes that the evmsd daemon is installed in +/sbin/evmsd. If +the evmsd daemon is not installed in /sbin/evmsd, +change /sbin/evmsd to the correct location when executing +the command. + + + +See for information about clustering +operations. + + + + \ No newline at end of file diff --git a/LDP/guide/docbook/EVMSUG/migrateto-ug.xml b/LDP/guide/docbook/EVMSUG/migrateto-ug.xml index 9b036b37..f16a7abc 100644 --- a/LDP/guide/docbook/EVMSUG/migrateto-ug.xml +++ b/LDP/guide/docbook/EVMSUG/migrateto-ug.xml @@ -1,11 +1,12 @@ -Viewing Compatibility Volumes after Migrating + +Viewing compatibility volumes after migrating Migrating to EVMS allows you to have the flexibility of EVMS without losing the integrity of your existing data. EVMS discovers existing volume management volumes as compatibility volumes. After you have installed EVMS, you can view your existing volumes with the interface of your choice. Using the EVMS GUI -If you are using the EVMS GUI as your preferred interface, you can view your migrated volumes by typing evmsgui at the command prompt. The following screen appears listing your migrated volumes. +If you are using the EVMS GUI as your preferred interface, you can view your migrated volumes by typing evmsgui at the command prompt. The following window opens, listing your migrated volumes. -
GUI Start-up Window - +
GUI start-up window + GUI start-up window
@@ -13,20 +14,19 @@ Using Ncurses If you are using the Ncurses interface, you can view your migrated volumes by - typing evmsn at the command prompt. The following screen will - appear listing your migrated volumes. + typing evmsn at the command prompt. The following window opens, listing your migrated volumes. -
Ncurses Start-up Window +
Ncurses start-up window - + - Ncurses Start-up Window
+ Ncurses start-up window
 Using the CLI If you are using the Command Line Interpreter (CLI) interface, you can view - your migrated volumes by typing the following: + your migrated volumes by following these steps: Start the Command Line Interpreter by typing evms at the command line. @@ -37,24 +37,9 @@ Your migrated volumes are displayed as results of the query. -
CLI Volume Query Results - - CLI Volume Query
+
CLI volume query results + + CLI volume query
 -Using Linux LVM Emulation Tools - If you are using the EVMS emulation of the Linux LVM command set, you can view - your Linux LVM migrated volumes by typing the following command: - evms_lvscan - -The following screen appears listing your migrated volumes. - -
EVMS Emulation of Linux LVM - - -EVMS Emulation of Linux LVM to view Linux LVM volumes.
 - - - - - + diff --git a/LDP/guide/docbook/EVMSUG/n.png b/LDP/guide/docbook/EVMSUG/n.png index 22cd3727..164bcee8 100644 Binary files a/LDP/guide/docbook/EVMSUG/n.png and b/LDP/guide/docbook/EVMSUG/n.png differ diff --git a/LDP/guide/docbook/EVMSUG/over-ug.xml b/LDP/guide/docbook/EVMSUG/over-ug.xml index ca7550e9..c500b1a8 100644 --- a/LDP/guide/docbook/EVMSUG/over-ug.xml +++ b/LDP/guide/docbook/EVMSUG/over-ug.xml @@ -1,28 +1,55 @@ -What Is EVMS? -Enterprise Volume Management System (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, and filesystem operations into a single cohesive package. With EVMS, various volume managemet technologies are accessible through one interface, and new technologies can be added as they are developed. -Why Choose EVMS? - EVMS allows you to manage your storage space in a way that is more intuitive and flexible than many other Linux volume management systems. Practical tasks such as migrating disks or adding new disks to your Linux system become more managable with EVMS because of its ability to recognize and read from different volume types and filesystems. EVMS provides additional safety controls by not allowing unsafe commands. These controls help maintain the integrity of the data stored on the system. -You can use EVMS to create and manage data storage. With EVMS, you can use multiple volume management technologies under one framework. With one framework, you can access many technologies while ensuring your system will still interact correctly with stored data. With EVMS, you are able to 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. You are also able to use many types of filesystems and manipulate these storage pieces in ways that best meet your needs for your particular work environment. - -EVMS provides a choice of user interfaces that allow you to manage your storage space. Additionally, if you need to design your own interface for EVMS, the system allows you to create customized interfaces. +What is EVMS? + +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 +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. + +Why choose EVMS? + EVMS lets you manage storage space in a way that is more +intuitive and flexible than many other Linux volume management systems. +Practical tasks, such as migrating disks or adding new disks to your +Linux system, become more manageable with EVMS because EVMS can +recognize and read from different volume types and file systems. +EVMS provides additional safety controls by not allowing commands that are +unsafe. +These controls help maintain the integrity of the data stored on the system. + +You can use EVMS to create and manage data storage. +With EVMS, you can use multiple volume management technologies under one +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. +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. + +EVMS also provides the capability to manage data on storage that is +physically shared by nodes in a cluster. This shared storage allows data to +be highly available from different nodes in the cluster. + -Why Are There Different User Interfaces? +The EVMS user interfaces -There are currently three user interfaces available for EVMS: graphical (GUI), text mode (Ncurses), and the Command Line Interpreter (CLI). You can use the EVMS Application Programming Interface to implement your own customized user interface. An example of a customized user interface is the EVMS emulation of the Linux LVM command set that comes standard with the EVMS download. - lists details about each of the user interfaces and when each is appropriate. +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. -EVMS User Interfaces - -User Interface -Typical User -Types of Use +
EVMS user interfaces + +User interface +Typical user +Types of use FunctionGUI All @@ -36,24 +63,21 @@ Expert All uses Allows easy automation of tasks -LVM Emulation Tools -Experienced LVM User -LVM manipulation -Allows users to keep old scripts and knowledge base with only slight changes. +
 -What Terms Does EVMS Use for Volume Management? - To avoid confusion with other terms used to describe volume - management, EVMS uses a set of terms specific to EVMS. The following list - defines volume management terms as they relate to EVMS. The terms - are listed from most fundamental to most comprehensive. +EVMS terminology + To avoid confusion with other terms that describe volume + management in general, EVMS uses a specific set of terms. + These terms are listed, from most fundamental to most comprehensive, + as follows: - Logical Disk + Logical disk Representation of anything EVMS can access as a physical disk. In EVMS, physical disks are logical disks. @@ -64,31 +88,62 @@ meaning found in other management systems. - Disk Segment + Disk segment An ordered set of physically contiguous sectors residing on the same storage object. The general analogy for a segment is to a traditional disk partition, such as DOS or OS/2 ® - Storage Region + Storage region An ordered set of logically contiguous sectors that are not necessarily physically contiguous. - Storage Object + Storage object Any persistent memory structure in EVMS that can be used to build objects or create a volume. Storage object is a generic term for disks, segments, regions, and feature objects. - Storage Container + Storage container A collection of storage objects. A storage container consumes one set of storage objects and produces new storage objects. One common subset of storage containers is volume groups, - such as AIX® or LVM. + such as AIX® or LVM. + Storage containers can be either of type private or cluster. + - Feature Object + Cluster storage container + Specialized storage containers that consume only disk objects + that are physically accessible from all nodes of a cluster. + + + Private 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 a single node of the cluster at any given time. + + + + + + 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. + + + + Deported storage container + A shared cluster container that is not owned by any node of the cluster. + + + + + + + Feature object A storage object that contains an EVMS native feature, such as bad block relocation. An EVMS Native Feature is a function of volume management designed @@ -97,67 +152,87 @@ volume management technologies. - Logical Volume + Logical volume A volume that consumes a storage object and exports something mountable. There are two varieties of logical volumes: EVMS Volumes - and Compatibility Volumes. + and Compatibility volumes. EVMS Volumes contain EVMS native metadata and can support all EVMS features. /dev/evms/my_volume would be an example of an EVMS Volume. - Compatibility Volumes do not contain any EVMS native metadata. + Compatibility volumes do not contain any EVMS native metadata. Compatibility volumes are backward compatible to their particular scheme, but they cannot support EVMS features. /dev/evms/md/md0 would be an example of a compatibility volume. -What Makes EVMS So Flexible? +What makes EVMS so flexible? -By dividing the labor between the Runtime and the Engine, EVMS reduces the size and kernel resources the system requires. The Runtime resides in kernel space and handles the actual use of the volumes. The Engine resides in user space and handles the creation, configuration, and management of volumes, segments, and disks. The EVMS Engine is a programmatic interface to the EVMS system. User interfaces and programs that use EVMS must go through the Engine. +There are numerous drivers in the Linux kernel, such as Device +Mapper and MD (software RAID), that implement volume management schemes. EVMS is built +on top of these drivers to provide one framework for combining and +accessing the capabilities. -EVMS provides the capacity for plug-in modules that allow EVMS to perform specialized tasks without altering the core code. These plug-in modules reside in kernel space and user space. A kernel space plug-in will have a corresponding user space plug-in module that provides the configuration and management tasks that are needed by the plug-in. The use of plug-in modules allow EVMS to be more extensible and customizable than other volume management systems. This design also allows EVMS to use only the resources needed to handle a volume. +The EVMS Engine handles the creation, +configuration, and management of volumes, segments, and disks. +The EVMS Engine is a programmatic interface to the EVMS system. +User interfaces and programs that use EVMS must go through the Engine. + +EVMS provides the capacity for plug-in modules to the Engine that +allow EVMS to perform specialized tasks without altering the core code. +These plug-in modules allow EVMS to be more extensible and customizable than +other volume management systems. + - - Plug-in Layer Definitions + + Plug-in layer definitions EVMS defines a layered architecture where plug-ins in each layer create abstractions of the layer or layers below. EVMS also allows most plug-ins to create abstractions of objects within the same layer. The following list defines these layers from the bottom up. - Device Managers - The first layer is the device managers. - These plug-ins communicate with the hardware device drivers to + Device managers + The first (bottom) layer consists + of device managers. + These plug-ins communicate with hardware device drivers to create the first EVMS objects. Currently, all devices are handled by a single plug-in. Future releases of EVMS might need additional device managers - to do network device management, such as for disks on a storage - area network (SAN). + for network device management (for example, to manage + disks on a storage area network (SAN)). - Segment Managers - The second layer is the segment managers. These plug-ins + Segment managers + The second layer consists of segment + managers. These plug-ins handle the segmenting, or partitioning, of disk drives. The Engine components can replace partitioning programs, such as fdisk and - Disk Druid, and the kernel components - can replace the in-kernel disk partitioning code. Segment - managers can also be "stacked," meaning that one segment manager - can take as input output from another segment manager. + Disk Druid, and EVMS + uses Device Mapper to replace the in-kernel disk + partitioning code. + Segment managers can also be "stacked," meaning that + one segment manager + can take as input the output from another segment + manager. EVMS provides the following segment managers: - DOS, GPT, and System/390® (S/390). Other segment manager + DOS, GPT, System/390® (S/390), Cluster, and BSD. Other segment manager plug-ins can be added to support other partitioning schemes. - Region Managers - The third layer is the region managers. This - layer is intended to provide a place for plug-ins that ensure - compatibility with existing volume management schemes in Linux - or other operating systems. Region managers are intended to - model systems that provide a logical abstraction above disks + Region managers + The third layer consists of region + managers. + This layer provides a place for plug-ins that ensure + compatibility with existing volume management schemes + in Linux and other operating systems. + Region managers are intended to model systems that + provide a logical abstraction above disks or partitions. - Like the segment managers, region managers can also be - stacked. Therefore, the input object(s) to a region manager can + Like segment managers, region managers can + also be stacked. + Therefore, the input object(s) to a region manager can be disks, segments, or other regions. There are currently four region manager plug-ins in EVMS: @@ -180,33 +255,35 @@ is based on linear linking of disk partitions, as well as bad-block relocation. The OS/2 LVM does not allow for modifications. - MD LVM + MD The Multi-Disk (MD) plug-in for RAID provides RAID levels linear, 0, 1, 4, and 5 in - software. MD is one plug-in that will appear as four region - managers you will be able to choose from. + software. MD is one plug-in that displays as four region + managers that you can choose from. - EVMS Features - The next layer is EVMS features. This layer is + EVMS features + The next layer consists of EVMS + features. This layer is where new EVMS-native functionality is implemented. EVMS features can be built on any object in the system, including - disks, segments, regions, or other feature objects. EVMS - features all share a common type of metadata, which makes - discovery of feature objects much more efficient, and recovery + disks, segments, regions, or other feature objects. + All EVMS features share a common type of metadata, + which makes discovery of feature objects much more + efficient, and recovery of broken features objects much more reliable. There are three - features currently available in EVMS: Drive Linking, Bad Block Relocation, - and Snapshotting. + features currently available in EVMS: drive linking, Bad + Block Relocation, and snapshotting. Drive Linking -The Drive Linking feature allows any +Drive linking allows any number of objects to be linearly concatenated together into a - single object. A Drive Linked volume can be expanded by + single object. A drive linked volume can be expanded by adding another storage object to the end or shrunk by removing the last object. Bad Block Relocation -The Bad Block Relocation (BBR) feature +Bad Block Relocation (BBR) monitors its I/O path and detects write failures (which can be caused by a damaged disk). In the event of such a failure, the data from that request is stored in a new location. BBR keeps @@ -230,28 +307,33 @@ File System Interface Modules - File System Interface Modules (FSIMs) are - the one layer of EVMS that exists only in user space. - These plug-ins are used to provide coordination with the - filesystems during certain volume management operations. For - instance, when expanding or shrinking a volume, the filesystem + File System Interface Modules (FSIMs) + provide coordination with the + file systems during certain volume management + operations. For + instance, when expanding or shrinking a volume, + the file system must also be expanded or shrunk to the appropriate size. - Ordering in this example is also important; a filesystem cannot - be expanded before the volume, and a volume cannot be shrunk - before the filesystem. The FSIMs allow EVMS to ensure this + Ordering in this example is also important; + a file system cannot + be expanded before the volume, and a volume cannot + be shrunk before the file system. + The FSIMs allow EVMS to ensure this coordination and ordering. - FSIMs also perform filesystem + FSIMs also perform file system operations from one of the EVMS user interfaces. For instance, - a user can make new filesystems and check existing filesystems + a user can make new file systems and check existing file systems by interacting with the FSIM. + + Cluster Manager Interface Modules + Cluster Manager Interface Modules, also + known as the EVMS Clustered Engine (ECE), interface + with the local cluster manager installed on the system. + The ECE provides a standardized ECE API to the Engine + while hiding cluster manager details from the Engine. - - - - - - - + + \ 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 ebda8809..a18d2295 100644 --- a/LDP/guide/docbook/EVMSUG/pref-ug.xml +++ b/LDP/guide/docbook/EVMSUG/pref-ug.xml @@ -1,26 +1,81 @@ - -Preface -This book is designed to address user's questions about Enterprise Volume Management System (EVMS) and provide a context for using EVMS. -For additional information about EVMS or to ask questions specific to your distribution, the EVMS mailing lists are an excellent resource. You can view the list archives or subscribe to the lists from the EVMS Project web site. - - -Listed below are descriptions for the various sections of this User Guide. - -Chapter 2: provides an oveview of some basic EVMS terms. - -Chapter 3: explains how to download, install, and configure EVMS. - -Chapter 4: reviews how to locate and fix /dev/ files. -Chapter 5: introduces the EVMS interfaces and explains how to navigate through each. -Chapter 6: provides an overview of how to view your existing files after you migrate to EVMS. -Chapter 7: introduces the types of segment managers and describes how to apply segment managers to disks using the various EVMS interfaces. -Chapter 8-11: offers scenarios and explanations of how and why you would create the most fundamental pieces of the EVMS storage system. -Chapter 12: explains how to convert volumes from EVMS native volumes to compatibility volumes and from compatibility volumes to EVMS native volumes. - - - +Preface +This guide tells how to install, 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. + +This guide is intended for Linux system administrators and users who are +responsible for setting up and maintaining EVMS. + +For additional information about EVMS or to ask questions specific to +your distribution, refer to the EVMS mailing lists. You can view the list +archives or subscribe to the lists from +the EVMS Project +web site. + +The following table shows how this guide is organized: +Organization of the EVMS User Guide + +Chapter or appendix title +Contents +1. 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 +Describes the three EVMS user interfaces and how to use them. +4. 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 +Tells how to view existing files that have been migrated to EVMS. +6. 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 +Explains when and how to create segments. +9. Creating containers +Discusses containers and explains when and how to create them. +10. Creating regions +Discusses regions and explains when and how to create them. +11. Creating drive links +Discusses the drive linking feature and tells how to create a drive link. +12. 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 +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 +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 +Tells how to add additional features, such as drive linking and bad block relocation, to an existing volume. +19. 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 +Provides details about the DOS link plug-in, which is a segment manager plug-in. +C. The MD region manager +Explains the Multiple Disks (MD) support in Linux that is a software implementation of RAID. +D. The LVM plug-in +Tells how the LVM plug-in is implemented and how to perform container operations. +E. 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 +Provides information about the JFS FSIM. +G. XFS file system interface module +Provides information about the XFS FSIM. +H. ReiserFS file system interface module +Provides information about the ReiserFS FSIM. +I. Ext-2/3 file system interface module +Provides information about the Ext-2/3 FSIM. + +
+ \ No newline at end of file