[ Previous |
AIX Version 4 Files Reference
Contains information on the image installed during the Base Operating System installation process.
The image.data file contains information describing the image installed during the BOS installation process. This information includes the sizes, names, maps, and mount points of logical volumes and file systems in the root volume group. The mkszfile command generates the image.data file. It is not recommended that the user modify the file. Changing the value of one field without correctly modifying any related fields can result in a failed installation and a corrupted backup image. The only exception to this recommendation is the SHRINK field, which the user may modify to instruct the BOS installation routines to create the file systems as specified in the image.data file or to create the file systems only as large as is required to contain all the data in the file system.
The BOS installation process also takes input from the image.data file regarding defaults for the machine being installed. Any default values in the image.data file will override values obtained when the BOS installation queries the hardware topology and existing root volume group. The image.data file resides in the / directory.
Note: The image.data file replaces the .fs.size file used in release 3.2.
The image.data file is arranged in stanza format. Each stanza contains one or more fields. These stanzas include the following:
|| Identifies the format of the image. Examples include backup file format (bff) and tar format.|
|| Contains the date and time that the image was taken.|
|| Identifies the system and system level data was taken from.|
|| Specifies whether the image is a product image or a mksysb image. The possible field values are yes or no.|
|| Lists the user volume groups defined in the system.|
Note: The PRODUCT_TAPE and USERVG_LIST fields are only present for the ROOTVG volume group.
|| Instructs BOS install routines to create the file systems as they are specified in the image.data file or create the smallest file systems required to contain all the data in the file system. The field value specified can be yes (shrink file systems) or no (use image.data file specifications).|
|| The field value specified can be yes or no. If yes is specified, the disk information listed in the source_disk_data stanza must match the actual disks found on the target machine during installation.|
|| Sets the language used by the BOS Install program.|
Note: The image.data file contains one source_disk_data stanza for each disk in the root volume group.
|| Supplies the names of the disks in the root volume group.|
|| Supplies the locations of the disks in the root volume group.|
|| Supplies the size, in MB, of the disks in the root volume group.|
Note: The image.data file can contain only one vg_data stanza.
|| Specifies the volume group name.|
|| Specifies the size of the physical partition for the volume group.|
|| Activates the volume group and all associated logical volumes so that the volume group is available for use. The field value can be yes or no.|
|| Lists the disks in the volume group.|
Note: The image.data file contains one lv_data stanza for each logical volume created on the system.
|| Specifies the logical volume group name. Volume group names must be unique systemwide and can range from 1 to 15 characters.|
|| Lists the disks in the logical volume.|
|| Contains the identifier of the logical volume.|
|| Contains the name of the logical volume.|
|| Sets the access permissions. The field value can be read/write or read only.|
|| Indicates the state of the volume group. If the volume group is activated with the varyonvg command, the value of the VG_STAT field is either active/complete or active/partial. An active/complete field value indicates that all physical volumes are active, while an active/partial field value indicates that all physical volumes are not active. If the volume group is not activated with the varonvg command, the VG_STAT field value is inactive.|
|| Describes the logical volume type.|
|| Sets the maximum number of logical partitions within the logical volume.|
|| Specifies the number of physical partitions created for each logical partition during the allocation process.|
|| Specifies the number of logical partitions currently in the logical volume.|
|| Specifies the number of physical partitions in the logical volume that are not current.|
|| Specifies the inter-physical allocation policy. The field value can be minimum or maximum.|
|| Specifies the intra-physical allocation policy. The possible field values are either middle, center, or edge.|
|| Specifies the file-system mount point for the logical volume, if applicable.|
|| Specifies mirror-write consistency state. The field value can be off or on.|
|| Specifies a yes or no field value for strict allocation. A yes value for strict allocation states that no copies for a logical partition are allocated on the same physical volume. A no value for strict allocation (nonstrict) states that at least one occurrence of two physical partitions belong to the same logical partition.|
|| Describes the state of the logical volume. An Opened/stale value indicates the logical volume is open but contains physical partitions that are not current. An Open/syncd value indicates the logical volume is open and its physical partitions are current, or synchronized. A Closed value indicates the logical volume has not been opened.|
|| Specifies the field value of the write verify state as on or off.|
|| Provides the size physical partition.|
|| Specifies a sequential or parallel scheduling policy.|
|| Specifies the number of physical partitions currently in the logical volume.|
|| Specifies the bad block relocation policy.|
|| Indicates whether the partitions can be relocated if a reorganization of partition allocation takes place. The field value can be yes or no.|
|| Specifies the maximum number of physical volumes for allocation.|
|| Specifies the label field for the logical volume.|
|| Provides the full path name to a map file to be used in creating the logical volume.|
|| Specifies the minimum size of the logical volume to use when shrinking the logical volume.|
|| Specifies the number of physical volumes being striped across.|
|| Specifies the number of bytes per stripe. The field value must be a power of two, between 4K and 128K; for example, 4K, 8K, 16K, 32K, 64K, or 128K.|
|| Specifies the mount point of the file system.|
|| Supplies the size, in 512-byte blocks, of the file system.|
|| Specifies the minimum size required to contain the files of the file system. This size is used when the SHRINK field in the logical_volume_policy stanza has a field value of yes.|
|| Provides the logical volume name. The name must contain the /dev/ prefix. An example of an appropriate name is /dev/hd4.|
|| Specifies the fragmentation size of the system. This value is optional.|
|| Specifies the number of bytes per inode. This value is optional.|
|| Designates whether the file system should be compressed or not. The field value can be LZ, which compresses the file system, or the no field value.|
|| Enables the file system for files greater than 2 GB. The possible values are true or false.|
|| Specifies the allocation group size. The possible values are 8, 16, 32, or 64. The allocation group size is specified in units of megabytes.|
|| Provides the full path name of a file or command to execute after BOS install completes.|
|| Specifies the full path name of the file or command to execute after the restvg process completes.|
Note: The post_install_data stanza exists for the ROOTVG volume group and the post_restvg stanza is present for other volume groups.
This file is part of System Backup and BOS Install Utilites.
The mkszfile command, mkfs command, mklv command, and lslv command.
[ Previous |