 | ||
| Boot-time volume restrictions | ||
|---|---|---|
| Prev | Rootability | Next |
When the operating system is booted, the root file system and swap area must be available for use before the vxconfigd daemon can load the VxVM configuration or start any volumes. During system startup, the operating system must see the rootvol and swapvol volumes as regular partitions so that it can access them as ordinary disk partitions.
Due to this restriction, each of the rootvol and swapvol plexes must be created from contiguous space on a disk that is mapped to a single partition. It is not possible to stripe, concatenate or span the plex of a rootvol or swapvol volume that is used for booting. Any mirrors of these plexes that are potentially bootable also cannot be striped, concatenated or spanned.
Volumes on the root disk have the following restrictions on their configuration:
For the x64 platform, root encapsulation is supported for Update 1 and later releases of the Solaris 10 OS that include the GRUB boot loader.
The root volume (rootvol) must exist in the disk group that is chosen to be the boot disk group, bootdg. Although other volumes named rootvol can be created in other disk groups, only the rootvol in bootdg can be used to boot the system.
If the volumes that are required to boot the system span multiple disks, all these disks must be in the boot disk group.
The rootvol and swapvol volumes always have minor device numbers 0 and 1 respectively. Other volumes on the root disk do not have specific minor device numbers.
Restricted mirrors of volumes on the root disk have overlay partitions created for them. An overlay partition is one that exactly includes the disk space occupied by the restricted mirror. During boot, before the rootvol, varvol, usrvol and swapvol volumes are fully configured, the default volume configuration uses the overlay partition to access the data on the disk.
Although it is possible to add a striped mirror to a rootvol device for performance reasons, you cannot stripe the primary plex or any mirrors of rootvol that may be needed for system recovery or booting purposes if the primary plex fails.
rootvol and swapvol cannot be spanned or contain a primary plex with multiple noncontiguous subdisks. You cannot grow or shrink any volume associated with an encapsulated boot disk (rootvol, usrvol, varvol, optvol, swapvol, and so on) because these map to a physical underlying partition on the disk and must be contiguous. A workaround is to unencapsulate the boot disk, repartition the boot disk as desired (growing or shrinking partitions as needed), and then re-encapsulating.
When mirroring parts of the boot disk, the disk being mirrored to must be large enough to hold the data on the original plex, or mirroring may not work.
The volumes on the root disk cannot use dirty region logging (DRL).
In addition to these requirements, it is a good idea to have at least one contiguous, (cylinder-aligned if appropriate) mirror for each of the volumes for root, usr, var, opt and swap. This makes it easier to convert these from volumes back to regular disk partitions (during an operating system upgrade, for example).