Chapter 4. Managing EVMS Devices / 4.2. Initializing Disks | ||||
|---|---|---|---|---|
 | Chapter 4. Managing EVMS Devices | 4.3. Removing the Segment Manager from a Device |  | |
Chapter 4. Managing EVMS Devices / 4.2. Initializing Disks | ||||
|---|---|---|---|---|
| Chapter 4. Managing EVMS Devices | 4.3. Removing the Segment Manager from a Device | | |
You must initialize new disks and disks that you want to reformat. After the disk is initialized, you can subdivide, or carve, the device into one or more disk segments for your file systems.
If you use large disks or disk arrays, use the vendor’s tools to carve them into the sizes that are usable for the management tools you plan to use. For example, the md driver recognizes disks only up to 2 TB in size, so the limit also applies to the md plug-in for EVMS. Software RAID devices you create with EVMS can be larger than 2 TB, of course, because the md driver plug-in manages the disks underneath that storage structure.
When you boot the server, EVMS scans and recognizes all devices it manages. If you add a new device to the server or create a device using mkfs, EVMS automatically mounts it on reboot under /dev/evms as a compatibility volume, such as /dev/evms/sdb.
![[Important]](admon/important.png) | Important |
|---|---|
If you cannot find a new disk, device, or volume, look under | |
Consider the following guidelines when initializing a disk:
EVMS might allow you to create segments without first adding a segment manager for the disk, but it is best to explicitly add a segment manager to avoid problems later.
| Important |
|---|---|
You must add a Cluster segment manager if you plan to use the devices for volumes that you want to share as cluster resources. | |
When you initialize an existing disk that is already formatted, the process of adding a segment manager destroys all data on the disk. If you want to keep the data on the disk, make sure to back up the data before you begin this process.
For existing disks on the system or disks that you move from another system, you must delete any existing volume management structures, and remove any segment managers. This removes the device’s metadata and data, and destroys all data on the disk.
![[Warning]](admon/warning.png) | Warning |
|---|---|
Do not initialize the device that contains your current system disk or any device that contains the | |
If a new disk does not show up in the list of , look for it in the list to see if the disk shows up as a compatibility volume. For example, a new disk sdb would show up as /dev/evms/sdb. Delete it from the Volumes list to force the disk to show up in , then create segments as desired.
Use the following procedure to assign a segment manager to device for servers using x86, x64, and IA64 controllers. This option is not available for S390 platforms, so simply continue with configuring software RAIDs or file system partitions, as desired.
| Warning |
|---|---|
Adding a segment manager initializes the disk, completely removing all the segments it contains. All the data stored on the device is lost. | |
If the disk has any existing volume management structures or an existing segment manager, remove them.
Select ++ to view the Volumes list.
Select any existing volume management structures on the device, then click .
Select ++.
Select the type of Segment Manager in use, then click .
Select the device, then click Remove.
If the disk is a new one that is listed as a compatibility volume in the Volumes list, delete it as a compatibility volume.
Select ++ to view the Volumes list.
Select the device, then click .
Add the Segment Manager.
In the list of , select the device, then click ++.
From the list, select one of the following types of segment manager, then click .
(the most common choice)
(for IA-64 platforms)
(available only if it is a viable option for the selected disk)
Select the device from the list of , then click .
If required, specify the disk type as Linux.
Click to create the segment management container for the disk, then click to dismiss the confirmation message.
