2.1.1. 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 of the main "views." Each view corresponds to a 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, 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 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, choose Action-><the action you want to accomplish>-><options>. 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 the Actions menu.

2.1.2. 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 are reminded to save any pending changes.

To explicitly save all the changes you made, select Action->Save, and click the Save button.

2.1.3. 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.

2.1.4. 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.

2.1.5. 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.

2.2.1. 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. 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 window is listed below:

• Tab cycles you through the available views.

• Status messages and tips are displayed on the last line of the screen.

• 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.

• Typing A + Q in a view quits the application.

• Typing A + S in a view saves changes made during an evmsn session.

• 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.

• 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.

Dialog windows are similar in design to the EVMS GUI dialogs, which allow a user to navigate forward and backward through a series of dialogs using Next and Previous. A general guide to dialog windows is listed below:

• 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.

2.2.2. Saving changes

All changes you make while in the EVMS Ncurses are only in memory until you save the changes. In order to make the changes permanent, save all changes before exiting. If you 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, press A + S and confirm that you want to save changes.

2.3.1. 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 starts in interactive mode. In interactive mode, the EVMS CLI prompts 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:

	NOTE
	Information on less commonly used options is available in the EVMS man page.

2.3.2. Notes on commands and command files

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) be present between commands.

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 shown in the following example:

"This is a name containing ""embedded"" quote marks."

EVMS CLI keywords are not case sensitive, but EVMS names are case sensitive. Sizes can be input in any units with a unit label, such as KB, MB, GB, or TB.

Finally, C programming language style comments are supported by the EVMS CLI. Comments can begin and end anywhere except within a quoted string, as shown in the following example:

/* This is a comment */
Create:Vo/*This is a silly place for a comment, but it is
allowed.*/lume,"lvm/Sample Container/My LVM
Volume",compatibility

6.2.1. DOS Segment Manager

The most commonly used segment manager is the DOS Segment Manager. This plug-in provides support for traditional DOS disk partitioning. The DOS Segment Manager also recognizes and supports the following variations of the DOS partitioning scheme:

• OS/2: an OS/2 disk has additional metadata sectors that contain information needed to reconstruct disk segments.

• Embedded partitions: support for BSD, SolarisX86, and UnixWare is sometimes found embedded in primary DOS partitions. The DOS Segment Manager recognizes and supports these slices as disk segments.

6.2.2. GUID Partitioning Table (GPT) Segment Manager

The GUID Partitioning Table (GPT) Segment Manager handles the new GPT partitioning scheme on IA-64 machines. The Intel Extensible Firmware Interface Specification requires that firmware be able to discover partitions and produce logical devices that correspond to disk partitions. The partitioning scheme described in the specification is called GPT due to the extensive use of Globally Unique Identifier (GUID) tagging. GUID is a 128 bit long identifier, also referred to as a Universally Unique Identifier (UUID). As described in the Intel Wired For Management Baseline Specification, a GUID is a combination of time and space fields that produce an identifier that is unique across an entire UUID space. These identifiers are used extensively on GPT partitioned disks for tagging entire disks and individual partitions. GPT partitioned disks serve several functions, such as:

• keeping a primary and backup copy of metadata

• replacing msdos partition nesting by allowing many partitions

• using 64 bit logical block addressing

• tagging partitions and disks with GUID descriptors

The GPT Segment Manager scales better to large disks. It provides more redundancy with added reliability and uses unique names. However, the GPT Segment Manager is not compatible with DOS, OS/2, or Windows�.

6.2.3. S/390 Segment Manager

The S/390 Segment Manager is used exclusively on System/390 mainframes. The S/390 Segment Manager has the ability to recognize various disk layouts found on an S/390 machine, and provide disk segment support for this architecture. The two most common disk layouts are Linux Disk Layout (LDL) and Common Disk Layout (CDL).

The principle difference between LDL and CDL is that an LDL disk cannot be further subdivided. An LDL disk will produce a single metadata disk segment and a single data disk segment. There is no freespace on an LDL disk, and you cannot delete or re-size the data segment. A CDL disk can be subdivided into multiple data disk segments because it contains metadata that is missing from an LDL disk, specifically the Volume Table of Contents (vtoc) information.

The S/390 Segment Manager is the only segment manager plug-in capable of understanding the unique S/390 disk layouts. The S/390 Segment Manager cannot be added or removed from a disk.

6.2.4. Cluster segment manager

The cluster segment manager (CSM) supports high availability clusters. When the CSM is added to a shared storage disk, it writes metadata on the disk that:

• 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 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 disks discovered by the CSM and belonging to the same container. These shared storage disks are consumed by the container and a single data segment is produced by the container for each consumed disk. A failover of the EVMS resource is accomplished by simply reassigning the CSM container to the standby cluster node and having that node re-run its discovery process.

Adding disks to CSM containers implies that only disk storage objects are acceptable to the CSM. This is an important aspect of the CSM. Other segment managers can be embedded within storage objects and used to further subdivide them. However, the CSM cannot add any other kind of storage object to a CSM container because the container is meant to be a disk group and the entire disk group is reassigned during a failover. So, the CSM only accepts disks when constructing containers. This is important to remember when adding the CSM to a disk. If you choose Add and the CSM does not appear in the list of selectable plug-ins when you know you have a disk, you should look at the Volume list and see if the disk has already been listed as a compatibility volume. If you simply delete the volume, the disk will become an available object and the CSM will then appear in the list of plug-ins because it now has an available disk that it can add to a container.

6.2.5. 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.

6.2.6. MAC segment manager

Apple-partitioned disks use a disk label that is recognized by the MAC segment manager. The MAC segment manager recognizes the disk label during discovery and creates EVMS segments to map the MacOS disk partitions.

6.2.7. BBR segment manager

The bad block replacement (BBR) segment manager enhances the reliability of a disk by remapping bad storage blocks. When BBR is added to a disk, it writes metadata on the disk that:

• reserves replacement blocks

• maps bad blocks to reserved blocks

Bad blocks occur when an I/O error is detected for a write operation. When this happens, I/O normally fails and the failure code is returned to the calling program code. BBR detects failed write operations and remaps the I/O to a reserved block on the disk. Afterward, BBR restarts the I/O using the reserve block.

Every block of storage has an address, called a logical block address, or LBA. When BBR is added to a disk, it provides two critical functions: remap and recovery. When an I/O operation is sent to disk, BBR inspects the LBA in the I/O command to see if the LBA has been remapped to a reserve block due to some earlier I/O error. If BBR finds a mapping between the LBA and a reserve block, it updates the I/O command with the LBA of the reserve block before sending it on to the disk. Recovery occurs when BBR detects an I/O error and remaps the bad block to a reserve block. The new LBA mapping is saved in BBR metadata so that subsequent I/O to the LBA can be remapped.

6.5.1. Using the EVMS GUI

To add the DOS Segment Manager to sde, first remove the volume, /dev/evms/sde:

1. Select Actions->Delete->Volume.

2. Select /dev/evms/sde.

3. Click Delete.

Alternatively, you can remove the volume through the GUI context sensitive menu:

1. From the Volumes tab, right click /dev/evms/sde.

2. Click Delete.

