zvols with volblocksize > 8K cause zpools built on them to go unavail
(Doc ID 1918323.1)
Last updated on JANUARY 31, 2019
Solaris Operating System - Version 11.1 to 11.2 [Release 11.0] Information in this document applies to any platform.
If we create zvols in the Control/Primary Domain with volblocksize 128K (for performance), creating ZFS Storage Pools in the Guest fail spectacularly and become UNAVAIL. The customer first noticed this when they tried to expand one of their existing Guest pools by creating a new zvol in the dpool within the Control Domain, exporting it to the guest, and running 'zpool add <pool> <new vdev'. This caused the entire pool to go UNAVAIL immediately upon running the zpool add command.
After the fix forBug 15824925 - SUNBT7206382 zvol should support DKIOCGMEDIAINFOEXT,
the physical blocksize of a zvol is reported as the same its volblocksize property. This caused the ashift to be calculated as 17 when we created a zpool on the zvol.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!