Oracle Documentation
The Solaris Volume Manager Administration Guide.
Blogs:
Jerry Jelinek's Weblog, Solaris Volume Manager x86 root mirroring
Jerry Jelinek's Weblog, Solaris Volume Manager root mirror problems on S10
Jerry Jelinek's Weblog, Solaris Volume Manager disksets
Brad Beadles, Root Mirroring, Patching, and Upgrading Practices
Roch (rhymes with Spock) Bourbonnais : Kernel Performance Engineering Weblog WHEN TO (AND NOT TO) USE RAID-Z.
Milek's blog HW RAID vs. ZFS software RAID and HW RAID vs. ZFS software RAID - part II.
gurkulindia.com, How to do MIRRORING under SVM (Solaris Volume Manager) in Solaris.
Exploring Solaris and Veritas, Solaris volume Manager
Broadcast Engineers, Solaris Volume Manager benefits quick overview
Solaris Commands, How To Replace A Failing SVM Disk
Solaris Commands, How To Tell The Difference Between A Failed Disk And A Failing Disk
Solaris Commands, How To Replace A Failed SVM Disk
Blog O. Matty, Archive for 'Solaris Volume Manager'
Bhusal's Blog Page, Solaris Volume Manager stuff...
Young, Replacing mirrored root disk in svm /sds in solaris 10 online
solaris 10 operating system, Planning Your SVM-SOLARIS 10
Pasko's Rants, Solaris SDS/ODS/SVM san migration with minimal downtime
Other:
From Sun Blue Prints, Solaris Volume Manager Performance Best Practices
OpenSolaris.org's OpenSolaris Community Solaris Volume Manager.
OpenSolaris.org's Solaris Volume Manager Internals Tutorial.
From Oracle University, Solaris Volume Manager Administration (ES-222 - D61894GC10)
What The Heck is RAID 10?
Solstice DiskSuite / Solaris Volume Manager Soft Partitioning
Solaris Volume Manager provides storage management tools that enable you to create and manage RAID 0, RAID 1, and RAID 5 volumes, as well as transactional (logging) devices and soft partitions. Solaris Volume Manager provides all of the capabilities of Solstice DiskSuiteTM and adds the following:
Soft partitions - Allow numerous partitions on a single drive, thus breaking the 8-slice barrier
Device ID support - Preserves Solaris Volume Manager configuration even if disks are moved or rearranged
Active monitoring of disks - Detects silent failures
Solaris Management Console based interface - Enables you to manage the enhanced storage devices through the same management interface that is used for other Solaris management tasks
Solaris Volume Manager WBEM application programming interface (API) - Enables standards-based management of Solaris Volume Manager from any compliant tool
The Solaris 9 release seamlessly supports upgrading existing systems that run Solaris DiskSuite (SDS) to the Solaris Volume Manager without disturbing or changing the configuration. Upgrades of mirrored root file systems are fully and automatically supported.
Solaris Volume Manager provides storage management tools that enable you to create and manage RAID 0, RAID 1, and RAID 5 volumes, as well as transactional (logging) devices and soft partitions. Solaris Volume Manager provides all of the capabilities of Solstice DiskSuiteTM and adds the following:
Soft partitions - Allow numerous partitions on a single drive, thus breaking the 8-slice barrier
Device ID support - Preserves Solaris Volume Manager configuration even if disks are moved or rearranged
Active monitoring of disks - Detects silent failures
Solaris Management Console based interface - Enables you to manage the enhanced storage devices through the same management interface that is used for other Solaris management tasks
Solaris Volume Manager WBEM application programming interface (API) - Enables standards-based management of Solaris Volume Manager from any compliant tool
The Solaris 9 release seamlessly supports upgrading existing systems that run Solaris DiskSuite (SDS) to the Solaris Volume Manager without disturbing or changing the configuration. Upgrades of mirrored root file systems are fully and automatically supported.
Solaris Volume Manager and a Mirrored boot disk configuration
- If fewer than 50 precent of the defined metadb replicas are available, Solaris Volume Manager ceases to operate.
- If fewer than or equal to 50 present of the defined metadb replicas are available at boot time, you cannot boot the system. However, you can boot single-user mode and just use the metadb command to delete ones that are not available.
To override this behavior you can add the following line to the /etc/system file.
set md:mirrored_root_flag=1
This allows you to boot fully with exactly 50 precent of the metadb's but not less than 50 precent.