After the volume is removed, add the DOS Segment Manager:

1. Select Actions->Add->Segment Manager to Storage Object.

2. Select DOS Segment Manager.

3. Click Next.

4. Select sde

5. Click Add

6.5.2. Using Ncurses

To add the DOS Segment Manager to sde, first remove the volume /dev/evms/sde:

1. Select Actions->Delete->Segment Manager to Storage Object.

2. Select /dev/evms/sde.

3. Activate Delete.

Alternatively, you can remove the volume through the context sensitive menu:

1. From the Logical Volumes view, press Enter on /dev/evms/sde.

2. Activate Delete.

After the volume is removed, add the DOS Segment Manager:

1. Select Actions->Add->Segment Manager to Storage Object

2. Select DOS Segment Manager.

3. Activate Next.

4. Select sde.

5. Activate Add.

6.5.3. Using the CLI

To add the DOS Segment Manager to sde, first tell EVMS that this disk is not a volume and is available for use:

Delete:/dev/evms/sde

Next, add the DOS Segment Manager to sde by typing the following:

Add:DosSegMgr={},sde

6.7.1. Using the EVMS GUI context sensitive menu

Follow these steps to remove a segment manager with the GUI context sensitive menu:

1. From the Volumes tab, right click /dev/evms/sda1..

2. Click Delete.

3. Select Actions->Remove->Segment Manager from Storage Object.

4. Select DOS Segment Manager, sda.

5. Click Remove.

6.7.2. Using Ncurses

Follow these steps to remove a segment manager with the Ncurses interface:

1. Select Actions->Delete->Volume.

2. Select /dev/evms/sda1.

3. Activate Delete.

4. Select Actions->Remove->Segment Manager from Storage Object.

5. Activate Remove.

6.7.3. Using the CLI

Follow these steps to remove a segment manager with the CLI:

Delete:/dev/evms/sda1

Remove: sda

7.2.1. Using the EVMS GUI

To create a segment using the GUI, follow the steps below:

1. Select Actions->Create->Segment to see a list of segment manager plug-ins.

2. Select DOS Segment Manager. Click Next.

   The next dialog window lists the free space storage objects suitable for creating a new segment.

3. Select sde_freespace1. Click Next.

   The last dialog window presents the free space object you selected as well as the available configuration options for that object.

4. Enter 100 MB. 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.

   After you have filled in information for all the required fields, the Create button becomes available.

5. 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:

1. From the Segments tab, right click on sde_freespace1.

2. Click Create Segment...

3. Continue beginning with step 4 of the GUI instructions.

7.2.2. Using Ncurses

To create a segment using Ncurses, follow these steps:

1. Select Actions->Create->Segment to see a list of segment manager plug-ins.

2. Select DOS Segment Manager. Activate Next.

   The next dialog window lists free space storage objects suitable for creating a new segment.

3. Select sde_freespace1. Activate Next.

4. Highlight the size field and press spacebar.

5. At the "::" prompt enter 100MB. Press Enter.

6. After all required values have been completed, the Create button becomes available.

7. Activate Create.

Alternatively, you can perform some of the steps to create a segment from the context sensitive menu:

1. From the Segments view, press Enter on sde_freespace1.

2. Activate Create Segment.

3. Continue beginning with step 4 of the Ncurses instructions.

7.2.3. Using the CLI

To create a data segment from a freespace segment, use the Create command. The arguments the Create command accepts vary depending on what is being created. The first argument to the Create command indicates what is to be created, which in the above example is a segment. The remaining arguments are the freespace segment to allocate from and a list of options to pass to the segment manager. The command to accomplish this is:

Create: Segment,sde_freespace1, size=100MB

	NOTE
	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

8.2.1. Using the EVMS GUI

To create a container using the EVMS GUI, follow these steps:

1. Select Actions->Create->Container to see a list plug-ins that support container creation.

2. Select the LVM Region Manager. Click Next.

   The next dialog window contains a list of storage objects that the LVM Region Manager can use to create a container.

3. Select sdc, sdd, and hdc from the list. Click Next.

4. Enter the name Sample Container for the container and 16MB in the PE size field.

5. Click Create. A window opens to display the outcome.

8.2.2. Using Ncurses

To create a container using the Ncurses interface, follow these steps:

1. Select Actions->Create->Container to see a list of plug-ins that support container creation.

2. 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.

3. Select sdc, sdd, and hdc from the list. Activate Next.

4. Press spacebar to select the field for the container name.

5. Type Sample Container at the "::" prompt. Press Enter.

6. Scroll down until PE Size is highlighted. Press spacebar.

7. Scroll down until 16MB is highlighted. Press spacebar.

8. Activate OK.

9. Activate Create.

8.2.3. Using the CLI

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 previous example is:

Create:Container,LvmRegMgr={name="Sample Container",pe_size=16MB},sdc,sdd,hdc

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

9.2.1. Using the EVMS GUI

To create a region, follow these steps:

1. Select Actions->Create->Region

2. Select the LVM Region Manager. Click Next.

   	NOTE
   	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.

3. Select the freespace region from the container you created in Chapter 8. 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.

4. Fill in the name, Sample Region.

5. Enter 1000MB in the size field.

6. Click the Create button to complete the 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:

1. From the Regions tab, right click lvm/Sample Container/Freespace.

2. Click Create Region.

3. Continue beginning with step 4 of the GUI instructions.

9.2.2. Using Ncurses

To create a region, follow these steps:

1. Select Actions->Create->Region.

2. Select the LVM Region Manager. Activate Next.

3. Select the freespace region from the container you created earlier in Chapter 8. Verify that the region is named lvm/Sample Container/Freespace.

4. Scroll to the Name field, and press spacebar.

5. Type Sample Region at the "::" prompt. Press Enter.

6. Scroll to the size field, and press spacebar.

7. Type 1000MB at the "::" prompt. Press Enter.

8. Activate Create.

Alternatively, you can perform some of the steps for creating a region with the context sensitive menu:

1. From the Storage Regions view, press Enter on lvm/Sample Container/Freespace.

2. Activate the Create Region menu item.

3. Continue beginning with step 4 of the Ncurses instructions.

9.2.3. Using the CLI

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"

The LVM Region Manager supports many options for creating regions. To see the available options for creating regions and containers, use the following Query:

query:plugins,plugin=LvmRegMgr,list options

10.4.1. Using the EVMS GUI

To create the drive link using the GUI, follow these steps:

1. Select Actions->Create->Feature Object to see a list of EVMS features.

2. Select Drive Linking Feature.

3. Click Next.

4. Click the objects you want to compose the drive link: sde4 and hdc2.

5. Click Next.

6. Type dl in the "name" field

7. Click Create.

   The last dialog window presents the free space object you selected as well as the available configuration options for that object.

Alternatively, you can perform some of the steps to create a drive link with the GUI context sensitive menu:

1. From the Available Objects tab, right click sde4.

2. Click Create Feature Object...

3. Continue creating the drive link beginning with step 2 of the GUI instructions. In step 4, sde4 is selected for you. You can also select hdc2.

10.4.2. Using Ncurses

To create the drive link, follow these steps:

