The gabdiskconf utility can be used to initialize a GAB disk region. It also writes the disk signature to the beginning of each block. The disk signature has three components :
1) a fixed system prefix, “GAB”
2) the node id for the block, and,
3) a 4-byte string representing the user-supplied signature. After the disk region has been initialized, the gabdiskx/gabdiskhb utilities can be used in conjunction with the -S option to initiate signature checks. Signature checks are optional, but, if employed, offer better disk region integrity
Below command (shown for different platforms) initializes a disk region starting at block no. 0 (at block 16, in the case of Solaris) with the string representing the signature specified by the user.
# /sbin/gabdiskconf -i /dev/dsk/c1t1d0s0 -s 16 -S1100
# /sbin/gabdiskconf -i /dev/hdisk4 -s 0 -S 1100
# /sbin/gabdiskconf -i /dev/sdg -s 0 -S 1100
# /sbin/gabdiskconf -i /dev/vg01/lvol1 -s 0 -S 1100
Other Popular Posts
- VCS 6.1 – How to allocate two disk heartbeating resources, one for port a (the GAB control port) and one for port h (the VCS port) using gabdiskhb.
- Solaris Troubleshooting NFS : error ‘cp: cannot create : Permission denied’
- VCS 6.1 : How to Configure vxfen driver for cluster I/O fencing using vxfenconfig?
- VCS 6.1 : How to Manage Cluster Systems using hasys
- Linux Virual Machines : Add additional storage and extend LV with the additional space.
- Solaris Troubleshooting Reference – Forcing a coredump on hung x86 / x64 solaris system
- Solaris Troubleshooting : Forcing a coredump on hung x86 / x64 solaris system
- VCS 6.1 – How to configure and display information about Group and Atomic Broadcast (GAB) ports
- VCS 6.1 : How to Query Log Data Files using the hamsg?
- Solaris Troubleshooting : recover hung System Controller [ Sun Fire v1280, E2900, 3800, 4800, 4810, 6800, E4900, E6900, and Netra 1280, 1290 Server ]