Sun Enterprise 6x00, 5x00, 4x00, and 3x00 Systems Dynamic Reconfiguration User's Guide

Terminating I/O Devices

Terminate the use of all devices in the board. All I/O devices must be closed before they are unconfigured.

  1. Terminate all usage of devices on the board.

    1. To identify the components that are on the board to be unconfigured, use the ifconfig, mount, pf, or swap commands.

    2. To see which processes have these devices open, use the fuser(1M) command.

    3. Ensure that any networking interfaces on the board are not in use. All storage devices attached to the board should be unmounted and closed. See "I/O Board Unconfiguration".


      Note -

      DR does not automatically terminate network use or close devices. There currently is no way to ensure that the use of the network remains terminated or that all devices remain closed. Other clients may remount them between the time of the unmount and the unconfigure operations, so be careful.


    4. If AP (alternate pathing) is in use on the system, switch all board functions to the alternate board. Wait until all of the alternate paths are functioning before proceeding to Step 2.

    5. If AP is not available, warn all users to stop using the functions that the board provides.

  2. 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.

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

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

  5. Remove any private regions used by Sun(TM) Enterprise Volume Manager(TM). 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.

  6. Any Sun(TM) RSM Array(TM) 2000 controllers on the board that is being detached should be taken offline, using the rm6 or rdacutil commands.

  7. Remove disk partitions from the swap configuration.

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

  9. 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.


    Caution - Caution -

    Unmounting file systems may affect NFS(TM) client systems.