1. Select Actions->Create->Feature Object to see a list of EVMS features.

2. Select Drive Linking Feature.

3. Activate Next.

4. Use spacebar to select the objects you want to compose the drive link from: sde4 and hdc2.

5. Activate Next.

6. Press spacebar to edit the Name field.

7. Type dl at the "::" prompt. Press Enter.

8. Activate Create.

Alternatively, you can perform some of the steps to create a drive link with the context sensitive menu:

1. From the Available Objects view, press Enter on sde4.

2. Activate the Create Feature Object menu item.

3. Continue creating the drive link beginning with step 4 of the Ncurses instructions. sde4 will be pre-selected. You can also select hdc2.

10.4.3. Using the CLI

Use the create command to create a drive link through the CLI. You pass the "object" keyword to the create command, followed by the plug-in and its options, and finally the objects.

To determine the options for the plug-in you are going to use, issue the following command:

query: plugins, plugin=DriveLink, list options

Now construct the create command, as follows:

create: object, DriveLink={Name=dl}, sde4, hdc2

11.3.1. Using the EVMS GUI

To create the snapshot using the GUI, follow these steps:

1. Select Actions->Create->Feature Object to see a list of EVMS feature objects.

2. Select Snapshot Feature.

3. Click Next.

4. Select lvm/Sample Container/Sample Region.

5. Click Next.

6. Select /dev/evms/vol from the list in the "Volume to be Snapshotted" field.

7. Type snap in the "Snapshot Object Name" field.

8. Click Create.

Alternatively, you can perform some of the steps to create a snapshot with the GUI context sensitive menu:

1. From the Available Objects tab, right click lvm/Sample Container/Sample Region.

2. Click Create Feature Object...

3. Continue creating the snapshot beginning with step 2 of the GUI instructions. You can skip steps 4 and 5 of the GUI instructions.

11.3.2. Using Ncurses

To create the snapshot, follow these steps:

1. Select Actions->Create->Feature Object to see a list of EVMS feature objects.

2. Select Snapshot Feature.

3. Activate Next.

4. Select lvm/Sample Container/Sample Region.

5. Activate Next.

6. Press spacebar to edit the "Volume to be Snapshotted" field.

7. Highlight /dev/evms/vol and press spacebar to select.

8. Activate OK.

9. Highlight "Snapshot Object Name" and press spacebar to edit.

10. Type snap at the "::" prompt. Press Enter.

11. Activate Create.

Alternatively, you can perform some of the steps to create a snapshot with the context sensitive menu:

1. From the Available Objects view, press Enter on lvm/Sample Container/Sample Region.

2. Activate the Create Feature Object menu item.

3. Continue creating the snapshot beginning with step 6 of the Ncurses instructions.

11.3.3. Using the CLI

Use the create command to create a snapshot through the CLI. You pass the "Object" keyword to the create command, followed by the plug-in and its options, and finally the objects.

To determine the options for the plug-in you are going to use, issue the following command:

query: plugins, plugin=Snapshot, list options

Now construct the create command, as follows:

create: object, Snapshot={original=/dev/evms/vol, snapshot=snap}, 
"lvm/Sample Container/Sample Region"

11.4.1. Using the EVMS GUI or Ncurses

To reinitialize a snapshot, follow these steps:

1. Select Actions->Other->Storage Object Tasks

2. Select the volume "snap."

3. Click or activate Next.

4. Select Reset.

5. Click or activate Next.

6. Click or activate Reset on the action panel.

7. Click or activate Reset on the warning panel.

Alternatively, you can perform these same steps with the context sensitive menus:

1. From the Feature Objects panel, right click (or press Enter on) the object snap.

2. Click or activate Reset on the popup menu.

3. Click or activate Reset on the action panel.

4. Click or activate Reset on the warning panel.

11.4.2. Using the CLI

Follow these steps to reinitialize a snapshot with the CLI:

1. Issue the following command to the CLI:

   task:reset,snap

2. Press Enter to select "Reset" (the default choice) at the warning message.

11.5.1. Using the EVMS GUI or Ncurses

To create the snapshot using the GUI or Ncurses, follow these steps:

1. Select Actions->Expand->Volume to see a list of EVMS feature objects.

2. Select the volume /dev/evms/snap.

3. Click or activate Next.

4. Select lvm/Sample Container/Sample Region. This object is the object that will actually be expanded.

5. Click or activate Next.

6. Select the options for expanding the LVM region, including the amount of extra space to add to the region.

7. Click or activate Expand.

Alternatively, you can perform the same steps using the context sensitive menus.

1. From the Volumes panel, right click (or press Enter on) /dev/evms/snap.

2. Select Expand from the popup menu.

3. Click or activate Next.

4. Select the region lvm/Sample Container/Sample Region. This is the object that will actually be expanded.

5. Click or activate Next.

6. Select the options for expanding the LVM region, including the amount of extra space to add to the region.

7. Click or activate Expand.

11.5.2. Using the CLI

The CLI expands volumes by targeting the object to be expanded. The CLI automatically handles expanding the volume and other objects above the volume in the volume stock. As with a regular expand operation, the options are determined by the plug-in that owns the object being expanded.

Issue the following command to determine the expand options for the region lvm/Sample Container/Sample Region:

query:region,region="lvm/Sample Container/Sample Region",lo

The option to use for expanding this region is called "add_size." Issue the following command to expand the snapshot by 100 MB:

expand:"lvm/Sample Container/Sample Region", add_size=100MB

11.7.1. Using the EVMS GUI or Ncurses

Follow these steps to roll back a snapshot with the EVMS GUI or Ncurses:

1. Select Actions->Other->Storage Object Tasks+.+ +

2. Select the object "snap."

3. Click or activate Next.

4. Select Rollback

   .

5. Click or activate Next.

6. Click or activate Rollback on the action panel.

7. Click or activate Rollback on the warning panel.

Alternatively, you can perform these same steps with the context-sensitive menus:

1. From the Feature Objects panel, right click (or press Enter on) the object "snap."

2. Click or activate Rollback on the popup menu.

3. Click or activate Rollback on the action panel.

4. Click or activate Rollback on the warning panel.

11.7.2. Using the CLI

Follow these steps to roll back a snapshot with the CLI:

1. Issue the following command to the CLI:

   task:rollback,snap

2. Press Enter to select "Rollback" (the default choice) at the warning message.

12.2.1. Using the EVMS GUI

Follow these instructions to create an EVMS volume:

1. Select Actions->Create->EVMS Volume.

2. Choose lvm/Sample Container/Sample Region.

3. Type Sample Volume in the name field.

4. Click Create.

Alternatively, you can perform some of the steps to create an EVMS volume from the GUI context sensitive menu:

1. From the Available Options tab, right click lvm/Sample Container/Sample Region.

2. Click Create EVMS Volume...

3. Continue beginning with step 3 of the GUI instructions.

12.2.2. Using Ncurses

To create a volume, follow these steps:

1. Select Actions->Create->EVMS Volume.

2. Enter Sample Volume at the "name" prompt. Press Enter.

3. Activate Create.

Alternatively, you can perform some of the steps to create an EVMS volume from the context sensitive menu:

1. From the Available Objects view, press Enter on lvm/Sample Container/Sample Region.

