ioinit.1m (2010 09)

i
ioinit(1M) ioinit(1M)
If the driver associated with at least one given hardware paths does not support online
instance number reassignment, the
-r option must also be specified. (See the
-r option
below.) If the infile contains a hardware path of a node whose driver does not support
online instance number reassignment and
-r option is not specified, the command aborts
the operation.
-c Recreates /stand/ioconfig
, /stand/ext_ioconfig
, /etc/ioconfig
, and
/etc/ext_ioconfig
files from the kernel if any of these files are missing or cannot be
restored from backup. Whenever
ioinit updates these files from information obtained
from the kernel, it saves the current ioconfig file (the last known good one) before updat-
ing them as /stand/ioconfig.lkg
, /stand/ext_ioconfig.lkg
,
/etc/ioconfig.lkg
, and /etc/ext_ioconfig.lkg
in order to keep them syn-
chronized with kernel I/O data structures. If ioconfig files are missing or corrupt, users
are advised to copy the file from the last known good file (
.lkg) so that the least amount
of information is lost. If
-c
is invoked, any previous binding of hardware path to device
class and instance number may be lost.
-C class_name
Forces the kernel to reassign instance numbers starting from 0 for all existing devices
with the given class_name . This option must be used with the
-r option. On successful
completion the system is rebooted immediately.
-f infile Use the file infile to reassign instance numbers to devices within a specified class. infile
may have multiple entries, each to appear on a separate line, each field in the entry
separated by one or more blanks. Entries should conform to the following format:
h/w_path class_name instance_#
ioinit preprocesses the contents of infile, looking for invalid entries, and prints out
explanatory messages. An entry is considered to be invalid if the specified hardware
path or class name does not already exist in the system. If the specified instance number
already exists for the given class, the entry is invalid if it is not for circular reassignment.
On successful completion of this operation, previous special files will still be associated
with the device.
-i Invoke insf to install special files for new devices after checking consistency between
the /etc versions of the ioconfig files and the /stand versions. This creates device spe-
cial files for any new devices found on the system.
-r Reboot the system when it is required to correct the inconsistent state between the ker-
nel, /stand/ioconfig, and
/stand/ext_ioconfig, as used with the -i option.
When used with the
-f option, if there are no errors associated with the instance reas-
signment, -r reboots the system.
-v ioconfig_file
Verify if there is any corruption in ioconfig_file. If the verification of ioconfig_file is suc-
cessful, the command displays a message showing if the type of ioconfig_file is either
legacy (for example,
/etc/ioconfig) or agile (for example, /etc/ext_ioconfig
).
Note: HP-UX should not be rebooted without the
/stand/ext_ioconfig file. If the
file is missing or corrupted, HP-UX will recreate the file before rebooting the system. If
the system needs to be booted without the /stand/ext_ioconfig file (thus losing all
the persistent I/O information (see ioconfig(4)), the user can delete the file and reboot the
system with the command reboot -q (see reboot (1M)).
RETURN VALUE
0 No errors occurred, although warnings might be issued.
1 ioinit encountered an error.
2 file was recognized as an ioconfig_file file but it was found corrupted during
verification.
DIAGNOSTICS
Most of the diagnostic messages from
ioinit are self-explanatory. Listed below are some messages
deserving further clarification. Errors cause ioinit to halt immediately.
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: September 2010