Problems with I/O Devices

All I/O devices must be closed before they are unconfigured. To see which processes have these devices open, use the fuser(1M) command.

Perform the following tasks for I/O devices.

• If the redundancy features of Alternate Pathing or Solstice DiskSuite mirroring are used to access a device connected to the board, reconfigure these subsystems so that the device or network is accessible by way of controllers on other system boards.

• Unmount file systems, including Solstice DiskSuite meta-devices that have a board resident partition. (Example: umount/partit)

• Remove Solstice DiskSuite or Alternate Pathing databases from board-resident partitions. The location of Solstice DiskSuite or Alternate Pathing databases is explicitly chosen by the user and can be changed.

• Remove any private regions used by Sun Volume Manager or Veritas Volume Manager. Volume Manager by default uses a private region on each device that it controls, so such devices must be removed from Volume Manager control before they can be detached.

• Any RSM 2000 controllers on the board that is being detached should be taken offline, using the rm6 or rdacutil commands.

• Remove disk partitions from the swap configuration.

• Either kill any process that directly opens a device or raw partition, or direct it to close the open device on the board.

• If a detach-unsafe device is present on the board, close all instances of the device and use modunload(1M) to unload the driver.If a detach-unsafe device is present on the board, close all instances of the device and use modunload(1M) to unload the driver.

Unmounting file systems may affect NFS client systems.