Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

ZFS pool volume does not mounting via mount resource

Created: 07 Sep 2012 | 11 comments
Zahid.Haseeb's picture

Environment

HA = 6.0

Solaris = 10

single node cluster

one volume in zfs pool

pool name = pool

volume name = xxx

Query

Under service group of vcs I can define a mount resource and can successfully UP this resource with ufs filesystem but I am not able to UP mount  resource with zfs filesystem.

Discussion Filed Under:

Comments 11 CommentsJump to latest comment

Marianne's picture

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.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

sajith_cr's picture

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.

 

Regards,

Sajith

If this post has helped you, please vote or mark as solution.

Zahid.Haseeb's picture

# 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"
)

Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb

zahidhaseeb.wordpress.com

sajith_cr's picture

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".

 

Regards,

Sajith

If this post has helped you, please vote or mark as solution.

Zahid.Haseeb's picture

#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) ....

 

 

 

Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb

zahidhaseeb.wordpress.com

sajith_cr's picture

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?

 

Regards,

Sajith

If this post has helped you, please vote or mark as solution.

Zahid.Haseeb's picture

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 ?

Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb

zahidhaseeb.wordpress.com

sajith_cr's picture

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

Regards,

Sajith

If this post has helped you, please vote or mark as solution.

Zahid.Haseeb's picture

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

Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb

zahidhaseeb.wordpress.com

Venkata Reddy Chappavarapu's picture

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.

Venkata Reddy Chappavarapu,

Sr. Manager,

Information Availability Group (VCS),

Symantec Corporation

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

PS: If you are happy with the answer provided, please mark the post as sol

anand_raj's picture

Do you have VxFS license only? Does vxlicrep -s show valid license for "VERITAS File System"? Please don't paste the command output here as this is a public forum. Please let us know if you see a valid license or not. Thanks.