METADATA subdisks are created during root disk encapsulation to protect partitioning information. These subdisks are deleted automatically when a root disk is unencapsulated.
The following example fdisk output shows the original partition table for a system's root disk:
# fdisk -ul /dev/hda Disk /dev/hda: 255 heads, 63 sectors, 2431 cylinders Units = sectors of 1 * 512 bytes Device Boot Start End Blocks Id System /dev/hda1 63 2104514 1052226 83 Linux /dev/hda2 2104515 6297479 2096482+ 83 Linux /dev/hda3 6329610 39054014 16362202+ 5 Extended /dev/hda5 6329673 10522574 2096451 83 Linux /dev/hda6 10522638 14715539 2096451 83 Linux /dev/hda7 14715603 18908504 2096451 83 Linux /dev/hda8 18908568 23101469 2096451 83 Linux /dev/hda9 23101533 25205984 1052226 82 Linux swap
Notice that there is a gap between start of the extended partition (hda3) and the start of the first logical partition (hda5). For the logical partitions (hda5 through hda9), there are also gaps between the end of one logical partition and the start of the next logical partition. These gaps contain metadata for partition information. Because these metadata regions lie inside the public region, VxVM allocates subdisks over them to prevent accidental allocation of this space to volumes.
After the root disk has been encapsulated, the output from the vxprint command appears similar to the following:
Disk group: rootdg TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg rootdg rootdg - - - - - - dm disk01 sdh - 17765181 - - - - dm rootdisk hda - 39053952 - - - - sd meta-rootdisk05 - ENABLED 63 - - - METADATA sd meta-rootdisk06 - ENABLED 63 - - - METADATA sd meta-rootdisk07 - ENABLED 63 - - - METADATA sd meta-rootdisk08 - ENABLED 63 - - - METADATA sd meta-rootdisk09 - ENABLED 63 - - - METADATA sd meta-rootdisk10 - ENABLED 63 - - - METADATA sd rootdiskPriv - ENABLED 2049 - - - PRIVATE v bootvol fsgen ENABLED 2104452 - ACTIVE - - pl bootvol-01 bootvol ENABLED 2104452 - ACTIVE - - sd rootdisk-07 bootvol-01 ENABLED 2104452 0 - - - v homevol fsgen ENABLED 4192902 - ACTIVE - - pl homevol-01 homevol ENABLED 4192902 - ACTIVE - - sd rootdisk-05 homevol-01 ENABLED 4192902 0 - - - v optvol fsgen ENABLED 4192902 - ACTIVE - - pl optvol-01 optvol ENABLED 4192902 - ACTIVE - - sd rootdisk-04 optvol-01 ENABLED 4192902 0 - - - v rootvol root ENABLED 4192902 - ACTIVE - - pl rootvol-01 rootvol ENABLED 4192902 - ACTIVE - - sd rootdisk-02 rootvol-01 ENABLED 4192902 0 - - - v swapvol swap ENABLED 2104452 - ACTIVE - - pl swapvol-01 swapvol ENABLED 2104452 - ACTIVE - - sd rootdisk-01 swapvol-01 ENABLED 2104452 0 - - - v usrvol fsgen ENABLED 4192965 - ACTIVE - - pl usrvol-01 usrvol ENABLED 4192965 - ACTIVE - - sd rootdisk-06 usrvol-01 ENABLED 4192965 0 - - - v varvol fsgen ENABLED 4192902 - ACTIVE - - pl varvol-01 varvol ENABLED 4192902 - ACTIVE - - sd rootdisk-03 varvol-01 ENABLED 4192902 0 - - -
The new partition table for the root disk appears similar to the following:
# fdisk -ul /dev/hda Disk /dev/hda: 255 heads, 63 sectors, 2431 cylinders Units = sectors of 1 * 512 bytes Device Boot Start End Blocks Id System /dev/hda1 63 2104514 1052226 83 Linux /dev/hda2 2104515 6297479 2096482+ 83 Linux /dev/hda3 6329610 39054014 16362202+ 5 Extended /dev/hda4 63 39054014 19526976 7e Unknown /dev/hda5 6329673 10522574 2096451 83 Linux /dev/hda6 10522638 14715539 2096451 83 Linux /dev/hda7 14715603 18908504 2096451 83 Linux /dev/hda8 18908568 23101469 2096451 83 Linux /dev/hda9 23101533 25205984 1052226 82 Linux swap /dev/hda10 39051966 39054014 1024+ 7f Unknown
In this example, primary partition hda4 and logical partition hda10 have been created to represent the VxVM public and private regions respectively.