2. Activate the Create EVMS Volume menu item.

3. Continue beginning with step 3 of the Ncurses instructions.

12.2.3. Using the CLI

To create a volume, use the Create command. The arguments the Create command accepts vary depending on what is being created. In the case of the example, the first argument is the key word volume that specifies what is being created. The second argument is the object being made into a volume, in this case lvm/Sample Container/Sample Region. The third argument is type specific for an EVMS volume, Name=, followed by what you want to call the volume, in this case Sample Volume. The following command creates the volume from the example.

Create: Volume, "lvm/Sample Container/Sample Region", Name="Sample Volume"

12.3.1. Using the GUI

To create a compatibility volume, follow these steps:

1. Select Actions->Create->Compatibility Volume.

2. Choose the region lvm/Sample Container/Sample Region from the list.

3. Click the Create button.

4. 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:

1. From the Available Objects tab, right click lvm/Sample Container/Sample Region.

2. Click Create Compatibility Volume...

3. Continue beginning with step 3 of the GUI instructions.

12.3.2. Using Ncurses

To create a compatibility volume, follow these steps:

1. Select Actions->Create->Compatibility Volume.

2. Choose the region lvm/Sample Container/Storage Region from the list..

3. Activate Create.

Alternatively, you can perform some of the steps to create a compatibility volume from the context sensitive menu:

1. From the Available Objects view, press Enter on lvm/Sample Container/Sample Region.

2. Activate the Create Compatibility Volume menu item.

3. Continue beginning with step 3 of the Ncurses instructions.

12.3.3. Using the CLI

To create a volume, use the Create command. The arguments the Create command accepts vary depending on what is being created. In the case of the example, the first argument is the key word volume that specifies what is being created. The second argument is the object being made into a volume, in this case lvm/Sample Container/Sample Region. The third argument, compatibility, indicates that this is a compatibility volume and should be named as such.

Create:Volume,"lvm/Sample Container/Sample Region",compatibility

13.1.1. JFS

The JFS module supports the IBM journaling file system (JFS). Current support includes mkfs, unmkfs, fsck, and online file system expansion. You must have at least version 1.0.9 of the JFS utilities for your system to work with this EVMS FSIM. You can download the latest utilities from the JFS for Linux site.

For more information on the JFS FSIM, refer to Appendix F.

13.1.2. XFS

The XFS FSIM supports the XFS file system from SGI. Command support includes mkfs, unmkfs, fsck, and online expansion. Use version 1.2 or higher, which you can download from the SGI open source FTP directory.

For more information on the XFS FSIM, refer to Appendix G.

13.1.3. ReiserFS

The ReiserFS module supports the ReiserFS journaling file system. This module supports mkfs, unmkfs, fsck, online and offline expansion and offline shrinkage. You need version 3.x.1a or higher of the ReiserFS utilities for use with the EVMS FSIM modules. You can download the ReiserFS utilities from The Naming System Venture (Namesys) Web site.

For more information on the ReiserFS FSIM, refer to Appendix H.

13.1.4. Ext2/3

The EXT2/EXT3 FSIM supports both the ext2 and ext3 file system formats. The FSIM supports mkfs, unmkfs, fsck, and offline shrinkage and expansion.

For more information on the Ext2/3 FSIM, refer to Appendix I.

13.1.5. SWAPFS

The SWAPFS FSIM supports Linux swap devices. The FSIM lets you create and delete swap devices, and supports mkfs, unmkfs, shrinkage and expansion. Currently, you are responsible for issuing the swapon and swapoff commands either in the startup scripts or manually. You can resize swap device with the SWAPFS FSIM as long as the device is not in use.

13.1.6. OpenGFS

The OpenGFS module supports the OpenGFS clustered journaling file system. This module supports mkfs, unmkfs, fsck, and online expansion. You need the OpenGFS utilities for use with the EVMS FSIM module. You can download the OpenGFS utilities from the OpenGFS project on SourceForge.

For more information on the OpenGFS FSIM, refer to Appendix J.

13.1.7. NTFS

The NTFS FSIM supports the NTFS file system format. The FSIM supports mkfs, unmkfs, and offline shrinkage and expansion. It also has support for running the ntfsfix and netfsclone from the ntfsprogs utilities. You can download the ntfsprogs utilities from the Linux NTFS project web site.

For more information on the NTFS FSIM, refer to Appendix K.

13.2.1. Using the EVMS GUI

Follow these steps to create a JFS file system with the EVMS GUI:

1. Select Actions->File Systems->Make.

2. Select JFS File System Interface Module.

3. Click Next.

4. Select /dev/evms/my_vol.

5. Click Next.

6. Type jfs_vol in the "Volume Label" field. Customize any other options you are interested in.

7. Click Make.

8. The operation is completed when you save.

Alternatively, you can perform some of the steps to create a file system with the GUI context sensitive menu:

1. From the Volumes tab, right click /dev/evms/my_vol.

2. Click Make Filesystem...

3. Continue creating the file system beginning with step 2 of the GUI instructions. You can skip steps 4 and 5 of the GUI instructions.

13.2.2. Using Ncurses

Follow these steps to create a JFS file system with Ncurses:

1. Select Actions->File Systems->Make.

2. Select JFS File System Interface Module.

3. Activate Next.

4. Select /dev/evms/my_vol.

5. Activate Next.

6. Scroll down using the down arrow until Volume Label is highlighted.

7. Press Spacebar.

8. At the "::" prompt enter jfs_vol.

9. Press Enter.

10. Activate Make.

Alternatively, you can perform some of the steps to create a file system with the context sensitive menu:

1. From the Volumes view, press Enter on /dev/evms/my_vol.

2. Activate the Make Filesystem menu item.

3. Continue creating the file system beginning with step 2 of the Ncurses instructions.

13.2.3. Using the CLI

Use the mkfs command to create the new file system. The arguments to mkfs include the FSIM type (in our example, JFS), followed by any option pairs, and then the volume name. The command to accomplish this is:

mkfs: JFS={vollabel=jfs_vol}, /dev/evms/my_vol

The command is completed upon saving.

If you are interested in other options that mkfs can use, look at the results of the following query:

query: plugins, plugin=JFS, list options

13.3.1. Using the EVMS GUI

Follow these steps to check a JFS file system with the EVMS GUI:

1. Select Actions->File Systems->Check/Repair.

2. Select /dev/evms/my_vol.

3. Click Next.

4. Click the Yes button by Verbose Output. Customize any other options you are interested in.

5. Click Check.

6. The operation is completed when you save.

Alternatively, you can perform some of the steps to check a file system with the GUI context sensitive menu:

1. From the Volumes tab, right click /dev/evms/my_vol.

2. Click Check/Repair File System...

3. Continue checking the file system beginning with step 3 of the GUI instructions.

13.3.2. Using Ncurses

Follow these steps to check a JFS file system with Ncurses:

1. Select Actions->File System->Check/Repair

2. Select /dev/evms/my_vol.

3. Activate Next.

4. Scroll down using the down arrow until Verbose Output is highlighted.

5. Press Spacebar to change Verbose Output to Yes.

6. Activate Check.

