IA: How to Create a Multiple Disk Configuration File on Intel Architecture

If you need to test a profile on multiple disks, you can concatenate disk configuration files together to create multiple disk configuration scenarios.

Creating a multiple disk configuration file for an Intel architecture system involves:

• Concatenating two or more disk configuration files to create a multiple disk configuration file

• Changing the target numbers of disks in the multiple disk configuration file

  ---

  Note -

  Disk device target numbers must be unique on a system.

  ---

  The following procedure creates a multiple disk configuration file. (The procedure uses the 500_test file from the previous procedure.)

1. Concatenate a disk configuration file with itself and save it to a file.

   The new file becomes the multiple disk configuration file. For example, the following command creates a multiple disk configuration file named dual_500_test:

   $ cat 500_test 500_test > dual_500_test

2. Edit the disk configuration file so that each disk device name has a different target number.

   The dual_500_test file is shown as follows:

   * /dev/rdsk/c0t0d0p0 partition map * * Dimensions: * 512 bytes/sector * 79 sectors/track * 7 tracks/cylinder * 553 sectors/cylinder * 1481 cylinders * 1479 accessible cylinders * * Flags: * 1: unmountable * 10: read-only * * First Sector Last * Partition Tag Flags Sector Count Sector Mount Directory 0 2 00 553 194103 194655 1 3 01 194656 65807 260462 2 6 00 0 819546 819545 3 6 00 260463 50876 311338 4 6 00 311339 72996 384334 6 4 00 384335 434105 818439 8 1 01 0 553 552 fdisk physical geometry: cylinders[1855] heads[7] sectors[79] sector size[512] blocks[1025815] mbytes[500] fdisk virtual (HBA) geometry: cylinders[500] heads[64] sectors[32] sector size[512] blocks[1024000] mbytes[500] fdisk table on entry: SYSID ACT BHEAD BSECT BEGCYL EHEAD ESECT ENDCYL RELSECT NUMSECT 6 0 1 1 0 63 32 99 32 204768 130 128 0 1 100 63 96 243 204800 819200 100 0 0 0 0 0 0 0 100 100 100 0 0 0 0 0 0 0 100 100 * /dev/rdsk/c0t1d0p0 partition map * * Dimensions: * 512 bytes/sector * 79 sectors/track * 7 tracks/cylinder * 553 sectors/cylinder * 1481 cylinders * 1479 accessible cylinders * * Flags: * 1: unmountable * 10: read-only * * First Sector Last * Partition Tag Flags Sector Count Sector Mount Directory 0 2 00 553 194103 194655 1 3 01 194656 65807 260462 2 6 00 0 819546 819545 3 6 00 260463 50876 311338 4 6 00 311339 72996 384334 6 4 00 384335 434105 818439 8 1 01 0 553 552 fdisk physical geometry: cylinders[1855] heads[7] sectors[79] sector size[512] blocks[1025815] mbytes[500] fdisk virtual (HBA) geometry: cylinders[500] heads[64] sectors[32] sector size[512] blocks[1024000] mbytes[500] fdisk table on entry: SYSID ACT BHEAD BSECT BEGCYL EHEAD ESECT ENDCYL RELSECT NUMSECT 6 0 1 1 0 63 32 99 32 204768 130 128 0 1 100 63 96 243 204800 819200 100 0 0 0 0 0 0 0 100 100 100 0 0 0 0 0 0 0 100 100

   Because the dual_500_test file was created by concatenating itself, it required editing as follows:

   The first disk device name was left as is

   The second disk device name was changed from /dev/rdsk/c0t0d0p0 to /dev/rdsk/c0t1d0p0 so it has a unique target number.

   You have created a multiple disk configuration file for an Intel architecture system.