This section describes how to configure EVMS as the volume manager of your devices.
This section describes how to configure the system device during the Linux install to use EVMS as the volume manager instead of the current default of Linux Volume Manager (LVM).
For the purposes of this install documentation, a system device is any device that contains the Linux /boot, swap, or root (/) partitions for your Linux computer.
The install instructions assume the following:
All three system partitions are on the same physical disk.
If you use different disks for any of the system partitions, make sure to modify the install instructions for your deployment scenario so that all of the system partitions are managed by EVMS.
You must configure the boot partition within the BIOS-addressable space (such as 2 GB for x86 or 8 GB for x86-64) of the first disk recognized by the system.
If this restriction is not required for your hardware, you can modify the location of the /boot partition as desired.
Your system uses the Grub or LILO boot loaders.
If you have an IA64 system, you must modify these install instructions to use the ELILO boot loader (/boot/efi/elilo.conf) instead.
![]() | Warning |
|---|---|
Whenever you manually alter the kernel or | |
Version 2.3 and later of mdadm supports component devices up to 4 TB in size each. Earlier versions support component devices up to 2 TB in size.
![]() | Important |
|---|---|
If you have a local disk, external disk arrays, or SAN devices that are larger than the supported device size, use a third-party disk partitioner to carve the devices into smaller logical devices. | |
You can combine up to 28 component devices to create the RAID array. The md RAID device you create can be up to the maximum device size supported by the file system you plan to use. For information about file system limits for SUSE® Linux Enterprise Server 10, see “Large File System Support” in the SUSE Linux Enterprise Server 10 Installation and Administration Guide..
This install requires that you delete the default partitioning settings created by the install, and create new partitions to use EVMS instead. This destroys all data on the disk.
![]() | Warning |
|---|---|
To avoid data loss, it is best to use the EVMS install option only on a new device. | |
If you have data volumes on the system device, take one or more of the following precautionary measures:
Move the data volumes from the system device to another device.
If you cannot move the volumes, make a backup copy of the data, so you can restore the data volumes later from a backup copy.
By default, the YaST install for SUSE Linux Enterprise Server uses the Linux Volume Manager to manage the system device. The install procedures in this section describe how to install SUSE Linux Enterprise Server with EVMS as the volume manager of the system device. The instructions assume the following:
You want to use EVMS to manage the system device.
Only the system device is to be configured during the install.
Other devices on the system are not configured during the install, or are attached to the server later. These additional devices are configured only after the system is operating and performing as expected.
To install Linux with EVMS as the volume manager for your boot and system partitions, you must modify the Partitioning configuration in the Installation Settings.
![]() | Warning |
|---|---|
The following procedure destroys all data on the system device. | |
Begin the install, according to the instructions provided in Deployment in the SUSE Linux Enterprise 10 Installation and Administration Guide.
When the installation reaches the Installations Settings screen, delete the proposed LVM-based partioning solution. This deletes the proposed partitions and the partition table on the system device so that the device can be marked to use EVMS as the volume manager instead of LVM.
In the list of Installation Settings, select .
In the Partitioning menu, select , then click .
Select , then click to open the dialog box.
Select > , then click twice to continue through the Warning advisories.
This deletes the recommended partitions and the partition table on the system disk.
Create a primary partition on the system disk to use as the boot partition:
Click .
From the list of devices, select the device you want to use for the boot partition, such as /dev/hda, then click .
If you have a single system disk, only one device is available, and you are not prompted to choose the device.
Select , then click .
Select , then select the native Linux file system you want to use, such as Ext3.
![]() | Important |
|---|---|
In a paravirtualized environment, use Ext2 as the file system for the boot device. | |
In field, specify 200 MB or larger.
For example, to set the size at 300 MB, type 300M.
Set the mount point to .
Click .
The partition appears as a logical device in the devices list, such as /dev/hda1.
Create a second primary partition on the system disk to use for both the swap and system volumes:
Click .
From the list of devices, select the device you want to use for the second primary partition, such as /dev/hda, then click .
If you have a single system disk, only one device is available and you are not prompted to choose the device.
Select , then click .
Select , then select from the list of file system IDs.
In ( field), set the cylinder End value to 5 GB or larger, depending on the combined partition size you need to contain your system and swap volumes.
![]() | Important |
|---|---|
Do not make the system partition larger than necessary. The remaining space on the system disk can be used to create NSS volumes or native Linux volumes that are managed by EVMS. | |
To determing how much space to use, consider the following recommendations:
For your system volume, allow 2 GB (minimum) to 10 GB (recommended), depending on the OES services that you intend to install.
If you intend to create additional NSS volumes on the same physical disk, you must leave unpartitioned space available.
Set aside 128 MB or larger for the swap volume.
Swap management is different for Linux kernel 2.4.10 and later. How much swap to add depends on the RAM size, the tasks that are planned for the system, and whether you want to make more virtual memory available than the RAM provides.
Some swap (at least 128 MB) is good to have to minimize the risk of losing data when active processes run out of RAM space. Swap is not required for systems with more than 1 GB of RAM. You must have at least 1 GB of virtual memory (RAM plus swap) during the install, but if the swap is more than 2 GB, you might not be able to install on some machines.
The total size should be the size you need for your system volume plus the size you need for your swap volume.
For example, if you have a 20 GB hard drive with 2 GB of RAM and plan to install all of the OES services on the system volume, your system partition should be at least 11 GB. The remaining 9 GB should remain as free unpartitioned space that can be used for NSS volumes or other Linux partitions that you might want to create later.
Click .
The partition appears as a logical device in the devices list, such as /dev/hda2.
Modify the volume management type from LVM to EVMS for the second primary partition you created in Step 4:
At the bottom of the page, click .
Available partitions for EVMS appear as devices under /dev/evms, such as /dev/evms/hda2.
In the EVMS Configurator, select the LVM partition created in Step 4, then click .
In the Create EVMS Container dialog box, select the partition, specify the container name (such as system), then click to create the lvm/ container, where system is the container name.system
Click .
The EVMS Configurator displays the lvm/ container you just created, its size, and free space.system
Create the swap volume in the lvm/ container:system
Select lvm/system, then click .
In the Create Logical Volume dialog box, select , then select from the drop-down menu.
Specify swap as the volume name.
Specify 1 GB (recommended) for the swap volume.
The swap size should be 128 MB or larger, with a recommended size of 1 GB. For an explanation of this recommendation, see Step 4.e.
Specify the mount point as .
Click .
Create the system volume in the lvm/ container:system
Select lvm/system, then click .
In the Create Logical Volume dialog box, select , then select the file system to use from the drop-down menu, such as .
In the Volume Name field, specify a volume name, such as sys_lx.
In the field, click Max to set the size of the system volume as the remaining space available in the lvm/ partition. system
Specify the mount point as / (root volume).
Click .
Click to return to the list of devices.
Below is an example of the physical and logical devices that should be configured on your system. Your setup depends on the number of devices in the server and the sizes you choose for your partitions.
Click to return to the Installation Settings page.
You can dismiss the message warning that you should not mix EVMS and non-EVMS partitions on the same device.
Continue with the SUSE Linux Enterprise Server installation.
![]() | Important |
|---|---|
After the install is complete, make sure to perform the mandatory post-install configuration of the related system settings to ensure that the system device functions properly under EVMS. Otherwise, the system fails to boot properly. For information, see Section 2.1.3, “After the Server Install”. | |
After the SUSE Linux Enterprise Server 10 install is complete, you must perform the following tasks to ensure that the system device functions properly under EVMS:
When you boot the system, the kernel reads the /etc/fstab file to identify which file systems should be mounted and then mounts them. This file contains a table of file system information about the root (/), /boot, and swap partitions plus other partitions and file systems you want to mount.
The /boot partition is separate from the EVMS container where you placed the root (/) and swap partitions and is not managed by EVMS at this time. However, in the following steps, you disable boot.lvm and boot.md, then enable boot.evms. In effect, this forces EVMS to scan all the partitions at boot time, including the /boot partition, and it activates /boot under the /dev/evms directory. Therefore, this makes /boot a partition that is discovered by EVMS at startup, and requires that the device be listed under /dev/evms in the fstab file so it can be found when booting with boot.evms. You must edit the /etc/fstab file to modify the location of the /boot partition so it is under the /dev/evms directory.
In fstab, the entry for the boot device might present the boot device by the device node name (such as /dev/sda1) or by the UUID pathname (such as /dev/disk/by-id/scsi-SServeRA_Drive_1_600BC00000-part1). In ether case, that name for the boot device must be changed to include evms in the path, such as /dev/evms/sda1.
The procedure in this section shows how to change /dev/ to sda1/dev/evms/. Replace sda1 with the device name of the device you used for your sda1/boot partition.
![]() | Important |
|---|---|
When working in the | |
To modify the path of the boot device in the /etc/fstab file, complete the following procedure:
Open the /etc/fstab file in a text editor.
Locate the line that contains the /boot partition.
For example, if your /boot partition uses device sda1 and the Reiser file system, look for a line similar to this:
/dev/sda1/bootreiserdefaults 1 1
In the column, modify the location of the /boot partition from /dev to /dev/evms so it can be managed by EVMS. Modify only the device name by adding /evms to the path:
/dev/evms/sda1 /boot reiser defaults 1 1
Save the file.
The changes do not take effect until the server is restarted. Do not restart at this time.
Continue with Section 2.1.3.2, “Make a New initrd”.
Open a terminal console, and log in as the root user.
At the console prompt, enter
mkinitrd
This creates a new initrd file with the correct settings for the boot device. The changes do not take effect until the server is restarted. Do not restart at this time.
Continue with Section 2.1.3.3, “Disable the boot.lvm and boot.md Services”.
Disable the boot.lvm and boot.md services so they do not run at boot time (runlevel B). EVMS now handles the boot.
In YaST, click > ) > .
Select .
Click > .
Select .
Click > .
Click , then click .
The changes do not take effect until the server is restarted. Do not restart at this time.
Continue with Section 2.1.3.4, “Enable the boot.evms Service”.
The boot.evms service should be enabled automatically after the install, but you should verify that it is enabled.
In YaST, click > > .
Select .
Click > .
The option is automatically selected.
Click , then click .
The changes do not take effect until the server is restarted.
![]() | Note |
|---|---|
Effective in SUSE Linux Enterprise 10, the | |
Continue with Section 2.1.3.5, “Restart the Server”.