Alternatively, you can perform some of the steps to check a file system with the context sensitive menu:

1. From the Volumes view, press Enter on /dev/evms/my_vol.

2. Activate the Check/Repair File System menu item.

3. Continue checking the file system beginning with step 3 of the Ncurses instructions.

13.3.3. Using the CLI

The CLI check command takes a volume name and options as input. The command to check the file system on /dev/evms/my_vol is the following:

check: /dev/evms/my_vol, verbose=TRUE

Currently, a query command for viewing additional options is not available.

14.2.1. Using the EVMS GUI

To create a container with the EVMS GUI, follow these steps:

1. Select Actions->Create->Container to see a list of plug-ins that support container creation.

2. Select the Cluster Segment Manager.

3. Click Next.

   The next dialog window contains a list of storage objects that the CSM can use to create a container.

4. Select sdd, sde, and sdf from the list.

5. Click Next.

6. In the first pull-down menu, select the "Node Id" of the cluster node that owns this container (node1). Select "Storage Type" as private from the second pull-down menu.

7. Enter the name Priv1 for the Container Name.

8. Click Create.

   A window opens that displays the outcome.

9. Commit the changes.

14.2.2. Using Ncurses

To create the private container with the Ncurses interface, follow these steps:

1. Select Actions->Create->Container to see a list of plug-ins that support container creation.

2. Scroll down with the down arrow and select Cluster Segment Manager by pressing spacebar. The plug-in you selected is marked with an "x."

3. Press Enter.

   The next submenu contains a list of disks that the Cluster Segment Manager finds acceptable to use for the creation of a container.

4. Use spacebar to select sdd, sde, and sdf from the list. The disks you select are marked with an "x."

5. Press Enter.

6. On the Create Storage Container - Configuration Options menu, press spacebar on the Node Id, which will provide a list of nodes from which to select.

7. Press spacebar on the node node1 and then press Enter.

8. Scroll down with the down arrow and press spacebar on the Storage Type. A list of storage types opens.

9. Scroll down with the down arrow to private entry and press spacebar.

10. Press Enter.

11. Scroll down with the down arrow to Container Name and press spacebar.

    The Change Option Value menu opens and asks for the Container Name. Type in the name of the container as Priv1, and press Enter.

12. Press Enter to complete the operation.

14.2.3. Using the CLI

An operation to create a private cluster container with the CLI takes three parameters: the name of the container, the type of the container, and the nodeid to which the container belongs.

On the CLI, type the following command to create the private container Priv1:

create: container,CSM={name="Priv1",type="private",nodeid="node1"},sdd,sde,sdf

14.3.1. Using the EVMS GUI

To create a shared cluster container with the EVMS GUI, follow these steps:

1. Select Actions->Create->Container to see a list of plug-ins that support container creation.

2. Select the Cluster Segment Manager.

3. Click Next.

   The next dialog window contains a list of storage objects that the CSM can use to create a container.

4. Select sdd, sde, and sdf from the list.

5. Click Next.

6. You do not need to change the "Node Id" field. Select Storage Type as shared from the second pull-down menu.

7. Enter the name Shar1 for the Container Name.

8. Click Create. A window opens to display the outcome.

9. Commit the changes.

14.3.2. Using Ncurses

To create a shared cluster contained with the Ncurses interface, follow these steps:

1. Select Actions->Create->Container to see a list of plug-ins that support container creation.

2. Scroll down with the down arrow and select Cluster Segment Manager by pressing spacebar. The plug-in you selected is marked with an "x."

3. Press Enter.

   The next submenu contains a list of disks that the Cluster Segment Manager finds acceptable to use for the creation of a container.

4. Use spacebar to select sdd, sde, and sdf from the list. The disks you select are marked with an "x."

5. Press Enter.

6. The Create Storage Container - Configuration Options menu open; ignore the "Node Id" menu.

7. Scroll down with the down arrow and press spacebar on the Storage Type. A list of storage types opens.

8. Scroll down with the down arrow to shared entry and press spacebar.

9. Press Enter.

10. Scroll down with the down arrow to Container Name and press spacebar.

    The Change Option Value menu opens and asks for the Container Name. Type in the name of the container as Shar1, and press Enter.

11. Press Enter to complete the operation.

12. Quit Ncurses and run evms_activate on each of the cluster nodes. This process will be automated in future releases of EVMS.

14.3.3. Using the CLI

An operation to create a shared cluster container with the CLI takes two parameters: the name of the container and the type of the container.

On the CLI, type the following command to create shared container Shar1:

create: container,CSM={name="Shar1",type="shared"},sdd,sde,sdf

14.4.1. Using the EVMS GUI

Follow these steps to convert a private cluster container to a shared cluster container with the EVMS GUI:

1. Select Actions->Modify->Container to see a list of containers.

2. Select the container Priv1 and press Next.

   A Modify Properties dialog box opens.

3. Change "Type" to "shared" and click Modify.

   A window opens that displays the outcome.

4. Commit the changes.

14.4.2. Using Ncurses

Follow these steps to convert a private cluster container to a shared cluster container with the Ncurses interface:

1. Select Actions->Modify->Container to see a list of containers.

2. The Modify Container Properties dialog opens. Select the container Priv1 by pressing spacebar. The container you selected is marked with an "x."

   Press Enter.

3. Use spacebar to select sdd, sde, and sdf from the list. The disks you select are marked with an "x."

4. Press Enter.

5. The Modify Container Properties - Configuration Options" dialog opens. Scroll down with the down arrow and press spacebar on "Type".

6. Press spacebar.

7. The Change Option Value dialog opens. Type shared and press Enter.

   The changed value now displays in the Modify Container Properties - Configuration Options dialog.

8. Press Enter.

   The outcome of the command is displayed at the bottom of the screen.

9. Save the changes by clicking Save in the Actions pulldown menu.

14.4.3. Using the CLI

The modify command modifies the properties of a container. The first argument of the command is the object to modify, followed by its new properties. The command to convert the private container to a shared container in the example is:

modify: Priv1,type=shared

14.5.1. Using the EVMS GUI

Follow these steps to convert a shared cluster container to a private cluster container with the EVMS GUI:

1. Select Actions->Modify->Container to see a list of containers.

2. Select the container Shar1 and press Next.

   A Modify Properties dialog opens.

3. Change "Type" to "private" and the "Node" field to node1. Click Modify.

   A window opens that displays the outcome.

4. Commit the changes.

14.5.2. Using Ncurses

Follow these steps to convert a shared cluster container to a private cluster container with the Ncurses interface:

1. Select Actions->Modify->Container

2. The Modify Container Properties dialog opens. Select the container Shar1 by pressing spacebar. The container you selected is marked with an "x."

   Press Enter.

3. The Modify Container Properties - Configuration Options" dialog opens. Scroll down with the down arrow and press spacebar on the "Type" field.

4. Press spacebar.

5. The Change Option Value dialog opens. Select private and press Enter.

6. The Modify Container Properties - Configuration Options dialog opens. Scroll down the list to NodeId with the down arrow and press spacebar.

7. The Change Option Value dialog opens. Select node1 and press Enter.

