3.9 Creating Traditional Linux File Systems on Shared Disks

To configure shared media for a cluster, you must use EVMS. Using EVMS to create partitions, containers, volumes, and file systems helps prevent data corruption caused by multiple nodes accessing the same data. You can create partitions and volumes using any of the journaled Linux file systems (EXT3, Reiser, etc.).

EVMS virtual volumes are recommended for Novell Cluster Services because they can more easily fail over to different cluster servers and provide greater protection of shared media from unauthorized access. You can enter man evms at the Linux server console to reference the evms man page, which provides additional instructions and examples for evms.

You can also enter man mount at the Linux server console to reference the mount man page, which provides additional instructions and examples for the mount command.

The following sections provide the necessary information for using EVMS to create a traditional Linux volume and file system on a shared disk:

WARNING:EVMS administration utilities (evms, evmsgui, and evmsn) should not be running when they are not being used. EVMS utilities lock the EVMS engine, which prevents other evms-related actions from being performed. This affects both NSS and traditional Linux volume actions.

NSS and traditional Linux volume cluster resources should not be migrated, offlined, or onlined while any of the EVMS administration utilities are running.

3.9.1 Ensuring That the Shared Disk Is not a Compatibility Volume

New EVMS volumes are by default configured as compatibility volumes. If any of the volumes on your shared disk (that you plan to use in your cluster) are compatibility volumes, you must delete them because the volumes are created later

NOTE:The SBD partition should not be changed using this procedure. The SBD partition is fine as a NWSegMgr.

  1. At the Linux server console, enter evmsgui.

  2. Click Yes, if the following prompt appears.

    EVMS GUI Prompt

    When starting, EVMS discovers new disks available to the server and configures them as NWSegMgr.

  3. Click the Volumes tab, then right-click the volume on the shared disk and select Display details.

  4. Click the Page 2 tab and determine from the Status field if the volume is a compatibility volume.

    EVMS Compatibility Volumes

    If the volume is a compatibility volume or has another segment manager on it, continue with Step 4.a below.

    1. Click the Volumes tab, right-click the volume, then select Delete.

    2. Select the volume, then click Recursive Delete.

    3. (Conditional) If a Response Required pop-up appears, click the Write zeros button.

    4. (Conditional) If another pop-up appears, click Continue to write 1024 bytes to the end of the volume.

3.9.2 Removing Other Segment Managers

If any of the shared disks you plan to use with your cluster have segment managers other than CSM, you must delete them as well.

The sbd partition cannot be located on the same virtual disk as your cluster resource. If the segment manager contains the sbd partition, use your shared storage tools to carve out a different partition for your cluster resource.

WARNING:Do not reconfigure or remove a logical disk or segment manager containing the sbd partition.

  1. In evmsgui, click the Disks tab, then right-click the disk you plan to use for a cluster resource.

  2. Select remove segment manager from Object.

    This option only appears if there is another segment manager for the selected disk.

    EVMS GUI Administration Utility, Remove Segment
  3. Select the listed segment manager and click Remove.

3.9.3 Creating a Cluster Segment Manager Container

To use a traditional Linux volume with EVMS as a cluster resource, you must use the Cluster Segment Manager (CSM) plug-in for EVMS to create a CSM container.

You should note the container name used as it is needed when configuring the cluster scripts.

NOTE:CSM containers require Novell Cluster Services (NCS) to be running on all nodes that access the CSM container. Do not make to modifications to EVMS objects unless NCS is running.

  1. In evmsgui, click Actions, select Create, then select Container.

  2. Select Cluster Segment Manager, then click Next.

  3. Select the disks (storage objects) you want to place in the container, then click Next.

  4. On the Configuration Options page, select the node where you are creating the container, specify Private as the type, then choose a name for the container.

    EVMS GUI Administration Utility, Volume Name

    The name must be one word, must consist of standard alphanumeric characters, and must not be any of the following reserved words:

    • Container

    • Disk

    • EVMS

    • Plugin

    • Region

    • Segment

    • Volume

  5. Click Create to save your changes.

  6. Click OK to close the confirmation dialog and return to the EVMS main screen

  7. Click the Save icon.

3.9.4 Make New Container Active

  1. Click on the Container tab.

  2. Right-click the new container you just created and select Modify Properties.

  3. Select your container, and then click Next.

  4. Click Modify.

  5. Click the Save icon to commit the changes.

3.9.5 Creating an EVMS Volume for iPrint Resources (Conditional)

Verify that EVMS has created your volume by looking at the Volumes tab. If the volume does not exist, complete the following:

  1. In evmsgui, click Actions, select Create, and then EVMS Volume.

  2. Select the container you just created (either the CSM container or the additional segment manager container) and specify a volume name.

  3. Click Create, then click Save.

3.9.6 Creating a File System on the EVMS Volume

You should note the volume name used as it is needed when configuring the cluster scripts.

  1. In evmsgui, click the Volumes tab and right-click the volume you just created.

  2. Select Make File System, choose a traditional Linux file system from the list, then click Next.

    iPrint requires a native Linux file system such as reiserfs, ext2/3 or xfs. Do not choose Novell NSS or swap.

    You should note the file system used as it is needed when configuring the cluster scripts.

  3. Specify a volume label, then click Make.

  4. Save your changes by clicking Save.

  5. Exit evmsgui by clicking Quit > Save > OK.

WARNING:Do not mount the file system from EVMSGUI. The file system needs to be mounted by the cluster resource load script. Also, entries should not be found in /etc/fstab file for the operating system to automatically mount this file system.

WARNING:EVMS administration utilities (evms, evmsgui, and evmsn) should not be running when they are not being used. EVMS utilities lock the EVMS engine, which prevents other evms-related actions from being performed. This affects both NSS and traditional Linux volume actions.

NSS and traditional Linux volume cluster resources should not be migrated, offlined, or onlined while any of the EVMS administration utilities are running.