Managing Shared Disks
When you start up your SP system, the IBM Recoverable Virtual Shared Disk
component does the following:
- Configures all defined virtual shared disks at system startup
using cfgvsd -a. All the virtual shared disks on the nodes
are in stopped state.
- When quorum is reached, the rvsd subsystem activates all virtual shared
disks with servers in the active group.
- All virtual shared disks on the active nodes that also have a server in
the active group will be in the active state.
- If an virtual shared disk's primary server node is in the active
group, the primary will be the server for that virtual shared disk.
- If an virtual shared disk's primary server is not in the active group
but the secondary server is, the secondary will be the server for that virtual
- All virtual shared disks without a server in the active group will be in
the stopped state.
- If quorum is lost, all the virtual shared disks are put into the stopped
state. When quorum is active again, the virtual shared disks are put
into appropriate states based on the list above.
The rvsd subsystem actively manages all configured virtual shared
disks. The recovery scripts invoke the preparevsd,
resumevsd, suspendvsd, stopvsd, varyonvg,
and varyoffvg commands asynchronously and automatically in the
background as virtual shared disk server nodes become active or fail.
If you have any script that issues any virtual shared disk command, you
should disable it so it does not interfere with rvsd recovery. Do not
issue any commands that change the state of virtual shared disks.
The commands you must not issue when the rvsd subsystem is running
- In order for the rvsd subsystem to be activated, there must be a
- After you install your system, you can start the IBM Virtual Shared Disk
and IBM Recoverable Virtual Shared Disk components with the ha_vsd
reset command. See the ha_vsd reference page in the book
PSSP: Command and Technical Reference, for the command
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]