Overview: The Next Generation Mass Storage Stack (September 2009)

Figure 5: Ignite-UX More Info Screen
During an installation, Ignite-UX configures the root, dump, and swap devices with their agile addressing
representation. This means that after installing, the commands that display the boot, dump, and swap devices
show them using the agile form.
In previous releases, Ignite-UX associated the same DSFs to the same I/O components for any identically
configured systems. This is not true in HP-UX 11i v3, given the parallelism of the I/O system. There is no
guarantee that installing or reinstalling a system will generate the same set of DSFs on the system, although a
recovery retains the original set of DSFs.
Logical Volume Manager
Logical Volume Manager (LVM) supports both the legacy and agile views. In particular, LVM supports the use of
both legacy and persistent DSFs within the same volume group. New options to the vgscan and vgimport
commands, described below, affect how LVM creates LVM configuration information.
By default, vgscan recovers LVM configuration information (the /etc/lvmtab file) using kernel information for
activated volume groups or using legacy DSFs for volume groups that have not been activated since the last boot.
If you specify the new –N option, then vgscan uses persistent DSFs. If you specify the new –B option, then
vgscan populates the /etc/lvmtab file using both legacy and persistent DSFs.
By default, when importing a volume group in shared mode, vgimport populates the /etc/lvmtab file using
legacy DSFs. If you specify the new –N option together with –s, then vgimport uses persistent DSFs.
LVM configuration is stored in /etc/lvmtab in the same way in which it was configured. For example, if a
physical volume is added to a volume group using its legacy DSF, the entry is stored in legacy format. Since
Ignite-UX creates the root disk with agile addressing, after a cold install the lvlnboot command displays the root
32