After registration of disks with GDS is complete, accessing the disks using physical special files as below becomes impossible. GDS prevents unintentional access by the users to physical special files in order to protect mirroring statuses.
/dev/[r]dsk/cCtTdDs[0-7] (for normal hard disks) /dev/FJSVmphd/[r]dsk/mphdI s[0-7] (for MPHD disks) /dev/FJSVmplb/[r]dsk/mplbI s[0-7] (for MPLB disks)
C indicates the controller; T, the target ID; D, the disk number; I, the MPHD instance number or the MPLB instance number; [0-7], the slice number with 1 digit from 0 to 7.
For example, if you execute the dd command to write to the disk with physical special file, the following error message will be displayed.
# dd if=/dev/zero of=/dev/rdsk/c1t1d0s0 |
Disk list output by the format(1M) command does not display the disk registered with GDS.
This access protection is cancelled when a disk is removed from a class. It will also be cancelled when an object is used for disk swap. The access protection function will turn back on if disk recovery operation is performed on the object.
Access to physical special files is prevented on the following nodes:
For disks that are registered with disk classes
When registered with the PRIMECLUSTER's resource database
All of the nodes in the relevant domains
When not registered with the PRIMECLUSTER's resource database
Nodes where the relevant disk classes (root classes or local classes) reside
For disks that are registered with shadow classes
Nodes where the relevant shadow classes reside
For the following disks, access to physical special files is not prevented. Be careful not to access these physical special files.
Disks that are registered with classes in other domains
Disks that are registered with root classes or local classes on other nodes and for which disk resources are not registered with the resource database
Disks that are registered with shadow classes on other nodes
