Ignite-UX Custom Configuration files

} else {
size = 112Mb
}
} else {
size = 300Mb
}
contiguous_allocation = true
bad_block_relocate = false
}
300MB is the default for large disk configurations because additional Dynamically Loadable Kernel
Modules (DLKMs) require more space in /stand.
Now at this stage you might be wondering why you had to make sure that you set up those logical
volumes with certain values for contiguous allocation and bad block relocation. Table 3 contains a
brief summary
of the reasons.
Table 3
Name Contiguous
Allocation
Bad Block
Relocation
33
Reason
/
TRUE FALSE
The root file system must be usable before the volume manager is
active to enable this. It cannot allow the volume manager to relocate
blocks and it must be contiguous on a disk.
Primary
swap
TRUE FALSE
Primary swap is activated before the volume manager is active, so it
requires the same options as the root file system.
Dump
space
TRUE FALSE
A dump is written when no volume manager is active; because of
this, it must be contiguous, and cannot have bad blocks relocated
by the volume manager.
Secondary
swap
N/A N/A
Secondary swap has no requirements unless it is also a dump
space; in which case, it has the dump space requirements.
/stand TRUE FALSE
The /stand volume is read by the boot loader. The boot loader
knows nothing about volume managers and currently only
understands HFS
34
file systems, so the file system must be contiguous
and cannot have bad block relocation enabled.
Note:
On HP-UX B.11.11, it is assumed that all IODC (I/O Dependent Code)
in f
irmware can perform operations with up to 4GB offsets35. For some
I/O c
ontrollers this limits the maximum offset for dump. Newer systems
have block-based I/O implemented in IODC. This allows the offset of
an I/O operation to be given in blocks not bytes. This change
dramatically increases the amount allowed for offset of dump spaces on
most new I/O interfaces. Itanium®-based systems do not have a 4GB
33
This is bad block relocation performed by a volume manager not automatic relocation performed by the disk drives.
34
Itanium®-based systems may have /stand as a VxFS file system. The HFS restriction is applicable only to PA-RISC
systems.
35
Various combinations of 2GB and 4GB offsets (depending on the I/O interface) were allowed in older releases of Ignite-
UX (before B.3.0 and in all of the A.x.x versions).
57