Large Volume Support in Solaris Volume Manager

Large volume support enhances Solaris Volume Manager. With this support, the Solaris Volume Manager can create, manage, and delete large (>1Tbyte) RAID 0 (stripe), RAID 1 (mirror), RAID 5, and soft partition volumes. In addition, large volume support enables Solaris Volume Manager to construct volumes on large or EFI-labeled logical unit numbers (LUNs). 

Solaris Volume Manager large volume support is not available for systems that run a 32-bit Solaris kernel. For example, systems that run the Solaris operating environment (x86 Platform Edition) or the Solaris operating environment SPARC 32-bit kernel cannot use large volume support. 

For further information, see the Solaris Volume Manager Administration Guide.

See also the “Large Volume Support With EFI Disk Label” in File System Enhancements.

4/03 

Reconfiguration Coordination Manager Support in Solaris Volume Manager

Reconfiguration Coordination Manager (RCM) support adds to Solaris Volume Manager the ability to respond appropriately to dynamic reconfiguration (DR) requests. This addition ensures that removal of devices under Solaris Volume Manager control is blocked with an appropriate warning until the devices are no longer in use. This warning prevents system administrators from accidentally removing active volumes from a DR-configured system.  

For further information, see the Solaris Volume Manager Administration Guide.

4/03 

Solaris Patch Update Feature

You can use the Update option of the Solaris Management Console's Patches Tool or the smpatch update command to analyze, download, and install recommended patches from the SunSolve Online^SM program.

The update feature was previously only available for systems that run the Solaris 2.6, Solaris 7, or Solaris 8 releases. 

You must install the PatchPro 2.1 software on your system before running the update feature. Download the PatchPro 2.1 packages from http://www.sun.com/PatchPro and follow the instructions to install the software on your system.

For more information, see the smpatch(1M) man page.

4/03 

Combine Data Address and Test Address for Singleton IP Network Multipathing Group

The use of a dedicated test IP address for failure detection on single-adapter IP network multipathing groups is no longer required. When failover is not possible because only one network information center (NIC) is in an IP network multipathing group, you can now combine the test address and the data address. The in.mpathd daemon uses a data address to detect failure when a test address is not specified.

For further information on Solaris IP multipathing, see the IP Network Multipathing Administration Guide.

12/02