The mount agent does an fsck if required - see extract from bundled agent guide for FsckOpt attribute:

Use this attribute to specify options for the fsck command. You

must correctly set this attribute for local mounts. If the mount

process fails, the fsck command is executed with the specified

options before it attempts to remount the block device. Its value

must include either -y or -n. Refer to the fsck manual page for more

information.

BLOCK_DEVICE=$2
LOCKFILE=/tmp/.{$3}.DO_NOT_REMOVE
case "$1" in
start)
    touch $LOCKFILE
    fsck $BLOCK_DEVICE;;
stop)
    rm $LOCKFILE
    ;;
monitor)
if [ -a $LOCKFILE ]
then
        exit 110
    else
        exit 100
    fi ;;
*) 
    echo "Usage: $0 {start|stop|monitor} block_device lock_file
    exit 1
    ;;
esac 

Then create a resource using Application agent like:

Application fsk_vol1 (
  StartProgram = "/opt/VRTSvcs/bin/fsck.sh start /dev/vx/dsk/mydg/vol1 vol1"
  StopProgram = "/opt/VRTSvcs/bin/fsck.sh stop /dev/vx/dsk/mydg/vol1 vol1"
  MonitorProgram = "/opt/VRTSvcs/bin/fsck.sh monitor /dev/vx/dsk/mydg/vol1 vol1"
)

and make this resource dependent on diskgroup resource and make associated mount point dependent on this application resource

Mike