Error Message

VxVM view:   (reporting ZFS managed luns correctly as auto:ZFS)

# vxdisk -e list | grep ZFS
emcpower100s2 auto:ZFS       -            -           ZFS                 emcpower100c     -
emcpower101s2 auto:ZFS       -            -           ZFS                 emcpower101c     -
emcpower102s2 auto:ZFS       -            -           ZFS                 emcpower102c     -


DCLI View: (VRTSsfmh command "vxlist disk" reporting ZFS devices as SVM managed luns)

# vxlist disk | grep ZFS

# vxlist disk | grep SVM
disk disk_1          -                  -                       -          - SVM
disk emcpower100s2   -                  -                       -          - SVM
disk emcpower101s2   -                  -                       -          - SVM
disk emcpower102s2   -                  -                       -          - SVM

 

The ZFS_FORMAT state was added into VxVM 5.1 SP1, however, the dcli interface needs to be enhanced to recognize it.

Hot-fix for VRTSsfmh (vxlist) created.

Contact Veritas support to obtain VOM hot-fix HFHF040015980-01.sfa.

 
Following the installation of the VOM hot-fix, the "vxlist disk" command is now able to report ZFS managed devices.

# vxlist disk | grep -i ZFS
disk emcpower100s2 -                -                   -        - ZFS
disk emcpower101s2 -                -                   -        - ZFS
disk emcpower102s2 -                -                   -        - ZFS



# vxlist disk | grep -i SVM
disk disk_1        -                -                   -        - SVM

Applies To

When a ZFS disk is created under Solaris ZFS it will put a ZFS ID on the disk. The ZFS signature is unique to ZFS and will be maintained at offset 31 (for Solaris 10 Update 8 onwards) and various back up locations on the disk.

Pre Solaris 10 Update 8 the signature is maintained at offset 16.


How to check for a ZFS signature with Solaris 10 Update 8


Storage Foundation 5.1 is aware of Solaris SVM and ZFS defined disks.

In the case of ZFS, VxVM will search for the unique ZFS signature strings " 0210da7a b10c7a11" at offset 31 (for VxVM 5.1RP1 onwards) and will flag the disk with a format type of "auto:ZFS".


# od -Ad -X /dev/rdsk/c#t#d#s0 | grep "210da7a b10c7a11" | more
 

0016336 00000000 00000000 0210da7a b10c7a11          <<<<< ZFS signature
0131024 00000000 00000000 0210da7a b10c7a11
0132048 00000000 00000000 0210da7a b10c7a11
 

To calculate the offset location of the ZFS signature block, type:
 

# bc
0016336/512
31

VxVM protects SVM and ZFS defined disks from being inadvertently used by VxVM, and prevent VxVM operations that may overwrite the disk.

These operations include initializing the disk for use by VxVM or encapsulating the disk.


If you attempt to perform one of these VxVM operations against a device that is in use by SVM or ZFS, VxVM displays an error message.


# /etc/vx/bin/vxdisksetup -if
VxVM vxdisksetup ERROR V-5-2-5716 Disk is in use by ZFS. Slice(s) 0 are in use as ZFS zpool (or former) devices.
If you still want to initialize this device for VxVM use, please destroy the zpool by running 'zpool' command if it is still active, and then remove the ZFS signature from each of these slice(s) as follows:
    dd if=/dev/zero of=/dev/vx/rdmp/ s[n] oseek=31 bs=512 count=1
    [n] is the slice number.

The "vxlist disk"  command in the VRTSsfmh VOM package does not report/recognize Solaris ZFS devices. The Veritas Volume Manager (VxVM) "vxdisk list" command is capable of reporting ZFS configured devices.

Solaris Volume Manager (SVM) is a logical volume manager software provided by Oracle (Sun). ZFS is a type of file system presenting a pooled storage model that Oracle developed.
  Note: VxVM can co-exist with SVM and ZFS controlled disks.