8. The changed values now display in the Modify Container Properties - Configuration Options dialog. Press Enter.

   The outcome of the command is displayed at the bottom of the screen.

9. Save the changes by clicking Save in the Actions pulldown.

14.5.3. Using the CLI

The modify command modifies the properties of a container. The first argument of the command is the object to modify, followed by its new properties. The command to convert the shared container to a private container in the example is:

modify: Shar1,type=private,node=node1

14.6.1. Using the EVMS GUI

To deport a container with the EVMS GUI, follow these steps:

1. Select Actions->Modify->Container.

2. Select the container c1 and press Next.

   A Modify Properties dialog opens.

3. Change "Type" to "deported." Click Modify.

   A window opens that displays the outcome.

4. Commit the changes.

14.6.2. Using Ncurses

To deport a container with Ncurses, follow these steps:

1. Scroll down the list with the down arrow to Modify. Press Enter.

   A submenu is displayed.

2. Scroll down until Container is highlighted. Press Enter.

   The Modify Container Properties dialog opens.

3. Select the container csm/c1 by pressing spacebar. The container you selected is marked with an "x."

4. Press Enter.

   The Modify Container Properties - Configuration Options dialog opens.

5. Scroll down and press spacebar on the "Type" field.

6. Press spacebar.

   The Change Option Value dialog opens.

7. Type deported and press Enter.

   The changed value is displayed in the Modify Container Properties - Configuration Options dialog.

8. Press Enter.

   The outcome of the command is displayed at the bottom of the screen.

9. Commit the changes by clicking Save in the Actions pulldown.

14.6.3. Using the CLI

To deport a container from the CLI, execute the following command at the CLI prompt:

modify: c1,type=deported

14.9.1. Using the EVMS GUI

To designate node2 as the node to administer from the GUI, follow these steps:

1. Select Settings->Node Administered...

2. Select node2.

3. Click Administer to switch to the new node.

The GUI gathers information about the objects, containers, and volumes on the other node. The status bar displays the message "Now administering node node2," which indicates that the GUI is switched over to node node2.

14.9.2. Using Ncurses

To designate node2 as the node to administer from Ncurses, follow these steps:

1. Go to the Settings pulldown menu.

2. Scroll down with the down arrow to the "Node Administered" option and press Enter.

3. The Administer Remote Node dialog opens. Select node2 and press spacebar.

   The node you selected is marked with an "x."

4. Press Enter.

5. After a while, you will be switched over to the node node2.

14.9.3. Using the CLI

To designate node2 as a node administrator from the CLI, issue this command:

evms -n node2

15.2.1. Using the EVMS GUI

Follow these steps to convert a compatibility volume with the EVMS GUI:

1. Choose Action->Convert ->Compatibility Volume to EVMS.

2. Select /dev/evms/hda3 from the list of available volumes.

3. Type my_vol in the name field.

4. 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:

1. From the Volumes tab, right click on /dev/evms/hda3.

2. Click Convert to EVMS Volume...

3. Continue to convert the volume beginning with step 3 of the GUI instructions.

15.2.2. Using Ncurses

Follow these instructions to convert a compatibility volume to an EVMS volume with the Ncurses interface:

1. Choose Actions->Convert->Compatibility Volume to EVMS Volume

2. Select /dev/evms/hda3 from the list of available volumes.

3. Type my_vol when prompted for the name. Press Enter.

4. Activate Convert.

Alternatively, you can perform some of the steps to convert the volume from the context sensitive menu:

1. From the Volumes view, press Enter on /dev/evms/hda3.

2. Activate the Convert to EVMS Volume menu item.

3. Continue to convert the volume beginning with step 3 of the Ncurses instructions.

15.2.3. Using the CLI

To convert a volume, use the Convert command. The Convert command takes the name of a volume as its first argument, and then name= for what you want to name the new volume as the second argument. To complete the example and convert a volume, type the following command at the EVMS: prompt:

convert: /dev/evms/hda3, Name=my_vol

15.3.1. Using the EVMS GUI

Follow these instructions to convert an EVMS volume to a compatibility volume with the EVMS GUI:

1. Choose Action->Convert ->EVMS Volume to Compatibility Volume.

2. Select /dev/evms/my_vol from the list of available volumes.

3. 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:

1. From the Volumes tab, right click /dev/evms/my_vol.

2. Click Convert to Compatibility Volume...

3. Continue converting the volume beginning with step 3 of the GUI instructions.

15.3.2. Using Ncurses

Follow these instructions to convert an EVMS volume to a compatibility volume with the Ncurses interface:

1. Choose Actions->Convert->EVMS Volume to Compatibility Volume

2. Select /dev/evms/my_vol from the list of available volumes.

3. Activate Convert.

Alternatively, you can perform some of the steps to convert the volume through the context sensitive menu:

1. From the Volumes view, press Enter on /dev/evms/my_vol.

2. Activate the Convert to Compatibility Volume menu item.

3. Continue to convert the volume beginning with step 3 of the Ncurses instructions.

15.3.3. Using the CLI

To convert a volume use the Convert command. The Convert command takes the name of a volume as its first argument, and the keyword compatibility to indicate a change to a compatibility volume as the second argument. To complete the example and convert a volume, type the following command at the EVMS: prompt:

convert: /dev/evms/my_vol, compatibility

16.2.1. Using the EVMS GUI

Follow these steps to shrink the volume with the EVMS GUI:

1. Select Actions->Shrink->Volume...

2. Select /dev/evms/lvm/Sample Container/Sample Region from the list of volumes.

3. Click Next.

4. Select /lvm/Sample Container/Sample Region from the list of volumes.

5. Click Next.

6. Enter 500MB in the "Shrink by Size" field.

7. Click Shrink.

Alternatively, you can perform some of the steps to shrink the volume with the GUI context sensitive menu:

1. From the Volumes tab, right click /dev/evms/lvm/Sample Container/Sample Region

2. Click Shrink...

3. Continue the operation beginning with step 3 of the GUI instructions.

16.2.2. Using Ncurses

Follow these steps to shrink a volume with Ncurses:

1. Select Actions->Shrink->Volume.

2. Select /dev/evms/lvm/Sample Container/Sample Region from the list of volumes.

3. Activate Next.

4. Select lvm/Sample Container/Sample Region from the shrink point selection list.

5. Activate Next.

6. Scroll down using the down arrow until Shrink by Size is highlighted.

7. Press spacebar.

8. Press Enter.

9. At the "::" prompt enter 500MB.

10. Press Enter.

11. Activate Shrink.

Alternatively, you can perform some of the steps to shrink the volume with the context sensitive menu:

1. From the Volumes view, press Enter on /dev/evms/lvm/Sample Container/Sample Region.

2. Activate the Shrink menu item.

3. Continue the operation beginning with step 3 of the Ncurses instructions.

16.2.3. Using the CLI

The shrink command takes a shrink point followed by an optional name value pair or an optional shrink object. To find the shrink point, use the query command with the shrink points filter on the object or volume you plan to shrink. For example:

query: shrink points, "/dev/evms/lvm/Sample Container/Sample Region"

Use a list options filter on the object of the shrink point to determine the name-value pair to use, as follows:

query: objects, object="lvm/Sample Container/Sample Region", list options

