Cluster Enabling Traditional Linux Volumes On Shared Disks - Novell OPEN ENTERPRISE SERVER CLUSTER SERVICES 1.8.2 - ADMINISTRATION Manual

Moving a Volume to a Larger Disk
1 Unmount the file system for the volume you want to move.
2 Add a larger disk to the CSM container.
3 Restart evmsgui, click the Containers tab, then expand the container so that the objects under
4 Right-click the object for the disk where the volume resides and select Replace.
5 Select the object for the disk where the volume will be moved, then click Next.
6 Save your changes.
7 Click Save, exit evmsgui, then restart evmsgui.
8 Click the Volumes tab, right-click the volume, then select Check/Repair filesystem.
9 Click the Disks tab, right-click the disk the volume was moved from, then select Remove from
10 Click Save and exit evmsgui.
3.7.6 Cluster Enabling Traditional Linux Volumes on Shared
Disks
Cluster enabling a traditional Linux volume allows it to be moved or mounted on different servers in
the cluster. This provides a way for clients to reconnect to the volume regardless of which server is
hosting it.
EVMS containers are the unit of failover for traditional Linux volumes. Because the EVMS
container is the unit of failover, all volumes in a container will also fail over, but only the volumes
that are mounted through the cluster resource load script will be mounted. Any volumes in the
container that are not mounted through the resource load script will have to be mounted manually.
The following sections contain information on cluster enabling a traditional Linux volume on a
shared disk partition:
36 OES Novell Cluster Services 1.8.2 Administration Guide for Linux
2a In evmsgui, click Actions, select Create, then click Container.
2b Select the Cluster Segment Manager, then click Next.
2c Select the larger disk you want to move the volume to.
The entire disk is used for the expansion, so you must select a disk that does not have
other volumes on it.
2d Provide the same settings information (name, type, etc.) as the existing container for the
volume, then save your changes.
2e Click Save and exit evmsgui.
the container appear.
The new disk should appear as part of the container.
Saving your changes could take a while, depending on volume size and other factors.
This will run the repair process and ensure no problems exist on the moved volume.
container.
"Creating a Traditional Linux Volume Cluster Resource" on page 37
"Configuring Traditonal Linux Volume Load Scripts" on page 37
"Configuring Traditional Linux Volume Unload Scripts" on page 39