If needing to confirm the location of the Oracle voting devices, simply run an Oracle CRS command as below. In the example, the oracle user was used as this usually has the CRS_HOME variable declared in its profile:

cd $CRS_HOME/bin

$ pwd

/oracle/crshome/bin

$ ./crsctl query css votedisk

0. 0 /oracle/votevol/vote

located 1 votedisk(s).

So, in the above case, only one vote device resides on the system. When investigating, it actually turns out to be implemented on a shared filesystem:

/oracle/votevol on /dev/vx/dsk/oradg/votevol read/write/setuid/devices/delaylog/largefiles/qio/cluster/ioerror=mdisable/crw/dev=538f61a on Mon Dec 13 20:54:36 2010

and proof that the vote device is operating fine from this system, a vxtrace command can be run on the respective diskgroup:

75 START read vdev votevol block 5696 len 16 concurrency 1 pid 5962

75 END read vdev votevol op 75 block 5696 len 16 time 0

76 START write vdev votevol block 2490 len 1 concurrency 1 pid 0

76 END write vdev votevol op 76 block 2490 len 1 time 4

77 START write vdev votevol block 5696 len 16 concurrency 1 pid 0

77 END write vdev votevol op 77 block 5696 len 16 time 5

78 START write vdev votevol block 3152 len 16 concurrency 1 pid 0

78 END write vdev votevol op 78 block 3152 len 16 time 5

79 START read vdev votevol block 5696 len 16 concurrency 1 pid 5962

79 END read vdev votevol op 79 block 5696 len 16 time 0

ps -ef | grep 5962

oracle 5962 5961 0 Dec 13 ? 29:05 /oracle/crshome/bin/ocssd.bin

The ocssd.bin process is an Oracle Clusterware process responsible (amongst other things) for disk heartbeating to the voting devices.

Applies To
Solaris 10

Storage Foundation for Oracle 5.0MP3

Oracle 10gr2