Please show us attributes of the resource - copy the mount resource section in main.cf and post here.
Please also confirm if you can successfully mount and unmount at OS level.

See Bundled Agent Guide  (download from https://sort.symantec.com/documents/doc_details/sfha/6.0/Solaris/ProductGuides/ ) for ZFS file system and pool creation example as well as sample mount resource.

If you want to use Mount agent to manage a zfs file system, you need to set MountPoint attribute of zfs filsystem to legacy. This allows os commands like mount/umount to mange a zfs file system.

Set the value of the MountPoint attribute to legacy.
# zfs set mountpoint=legacy <zfs file system>

If you can provide the main.cf snippet and relevent part of engine/Mount agent log, we can help you better.

# zfs set mountpoint=legacy pool/px1

cannot set property for 'pool/px1': 'mountpoint' doesnot apply to datasets of this type

=====================================

Mount mount (
MountPoint = "/u3"
BlockDevice = "/pool/px1"
FSType = zfs
MountOpt = rw
FsckOpt = "-n"
)

Hi,

You need to set legacy setting to pool dataset.

Hope the following will help you.

#zfs list
NAME    USED  AVAIL  REFER  MOUNTPOINT
tpool  85.5K  9.78G    21K  /tpool
#zfs create tpool/tvol
#zfs list
NAME         USED  AVAIL  REFER  MOUNTPOINT
tpool        114K  9.78G    21K  /tpool
tpool/tvol    21K  9.78G    21K  /tpool/tvol
#zfs set mountpoint=legacy tpool
#zfs list
NAME         USED  AVAIL  REFER  MOUNTPOINT
tpool        116K  9.78G    23K  legacy
tpool/tvol    21K  9.78G    21K  legacy
#mount -F zfs tpool/tvol /zfsdir
#mount | grep zfsdir
/zfsdir on tpool/tvol read/write/setuid/devices/nonbmand/exec/xattr/atime/dev=401.....

Note that BlockDevice is "tpool/tvol".

#zfs list

NAME               MOUNTPOINT

pool                  /pool/u2

pool/px1           -

#zfs set mountpoint=legacy pool

#zfs list

NAME            MOUNTPOINT

pool               legacy   

pool/px1        -

(The mountpoint of pool/px1 is not changing to legacy) ....

I guess I got your issue now.

you have zfs volume created using zfs create -V option and now tryng to mount that volume as a zfs file sytem.

Technically zfs volumes act as a block device but can not be mounted. It can be used for creating a ufs filesystem, add as a swap or iscsi tartget device. So setting mountpount for a zvol is not supported.

Why don't you create zfs file systems directly on top of a zpool instead of creating zvols?

Thanks all for kind replies. Leave it. Me going for ufs. Last question just...

We dont have vxvm and only we have HA/vcs  ...

Question: Without vxvm we cannot use the vxfs filesystem ?

To make use of all the features of vxfs, vxvm is required. Recommended configuration is also vxfs on top of vxvm.

Means in the current configuration(only HA/VCS) we cant use the vxfs filesystem unless we have to buy the vxvm OR storage foundation ?

To use VxFS you do not require VxVM in general, but to use full functionality of VxFS you need VxVM.

You should buy VxFS or SF licence to use vxfs.

Venkat.