With the option information that is returned, you can construct the command, as follows:

shrink: "lvm/Sample Container/Sample Region", remove_size=500MB

16.3.1. Using the EVMS GUI

Follow these steps to expand the volume with the EVMS GUI:

1. Select Actions->Expand->Volume...

2. Select /dev/evms/lvm/Sample Container/Sample Region from the list of volumes.

3. Click Next.

4. Select lvm/Sample Container/Sample Region from the list as the expand point.

5. Click Next.

6. Enter 500MB in the "Additional Size" field.

7. Click Expand.

Alternatively, you can perform some of the steps to expand the volume with the GUI context sensitive menu:

1. From the Volumes tab, right click /dev/evms/lvm/Sample Container/Sample Region.

2. Click Expand...

3. Continue the operation to expand the volume beginning with step 3 of the GUI instructions.

16.3.2. Using Ncurses

Follow these steps to expand a volume with Ncurses:

1. Select Actions->Expand->Volume.

2. Select /dev/evms/lvm/Sample Container/Sample Region from the list of volumes.

3. Activate Next.

4. Select lvm/Sample Container/Sample Region from the list of expand points.

5. Activate Next.

6. Press spacebar on the Additional Size field.

7. At the "::" prompt enter 500MB.

8. Press Enter.

9. Activate Expand.

Alternatively, you can perform some of the steps to shrink the volume with the context sensitive menu:

1. From the Volumes view, press Enter on /dev/evms/lvm/Sample Container/Sample Region.

2. Activate the Expand menu item.

3. Continue the operation beginning with step 3 of the Ncurses instructions.

16.3.3. Using the CLI

The expand command takes an expand point followed by an optional name value pair and an expandable object. To find the expand point, use the query command with the Expand Points filter on the object or volume you plan to expand. For example:

query: expand points, "/dev/evms/lvm/Sample Container/Sample Region"

Use a list options filter on the object of the expand point to determine the name-value pair to use, as follows:

query: objects, object="lvm/Sample Container/Sample Region", list options

The free space in your container is the container name plus /Freespace.

With the option information that is returned, you can construct the command, as follows:

expand: "lvm/Sample Container/Sample Region", add_size=500MB, 
"lvm/Sample Container/Freespace"

17.2.1. Using the EVMS GUI

Follow these steps to add a drive link to the volume with the EVMS GUI:

1. Select Actions->Add->Feature to Volume.

2. Select /dev/evms/vol

3. Click Next.

4. Select Drive Linking Feature.

5. Click Next.

6. Type DL in the Name Field.

7. Click Add.

Alternatively, you can perform some of the steps to add a drive link with the GUI context sensitive menu:

1. From the Volumes tab, right click /dev/evms/vol.

2. Click Add feature...

3. Continue adding the drive link beginning with step 3 of the GUI instructions.

17.2.2. Using Ncurses

Follow these steps to add a drive link to a volume with Ncurses:

1. Select Actions->Add->Feature to Volume.

2. Select /dev/evms/vol.

3. Activate Next.

4. Select Drive Linking Feature.

5. Activate Next.

6. Press Spacebar to edit the Name field.

7. At the "::" prompt enter DL.

8. Press Enter.

9. Activate Add.

Alternatively, you can perform some of the steps to add a drive link with the context sensitive menu:

1. From the Volumes view, press Enter on /dev/evms/vol.

2. Activate the Add feature menu item.

3. Continue adding the drive link beginning with step 3 of the Ncurses instructions.

17.2.3. Using the CLI

Use the add feature to add a feature to an existing volume. Specify the command name followed by a colon, followed by any options and the volume to operate on. To determine the options for a given feature, use the following query:

query: plugins, plugin=DriveLink, list options

The option names and descriptions are listed to help you construct your command. For our example, the command would look like the following:

