Use this procedure to add a disk drive to a running cluster. Perform the steps in this procedure in conjunction with the procedures in the Sun Cluster 3.0 U1 System Administration Guide and your server hardware manual. "Example--Adding a StorEdge D1000 Disk Drive" shows how to apply this procedure.
For conceptual information on quorum, quorum devices, global devices, and device IDs, see the Sun Cluster 3.0 U1 Concepts document.
Locate an empty disk slot in the StorEdge D1000 disk array for the disk drive you are adding.
Identify the disk slot in the StorEdge D1000 disk array for the disk drive that you are adding and note the target number. Refer to the documentation that shipped with your StorEdge D1000 disk array.
Install the disk drive.
For the procedure on installing a disk drive, see the Sun StorEdge D1000 Storage Guide.
On all nodes attached to the StorEdge D1000 disk array, configure the disk drive.
# cfgadm -c configure cN # devfsadm |
On all nodes, verify that entries for the disk drive have been added to the /dev/rdsk directory.
# ls -l /dev/rdsk |
If necessary, use the format(1M) command or the fmthard(1M) command to partition the disk drive.
From any node, update the global device namespace.
If a volume management daemon such as vold is running on your node, and you have a CD-ROM drive that is connected to the node, a device busy error might be returned even if no disk is in the drive. This error is an expected behavior.
# scgdevs |
On all nodes, verify that a device ID (DID) has been assigned to the disk drive.
# scdidadm -l |
As shown in "Example--Adding a StorEdge D1000 Disk Drive", the DID 35 that is assigned to the new disk drive might not be in sequential order in the disk array.
Perform volume management administration to add the new disk drive to the configuration.
For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.
The following example shows how to apply the procedure for adding a StorEdge D1000 disk array disk drive.
# scdidadm -l 16 phys-circinus-3:/dev/rdsk/c2t0d0 /dev/did/rdsk/d16 17 phys-circinus-3:/dev/rdsk/c2t1d0 /dev/did/rdsk/d17 18 phys-circinus-3:/dev/rdsk/c2t2d0 /dev/did/rdsk/d18 19 phys-circinus-3:/dev/rdsk/c2t3d0 /dev/did/rdsk/d19 ... 26 phys-circinus-3:/dev/rdsk/c2t12d0 /dev/did/rdsk/d26 30 phys-circinus-3:/dev/rdsk/c1t2d0 /dev/did/rdsk/d30 31 phys-circinus-3:/dev/rdsk/c1t3d0 /dev/did/rdsk/d31 32 phys-circinus-3:/dev/rdsk/c1t10d0 /dev/did/rdsk/d32 33 phys-circinus-3:/dev/rdsk/c0t0d0 /dev/did/rdsk/d33 34 phys-circinus-3:/dev/rdsk/c0t6d0 /dev/did/rdsk/d34 8190 phys-circinus-3:/dev/rmt/0 /dev/did/rmt/2 # cfgadm -c configure c1 # devfsadm # scgdevs Configuring DID devices Could not open /dev/rdsk/c0t6d0s2 to verify device id. Device busy Configuring the /dev/global directory (global devices) obtaining access to all attached disks reservation program successfully exiting # scdidadm -l 16 phys-circinus-3:/dev/rdsk/c2t0d0 /dev/did/rdsk/d16 17 phys-circinus-3:/dev/rdsk/c2t1d0 /dev/did/rdsk/d17 18 phys-circinus-3:/dev/rdsk/c2t2d0 /dev/did/rdsk/d18 19 phys-circinus-3:/dev/rdsk/c2t3d0 /dev/did/rdsk/d19 ... 26 phys-circinus-3:/dev/rdsk/c2t12d0 /dev/did/rdsk/d26 30 phys-circinus-3:/dev/rdsk/c1t2d0 /dev/did/rdsk/d30 31 phys-circinus-3:/dev/rdsk/c1t3d0 /dev/did/rdsk/d31 32 phys-circinus-3:/dev/rdsk/c1t10d0 /dev/did/rdsk/d32 33 phys-circinus-3:/dev/rdsk/c0t0d0 /dev/did/rdsk/d33 34 phys-circinus-3:/dev/rdsk/c0t6d0 /dev/did/rdsk/d34 35 phys-circinus-3:/dev/rdsk/c2t13d0 /dev/did/rdsk/d35 8190 phys-circinus-3:/dev/rmt/0 /dev/did/rmt/2 |
To configure a disk drive as a quorum device, see the Sun Cluster 3.0 U1 System Administration Guide for the procedure on adding a quorum device.