Skip Navigation Links | |
Exit Print View | |
Solaris Volume Manager Administration Guide Oracle Solaris 10 1/13 Information Library |
1. Getting Started With Solaris Volume Manager
2. Storage Management Concepts
3. Solaris Volume Manager Overview
4. Solaris Volume Manager for Sun Cluster (Overview)
5. Configuring and Using Solaris Volume Manager (Scenario)
8. RAID-0 (Stripe and Concatenation) Volumes (Overview)
9. RAID-0 (Stripe and Concatenation) Volumes (Tasks)
Creating RAID-0 (Concatenation) Volumes
How to Create a RAID-0 (Concatenation) Volume
How to Expand Storage Capacity for Existing Data
How to Expand an Existing RAID-0 Volume
10. RAID-1 (Mirror) Volumes (Overview)
11. RAID-1 (Mirror) Volumes (Tasks)
12. Soft Partitions (Overview)
16. Hot Spare Pools (Overview)
20. Maintaining Solaris Volume Manager (Tasks)
21. Best Practices for Solaris Volume Manager
22. Top-Down Volume Creation (Overview)
23. Top-Down Volume Creation (Tasks)
24. Monitoring and Error Reporting (Tasks)
25. Troubleshooting Solaris Volume Manager (Tasks)
A. Important Solaris Volume Manager Files
B. Solaris Volume Manager Quick Reference
Caution - Do not create a stripe from an existing file system or data. Doing so destroys data. To create a stripe from existing data, you must back up the data, create the stripe volume, and then restore the data to the volume. |
Caution - Do not create volumes larger than 1Tbyte if you expect to run the Solaris software with a 32-bit kernel. Additionally, do not create volumes larger than 1Tbyte if you expect to use a version of the Solaris OS prior to the Solaris 9 4/03 release. See Overview of Multi-Terabyte Support in Solaris Volume Manager for more information about large volume support in Solaris Volume Manager. |
Before You Begin
Check Prerequisites for Creating Solaris Volume Manager Components and Background Information for Creating RAID-0 Volumes.
From the Enhanced Storage tool within the Solaris Management Console, open the Volumes node. Choose Action⇒Create Volume, then follow the instructions in the wizard. For more information, see the online help.
Use the following form of the metainit command:
# metainit volume-name number-of-stripes components-per-stripe component-names [ -i interlace]
Specifies the name of the volume to create. For information on naming volumes, see Volume Names.
Specifies the number of stripes to create.
Specifies the number of components each stripe should have.
Specifies the names of the components that are used. If more than one component is used, separate each component with a space.
Specifies the interlace width to use for the stripe. The interlace width is a value, followed by either `k' for kilobytes, `m' for megabytes, or `b' for blocks. The interlace specified cannot be less than 16 blocks, or greater than 100 megabytes. The default interlace width is 16 kilobytes.
See the following examples and the metainit(1M) man page for more information.
Example 9-1 Creating a RAID–0 (Stripe) Volume of Three Slices
# metainit d20 1 3 c0t1d0s2 c0t2d0s2 c0t3d0s2 d20: Concat/Stripe is setup
This example shows the stripe, d20, consists of a single stripe (the number 1). The stripe is composed of three slices (the number 3). Because no interlace value is specified, the stripe uses the default of 16 Kbytes. The system confirms that the volume has been set up.
Example 9-2 Creating a RAID-0 (Stripe) Volume of Two Slices With a 32–Kbyte Interlace Value
# metainit d10 1 2 c0t1d0s2 c0t2d0s2 -i 32k d10: Concat/Stripe is setup
This example shows the stripe, d10, consists of a single stripe (the number 1). The stripe is composed of two slices (the number 2). The -i option sets the interlace value to 32 Kbytes. (The interlace value cannot be less than 8 Kbytes, nor greater than 100 Mbytes.) The system verifies that the volume has been set up.
See Also
To prepare the newly created stripe for a file system, see Chapter 15, Creating and Mounting File Systems (Tasks), in System Administration Guide: Devices and File Systems. Some applications, such as a database, do not use a file system. These applications instead use the raw device. The application must have its own way of accessing the raw device.