Overview: The Next Generation Mass Storage Stack (September 2009)

Table Of Contents

iobind(1M)

The iobind command unbinds the driver from an existing LUN and binds a new driver to it. You can use

iobind to override a default driver selection made by the operating system. In releases prior to HP-UX 11i v3,

forcing a particular driver to claim a specified device was done through driver statements in the

/stand/system file. This method is supported in HP-UX 11 v3, but the iobind command supersedes it.

The iobind command syntax is as follows:

# iobind –M driver_name -H hw_path [-I instance]

This command unbinds a driver from the device at the specified hardware path. If the unbinding is successful, the

named driver is then bound to the device. If the unbinding cannot be done immediately, either because the device

is in use or the driver does not support it, iobind prints a warning, and the binding is applied on the next reboot.

The driver bound explicitly using the above mechanism is retained across reboots. You can specify an instance

number to be assigned to the new binding with –I.

io_redirect_dsf(1M)

The io_redirect_dsf command is used when you replace a mass storage device with a similar device, and

you want to use the existing DSF to access the replacement device. This command redirects the DSF to the

replacement disk by assigning the instance number of the replaced disk to the new disk. The DSF name of the new

disk, which is created using the base name and instance number, is the same as that of the replaced disk. After

physically replacing the disk, use the io_redirect_dsf command as follows:

# io_redirect_dsf –H old_device_LUN_hw_path –N new_device_LUN_hw_path

# io_redirect_dsf –d old_dsf_name –n new_dsf_name

The replacement disk must belong to the same class as the original disk for the DSF redirection to succeed. The

io_redirect_dsf command can only be used to redirect DSFs in the agile view. Redirection of a DSF from a

disk to a new disk results in a short application downtime.

Note: Use the io_redirect_dsf command only if the replacement disk has a different WWID from the

original disk. Replacing an internal disk or a disk in a JBOD changes the WWID because the LUN maps

directly to the physical disk. Disk LUNs in arrays are not mapped to physical disks. Replacing a disk in an

array does not change the LUN WWID as seen from the host, so io_redirect_dsf is not necessary.

iofind(1M)

The iofind command is a tool to assist migration from the legacy view to the agile view. It scans ASCII files on a

system, locates references to legacy DSFs and hardware paths, and optionally replaces them with their agile

equivalents. You can limit the search patterns to specific DSFs or hardware paths. The search can recurse from the

root directory, or be limited to a specific set of directories. If no DSF or hardware path is specified, iofind uses

ioscan to get the list of valid DSFs or hardware paths on the system and creates a file containing the mapping

for all entries. If you choose to replace the legacy information with its agile equivalent, the original ASCII files are

preserved in a backup directory.

For additional information on migrating to the agile view, see the HP-UX 11i v3 Persistent DSF Migration Guide in

For more

information.