Vdc Driver - Configuring Vdisk Physical Block Size in vdc.conf on a Guest Ldom
(Doc ID 1592785.1)
Last updated on FEBRUARY 09, 2021
Applies to:Solaris Operating System - Version 11.0 to 11.1 [Release 11.0]
Information in this document applies to any platform.
This document details a new feature in the lastest version of Solaris 18.104.22.168.0 helping with LUN alignement on NetApp filer using 4k sectors with a OVM for SPARC Guest Domain. (LDOM).
Previously one needed to implement settings described in document 1585893.1 in order to get ZFS pool ashift to equal 12. These settings don't work for a Guest Domain using Virtual Disk Client driver (vdc driver) as the check done on the disks to control the physical block size are done directly by the disk target driver vdc not the Solaris disk target driver sd/ssd.
When disks are controlled by the vdc driver on a guest ldom, you can see the following device path in format output:
In such configuration if one wanted to maintain the alignment, the workaround was to create the zpool on the control domain with the original ssd-config-list entry for NetApp in ssd.conf and export zfs volume dataset to the guest domain.
With the release of Solaris 22.214.171.124.0 one can now give full access to NetAPP logical unit to a guest ldom and create a zpool which will have an ashift value of 12.
This was made possible by the integration of <Bug 15824910>: Add support to configure vdisk physical block size in vdc.conf
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|The modification in vdc.conf file applies on a Guest Ldom:|
1. Create vdisk based on whole NetAPP logical unit and assign them to the guest ldom
2. Configure the physical block size of the vdisk in vdc.conf