NAME | SYNOPSIS | DESCRIPTION | OPTIONS | EXAMPLES | EXIT STATUS | ATTRIBUTES | SEE ALSO | NOTES
The scdidadm utility administers the disk ID (DID) pseudo device driver.
There are four primary operations that it performs: creating driver configuration files, modifying entries in the file, loading the current configuration into the kernel and listing the mapping between device entries and DID driver instance numbers.
The startup script /etc/init.d/bootcluster uses the scdidadm utility to initialize the DID driver. You can also use scdidadm to update or query the the current device mapping between the disks present and the corresponding disk ID and DID instance number.
The devfsadm(1M) creates the filesystem device entry points.
The following options are supported:
Perform a consistency check against the kernel representation of the devices and the physical devices. On failing a consistency check an error message is displayed. The process continues until all devices have been checked.
Remove all DID references to underlying devices which have been detached from the current node. This option should be used after the Solaris device commands have been used to remove references to non-existent devices on the cluster nodes.
You can only use this option from a node that is booted in cluster mode.
Print a header when listing device mappings. This option is meaningful only when used with the -l and -L flags.
Initialize the DID driver. This step is necessary to enable I/O requests to the DID driver.
List the local devices in the DID configuration file. The output of this command can be customized using the -o flag. When no -o options are specified, the default listing displays the instance number, the local fullpath and the fullname.
List all the paths, including those on remote hosts, of the devices in the DID configuration file. The output of this command can be customized using the -o flag. When no -o options are specified, the default listing displays the instance number, all local and remote fullpath strings and the fullname.
List the devices currently known to the did driver according to the format specification fmt. Multiple -o options can be specified; the fmt specification will be interpreted as a comma separated list of format option-arguments. This option is meaningful only when used with the -l and -L flags. The available format option-arguments include:
Print the instance number of the device known by the DID driver, for example, 1.
Print the physical path name of the device associated with this device ID, for example, /dev/rdsk/c0t3d0.
Print the full physical path name of the device associated with this device ID. This includes the host where the path is located. For example, phys-hostA:/dev/rdsk/c0t3d0.
With the -L option, print the names of all hosts that have connectivity to the specified device, one per line. With the -l option, print the name of the local host that has connectivity to the specified device.
Print the DID name of the device associated with this device ID for example, d1.
Print the full DID path name of the device associated with this device ID, for example, /dev/did/rdsk/d1.
Print the hexadecimal representation of the disk ID associated with the instance of the device being listed.
Print the ASCII representation of the disk ID associated with the instance of the device being listed.
Reconfigure the database. This flag results in a thorough search of the rdsk and rmt device trees. A new instance number is assigned for all device IDs not seen before. A new path is added for each newly discovered device.
You can only use this option from a node that is booted in cluster mode.
Perform repair procedures for a particular device instance. The argument to this command can be a particular physical device path that has been replaced with a new disk, or the instance number of the device that was just replaced.
This command does not modify the driver behavior until each of the nodes physically attached to the device has been rebooted.
This option also ensures correct SCSI reservation state on the specified device.
You can only use this option from a node that is booted in cluster mode.
Convert an existing /etc/did.conf file into a set of Cluster Configuration Repository (CCR) tables. If the tables already exist, this command will fail.
Load the device ID configuration table into the kernel. This option loads all the currently known configuration information about device paths and their corresponding instance numbers into the kernel.
Print the version number of this program.
The following example adds devices attached to the local host to the CCR:
% scdidadm -r |
The following example lists the physical path of the device corresponding to instance 2 of the DID driver:
% scdidadm -l -o path 2 /dev/dsk/c1t4d0 |
You can specify multiple format option arguments in either of the following ways:
% scdidadm –l –o path –o name 2 |
% scdidadm -l -o path,name 2 |
In either example, the output might look like:
/dev/dsk/c1t4d0 d1 |
The following example performs the repair procedures for a particular device path. Assuming the disk /dev/dsk/c1t4d0 has been replaced with a new disk with a new disk ID. The database is updated to reflect this new disk ID as the one corresponding to the instance number previously associated with the old disk ID:
% scdidadm -R c1t4d0 |
An alternative method of performing a repair procedure is to use the instance number associated with the device path. For example, if the instance number for the disk c1t4d0s0 in the previous example is 2, then the following syntax performs the same operation as the previous example:
% scdidadm -R 2 |
See attributes(5) for descriptions of the following attributes:
ATTRIBUTE TYPE |
ATTRIBUTE VALUE |
---|---|
Availability |
SUNWscu |
Interface Stability |
Evolving |
devfsadm(1M), scgdevs(1M), attributes(5),did(7)
Sun Cluster System Administration Guide
There is one caveat regarding multiported tape drives and CD-ROM drives. Each mulitported tape or CD-ROM drive appears in the namespace once per physical connection.
NAME | SYNOPSIS | DESCRIPTION | OPTIONS | EXAMPLES | EXIT STATUS | ATTRIBUTES | SEE ALSO | NOTES