Ignite-UX Custom Configuration files

A volu

me group definition must have the following:

 volume group attributes

 one or more physical_volume definitions (including "group"

definitions that also include

more physical volume definitions)

 one or more (usually more) logical_volume definitions.

volume_group _hp_group_name

{

The physical_volume definition places the first disks (whose number is determined by

_hp_root_grp_disks) returned by the disk[] construct into the root volume group

. When

Ignite-UX encounters the first volume group that uses *=<index>, it attempts to return the preset

root disk as the first disk. This causes things to look as though the disk in _hp_root_disk

(initialized from _hp_primary_path) was always placed into the list of physical volumes put into

the root volume group and disk group.

physical_volume disk[*=_hp_root_grp_disks]

Next is a test to choose the volume manager. Currently the only choice that enables VxVM is

"VERITAS Volume Manager (VxVM) with VxFS". All of the other choices use LVM.

(_hp_disk_layout == "VERITAS Volume Manager (VxVM) with VxFS") {

usage = VxVM

} else {

usage = LVM

}

All the volume group attributes, such as max_physical_extents, are optional and only affect

LVM volume groups. If you do not assign them to a value, they take on the defaults of the

vgcreate command.

# In order to accommodate adding 9GB disks now or in the

# future, set the default max_physical_extents large

# enough to handle it (based on 4Mb extent size).

# Note that this will be increased by IUX automatically

# for disks larger than 9GB.

max_physical_extents = 2500

Very large disks are the most common disks on new systems, with ≥140GB disks becoming normal,

36/72GB disks less common, and 18GB or smaller disks rare. The following tests adjust the

physical extent size for the LVM volume group being defined, and ensures the complete disk can be

used with the disks. It is only based upon the size of the root disk, not the size of every disk that

might be included. This might influence the amount of usable space in the volume group.

Additionally, Ignite-UX examines all the disks being used and selects the LVM parameters that work

for that entire disk group. The setting of physical extent size here is just a first approximation;

Ignite-UX can change these values at a later stage.

Defining physical volume groups is discussed later when discussing custom configuration.

This is evaluated once. After that, changes made via the Ignite-UX GUI affect which physical volumes is used in the root

volume group.