add feature: DriveLink={ Name="DL }, /dev/evms/vol

18.2.1. Activation

You can activate inactive volumes and objects using the various EVMS user interfaces.

	Note
	EVMS does not currently update the EVMS configuration file (/etc/evms.conf) when volumes and objects are activated. If you activate a volume or object that is not initially activated and do not make the corresponding change in /etc/evms.conf, the volume or object will not be activated the next time the system is booted and you run evms_activate or one of the user interfaces.

Activate:name

18.2.2. Deactivation

You can deactivate active volumes and objects using the various EVMS user interfaces.

	Note
	EVMS does not currently update the EVMS configuration file (/etc/evms.conf) when a volume or object is deactivated. If you deactivate a volume or object that is initially activated and do not make the corresponding change in /etc/evms.conf, then the volume or object will be activated the next time you run evms_activate or one of the user interfaces.

Deactivate:name

18.2.3. Activation and deactivation dependencies

In order for a volume or object to be active, all of its children must be active. When you activate a volume or object, EVMS will activate all the objects that the volume or object comprises.

Similarly, in order for an object to be inactive, all of its parents cannot be activate. When you deactivate an object, EVMS will deactivate all of the objects and volumes that are built from that object.

activate {
	include = [*]
	exclude = [hda*]
}

19.1.1. Using the EVMS GUI

Follow these steps to mount a volume with the EVMS GUI:

1. Select Actions->File System->Mount.

2. Select the volume you want to mount.

3. In the Mount Point box, enter the directory on which you want to mount the volume.

4. Click Options if you want to enter additional options for the mount.

5. Click Mount.

Alternatively, you can mount a volume from the EVMS GUI context sensitive menu:

1. Right click the volume you want to mount.

2. Click Mount...

3. In the Mount Point box, enter the directory on which you want to mount the volume.

4. Click Options if you want to enter additional options for the mount.

5. Click Mount.

19.1.2. Using Ncurses

Follow these steps to mount a volume with Ncurses:

1. Select Actions->File System->Mount....

2. Select the volume you want to mount.

3. At the Mount Point prompt, enter the directory on which you want to mount the volume and press Enter.

4. Select Mount Options if you want to enter additional options for the mount.

5. Select Mount.

Alternatively, you can mount a volume with the Ncurses context-sensitive menu:

1. Highlight the volume you want to mount and press Enter.

2. Select Mount File System.

3. At the Mount Point prompt, enter the directory on which you want to mount the volume and press Enter.

4. Select Mount Options if you want to enter additional options for the mount.

5. Select Mount.

19.1.3. Using the CLI

To mount a volume with the CLI, use the following command:

mount:<volume>, <mount point>, [ <mount options> ]

<volume> is the name of the volume to be mounted.

<mount point> is the name of the directory on which to mount the volume.

<mount options> is a string of options to be passed to the <command>mount</command> command.

19.2.1. Using the EVMS GUI

Follow these steps to unmount a volume with the EVMS GUI:

1. Select Actions->File System->Unmount.

2. Select the volume you want to unmount.

3. Click Unmount.

Alternatively, you can unmount a volume from the EVMS GUI context sensitive menu:

1. Right click the volume you want to unmount.

2. Click Unmount...

3. Click Unmount.

19.2.2. Using Ncurses

Follow these steps to unmount a volume with Ncurses:

1. Select Actions->File System->Unmount....

2. Select the volume you want to unmount.

3. Select Unmount.

Alternatively, you can unmount a volume with the Ncurses context-sensitive menu:

1. Highlight the volume you want to unmount and press Enter.

2. Select Unmount File System.....

3. Select Unmount.

19.2.3. Using the CLI

To unmount a volume with the CLI, use the following command:

unmount:<volume>

<volume> is the name of the volume to be unmounted.

19.3.1. Turning swap on

This section tells how to turn swap on using the various EVMS user interfaces.

Task: swapon, <volume>[, priority=low | , priority=high [level=0..32767]]

19.3.2. Turning swap off

This section tells how to turn swap off using the various EVMS user interfaces.

Task: swapoff, <volume>

20.2.1. Using the EVMS GUI

Follow these steps to add sde to /dev/evms/md/md0 with the EVMS GUI:

1. Select Other->Storage Object Tasks...

2. Select md/md0.

3. Click Next.

4. Select Add spare object.

5. Click Next.

6. Select sde.

7. Click Add.

8. The operation is completed when you save.

Alternatively, you could use context-sensitive menus to complete the task, as follows:

1. View the region md/md0. You can view the region either by clicking on the small plus sign beside the volume name (/dev/evms/md/md0) on the volumes tab, or by selecting the regions tab.

2. Right click the region (md/md0). A list of acceptable Actions and Navigational shortcuts displays. The last items on the list are the tasks that are acceptable at this time.

3. Point to Add spare object and left click.

4. Select sde.

5. Click Add.

20.2.2. Using Ncurses

Follow these steps to add sde to /dev/evms/md/md0 with Ncurses:

1. Select Other->Storage Object Tasks

2. Select md/md0.

3. Activate Next.

4. Select Add spare object.

5. Activate Next.

6. Select sde.

7. Activate Add.

Alternatively, you can use the context sensitive menu to complete the task:

1. From the Regions view, press Enter on md/md0.

2. Activate the Add spare object menu item.

3. Select sde.

4. Activate Add.

20.2.3. Using the CLI

With the EVMS CLI, all plug-in tasks must be accomplished with the task command. Follow these steps to add sde to /dev/evms/md/md0 with the CLI:

1. The following query command with the list options filter to determines the acceptable tasks for a particular object and the name-value pairs it supports. The command returns information about which plug-in tasks are available at the current time and provides the information necessary for you to complete the command.

   query: objects, object=md/md0, list options

2. The command takes the name of the task (returned from the previous query), the object to operate on (in this case, md/md0), any required options (none in this case) and, if necessary, another object to be manipulated (in our example, sde, which is the spare disk we want to add):

   task: addspare, md/md0, sde

   The command is completed upon saving.

21.2.1. Using the EVMS GUI

Follow these steps to delete the volume and the container with the EVMS GUI:

1. Select Actions->Delete->Volume.

2. Select volume /dev/evms/Sample Volume from the list.

3. Click Recursive Delete. This step deletes the volume and the region lvm/Sample Container/Sample Region. If you want to keep the underlying pieces or want to delete each piece separately, you would click Delete instead of Delete Recursive.

4. Assuming you chose Delete Recursive (if not, delete the region before continuing with these steps), select Actions->Delete->Container.

5. Select container lvm/Sample Container from the list.

6. Click Recursive Delete to destroy the container and anything under it. Alternatively, click Delete to destroy only the container (if you built the container on disks as in the example, either command has the same effect).

Alternatively, you can perform some of the volume deletion steps with the GUI context sensitive menu:

1. From the Volumes tab, right click /dev/evms/Sample Volume.

2. Click Delete...

3. Continue with the operation beginning with step 3 of the GUI instructions.

21.2.2. Using Ncurses

Follow these steps to delete the volume and the container with Ncurses:

1. Select Actions->Delete->Volume.

2. Select volume /dev/evms/Sample Volume from the list.

3. Activate Delete Volume Recursively. This step deletes the volume and the region lvm/Sample Container/Sample Region. If you want to keep the underlying pieces or want to delete each piece separately, activate Delete instead of Delete Recursive.

4. Assuming you chose Delete Volume Recursively (if not, delete the region before continuing with these steps), select Actions->Delete->Container.

5. Select container lvm/Sample Container from the list.

6. Click Recursive Delete to destroy the container and everything under it. Alternatively, activate Delete to delete only the container (if you built the container on disks as in the example, either command has the same effect).

7. Press Enter.

Alternatively, you can perform some of the volume deletion steps with the context sensitive menu:

1. From the Volumes view, press Enter on /dev/evms/Sample Volume.

2. Activate Delete.

3. Continue with the operation beginning with step 3 of the Ncurses instructions.

21.2.3. Using the CLI

Use the delete and delete recursive commands to destroy EVMS objects. Specify the command name followed by a colon, and then specify the volume, object, or container name. For example:

1. Enter this command to perform the delete recursive operation:

   delete recursive: "/dev/evms/Sample Volume"

   This step deletes the volume and the region /lvm/Sample Container/Sample Region. If you wanted to keep the underlying pieces or wanted to delete each piece separately, use the delete command, as follows:

   delete: "/dev/evms/Sample Volume"

2. Assuming you chose Delete Volume Recursively (if not, delete the region before continuing with these steps) enter the following to destroy the container and everything under it:

   delete recursive: "lvm/Sample Container"

   To destroy only the container, enter the following:

   delete: "lvm/Sample Container"

22.2.1. Using the EVMS GUI or Ncurses

Follow these steps to replace sdb1 with sdc1:

1. Select Actions->Replace.

2. In the "Replace Source Object" panel select sdb1.

3. Activate Next.

4. In the "Select Replace Target Object" panel, select sdc1.

5. Activate Replace.

Alternatively, you can perform these same steps with the context sensitive menus:

1. From the "Disk Segments" panel, right click (or Press Enter on) the object sdb1.

2. Choose Replace on the popup menu.

3. In the "Select Replace Target Object" panel, select sdc1.

4. Activate Replace.

When you save changes, EVMS begins to copy the data from sdb1 to sdc1. The status bar at the bottom of the UI will reflect the percent-complete of the copy operation. The UI must remain open until the copy is finished. At that time, the object sdb1 will be moved to the "Available Objects" panel.

22.2.2. Using the CLI

Use the Replace to replace objects with the CLI:

Replace:source_object_name, target_object_name

"source_object_name" is the name of the object you wish to replace with "target_object_name." In the following example, sdb1 is replaced with sdc1.

Replace:sdb1,sdc1

23.4.1. Using the EVMS GUI context sensitive menu

To move the DOS segment through the GUI context sensitive menu, follow these steps:

1. From the Segments tab, right click sda1.

2. Click Move.

3. Select sda_freespace1.

4. Click Move.

23.4.2. Using Ncurses

To move the DOS segment, follow these steps:

1. Use Tab to select the Disk Segments view.

2. Scroll down with the down arrow and select sda1.

3. Press Enter.

4. Scroll down with the down arrow and select Move by pressing Enter.

5. Use the spacebar to select sda_freespace1.

6. Use Tab to select Move and press Enter.

23.4.3. Using the CLI

Use the task command to move a DOS segment with the CLI.

task:Move,sda1,sda_freespace1