Solaris Volume Manager (SVM): metainit or metadb Fails with the Error "Overlaps with device" Because Both Disks Have the Same DEVID in Guest LDom
Last updated on OCTOBER 05, 2017
Applies to:Solaris Operating System - Version 10 5/08 U5 to 11.3 [Release 10.0 to 11.0]
Sun Solaris Volume Manager (SVM) - Version 11.9.0 to 11.11 [Release 11.0]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
Setting up a Solaris Volume Manager (SVM) mirror on a guest LDom doesn't work. Every attempt to create a metadevice on disk c0d1s0 or a replica on the same disk returns an error.
The configuration is that SVM metadevices where mapped to the Virtual Disk Server (VDS) and used in the guest domain as SVM devices again. The following example describe the details.
Two simple metadevices (d41 and d42) were added to VDS named guest0-vds0 on control/primary domain:
The two metadevices d41 and d42 on the control domain that are now simple metadevices originally were two submirrors of the same mirror.
In fact the following operations were done to trigger the issue:
• Initially created in the control domain a mirror metadevice d40 and assigned it to guest0 domain
d42 1 1 /dev/dsk/c0t5000CCA03C5A0DC8d0s4
d41 1 1 /dev/dsk/c0t5000CCA03C59E208d0s4
• Due to other requirements d40 was unassigned from the guest0 domain
• d40 mirror was cleared in the control domain and assigned the formerly submirrors d41 & d42 to the guest0 domain
• Currently both metadevices d41 & d42 are assigned to the guest0 domain
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms