Solstice DiskSuite & Solaris Volume Manager: How to Increase the Maximum Number of Metadevices and Metasets when Command Fails with "no available set numbers" or "No such file or directory"
Last updated on NOVEMBER 30, 2016
Applies to:Solstice DiskSuite Software - Version 4.2 to 4.2.1 [Release 4.0]
Sun Solaris Volume Manager (SVM) - Version 11.9.0 to 11.9.0 [Release 11.0]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on x86 (32-bit)
The followings are the symptoms when the limit of maximum metadevices (nmd) OR maximum metasets (md_nsets) are hit
(a) Symptom hitting the limit of maximum metadevices (nmd)
This document provide resolution to increase the limits by modifying kernel configuration file /kernel/drv/md.conf.
The condition for the change of limits to be effective is given.
A workaround to increase the limits is given even though the condition is NOT fulfilled.
Attempting to add additional SVM or SDS objects
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms