Starting with
There are a number of other Ignite tasks that require the identification of I/O devices:
•When building installation media, you must use the ioscan command to find the tape, CD, or DVD drive. Note that some of the CD/DVD writing SW included with
•When performing a system recovery on
•During
•When in expert recovery mode, you must have the hardware path of the disk you are attempting to recover.
•When identifying disks in configuration files to define them or combine them in a single volume group, you must supply the hardware paths of the disks.
Important characteristics of the agile viewThe following points will help you move from the legacy view to the agile view:
•When using the new persistent DSFs, be sure to use the new directory structure: Table 3 Mass storage DSF directories
Persistent DSF Directory | Legacy DSF Directory |
|
|
/dev/disk | /dev/dsk |
|
|
/dev/rdisk | /dev/rdsk |
|
|
/dev/rtape | /dev/rmt |
|
|
•Both legacy and persistent DSFs can be created during installation and recovery of
NOTE: The VxVM components in the
•Keep in mind that persistent DSFs endure with recovery if Ignite recovers to the same hardware or can map to replacement hardware, but are not guaranteed to remain the same between installations. See Figure 25 for an overview regarding consistency of I/O addressing.
•If hardware is replaced and recovery is not needed, you might want to run io_redirect_dsf to correct the system configuration. For more information, see io_redirect_dsf(1M).
78 Managing I/O for installation and recovery