This chapter describes RAID-0 (both stripe and concatenation) volumes that are available in Solaris Volume Manager. For information about related tasks, see Chapter 9, RAID-0 (Stripe and Concatenation) Volumes (Tasks).This chapter provides the following information:Overview of RAID-0 Volumes Background Information for Creating RAID-0 Volumes Scenario—RAID-0 Volumes RAID-0 volumes, are composed of slices or soft partitions. These volumes enable you to expand disk storage capacity. They can be used either directly or as the building blocks for RAID-1 (mirror) volumes, and soft partitions. There are three kinds of RAID-0 volumes:Stripe volumes Concatenation volumes Concatenated stripe volumes A component refers to any devices, from slices to soft partitions, used in another logical volume. A stripe volume spreads data equally across all components in the volume, while a concatenation volume writes data to the first available component until it is full, then moves to the next available component. A concatenated stripe volume is simply a stripe volume that has been expanded from its original configuration by adding additional components.RAID-0 volumes allow you to quickly and simply expand disk storage capacity. The drawback is that these volumes do not provide any data redundancy, unlike RAID-1 or RAID-5 volumes. If a single component fails on a RAID-0 volume, data is lost.For sequential I/O operations on a stripe volume, Solaris Volume Manager reads all the blocks in a segment of blocks (called an interlace) on the first component, then all the blocks in a segment of blocks on the second component, and so forth.For sequential I/O operations on a concatenation volume, Solaris Volume Manager reads all the blocks on the first component, then all the blocks of the second component, and so forth. On both a concatenation volume and a stripe volume, all I/O operations occurs in parallel.You can use a RAID-0 volume that contains a single slice for any file system. You can use a RAID-0 volume that contains multiple components for any file system except the following: root (/) /usr swap /var /opt Any file system that is accessed during an operating system upgrade or installation When you mirror root (/), /usr, swap, /var, or /opt, you put the file system into a one-way concatenation or stripe (a concatenation of a single slice) that acts as a submirror. This one-way concatenation is mirrored by another submirror, which must also be a concatenation. A RAID-0 (stripe) volume is a volume that arranges data across one or more components. Striping alternates equally-sized segments of data across two or more components, forming one logical storage unit. These segments are interleaved round-robin so that the combined space is made alternately from each component, in effect, shuffled like a deck of cards. To increase the capacity of a stripe volume , you need to build a concatenated stripe volume. See RAID-0 (Concatenated Stripe) Volume. Striping enables multiple controllers to access data at the same time, which is also called parallel access. Parallel access can increase I/O throughput because all disks in the volume are busy most of the time servicing I/O requests. An existing file system cannot be converted directly to a stripe. To place an existing file system on a stripe volume , you must back up the file system, create the volume, then restore the file system to the stripe volume.An interlace is the size, in Kbytes, Mbytes, or blocks, of the logical data segments on a stripe volume. Depending on the application, different interlace values can increase performance for your configuration. The performance increase comes from having several disk arms managing I/O requests. When the I/O request is larger than the interlace size, you might get better performance.RAID-5 volumes also use an interlace value. See Overview of RAID-5 Volumes for more information. When you create a stripe volume, you can set the interlace value or use the Solaris Volume Manager default interlace value of 512 Kbytes. Once you have created the stripe volume, you cannot change the interlace value. However, you could back up the data on it, delete the stripe volume, create a new stripe volume with a new interlace value, and then restore the data. Figure 8–1 shows a stripe volume that is built from three components (slices). It also illustrates how data is written onto the volume components according to the interlace size and using the round-robin technique.When Solaris Volume Manager writes data onto the components of a stripe volume, it writes data blocks of the interlace width to Disk A (interlace 1), Disk B (interlace 2), and Disk C (interlace 3). Solaris Volume Manager then repeats the pattern writing to Disk A (interlace 4), Disk B (interlace 5), Disk C (interlace 6), and so forth.The interlace value sets the size of each time data is written to a slice. The total capacity of the stripe volume equals the number of components multiplied by the size of the smallest component. (If each slice in the following example were 2 Gbytes, the volume would equal 6 Gbytes.)

Diagram shows physical slices, and how interlace widths are taken from each slice in turn and presented as a single logical volume.

A RAID–0 (concatenation) volume is a volume whose data is organized serially and adjacently across components, forming one logical storage unit.Use a concatenation volume to get more storage capacity by combining the capacities of several components. You can add more components to the concatenation volume as the demand for storage grows.A concatenation volume enables you to dynamically expand storage capacity and file system sizes online. A concatenation volume allows you to add components even if the other components are currently active. A concatenation volume can also expand any active and mounted UFS file system without having to bring down the system. In general, the total capacity of a concatenation volume is equal to the total size of all the components in the volume. If a concatenation volume contains a slice with a state database replica, the total capacity of the volume is the sum of the components minus the space that is reserved for the replica.You can also create a concatenation volume from a single component. Later, when you need more storage, you can add more components to the volume.You must use a concatenation volume to encapsulate root (/), swap, /usr, /opt, or /var when mirroring these file systems. Figure 8–2 illustrates a concatenation volume that is built from three components (slices). It also illustrates how data is written onto the volume components according to the interlace size and onto each slice sequentially.The data blocks are written sequentially across the components, beginning with Slice A. You can envision Slice A as containing logical data blocks 1 through 4. Disk B would contain logical data blocks 5 through 8. Drive C would contain logical data blocks 9 through 12. The total capacity of volume would be the combined capacities of the three slices. If each slice were 2 Gbytes, the volume would have an overall capacity of 6 Gbytes.

Diagram shows how interlace widths are taken from each slice (all widths from one slice, then all from the next) and presented as a single volume.

A RAID–0 (concatenated stripe) volume is a stripe that has been expanded by adding additional components (stripes). To set the interlace value for a concatenated stripe volume, at the stripe level, use either the Enhanced Storage tool within the Solaris Management Console, or the metattach i command. Each stripe within the concatenated stripe volume can have its own interlace value. When you create a concatenated stripe volume from scratch, if you do not specify an interlace value for a particular stripe, it inherits the interlace value from the previous stripe added to the volume.Figure 8–3 illustrates a concatenated stripe volume that is a concatenation of three stripes.The first stripe consists of three slices, Slice A through C, with an interlace value of 512 Kbytes. The second stripe consists of two slices, Slice D and E, and uses an interlace value of 1024 Kbytes32 Kbytes. The last stripe consists of a two slices, Slice F and G. Because no interlace value is specified for the third stripe, it inherits the value from the stripe that was added before it, which in this case is 1024 Kbytes32 Kbytes. Sequential data blocks are added to the first stripe until that stripe has no more space. Data blocks are then added to the second stripe. When this stripe has no more space, data blocks are added to the third stripe. Within each stripe, the data blocks are interleaved according to the specified interlace value.

Diagram shows how several stripes are concatenated together to present a single larger logical RAID-0 volume.

When you are working with RAID-0 volumes, consider the following:Use components that are each on different controllers to increase the number of simultaneous reads and writes that can be performed. Do not create a stripe from an existing file system or data. Doing so will destroy data. Instead, use a concatenation. (You can create a stripe from existing data, but you must dump and restore the data to the volume.) Use disk components of the same size for stripes. Striping components of different sizes results in wasted disk space. Set up a stripe's interlace value to better match the I/O requests made by the system or applications. Because a stripe or concatenation does not contain replicated data, when such a volume has a component failure, you must replace the component, recreate the stripe or concatenation, and restore data from a backup. When you recreate a stripe or concatenation, use a replacement component that has at least the same size as the failed component. Concatenation uses less CPU cycles than striping and performs well for small random I/O and for even I/O distribution. When possible, distribute the components of a stripe or concatenation across different controllers and busses. Using stripes that are each on different controllers increases the number of simultaneous reads and writes that can be performed. If a stripe is defined on a failing controller and another controller is available on the system, you can “move” the stripe to the new controller by moving the disks to the controller and redefining the stripe. Number of stripes: Another way of looking at striping is to first determine the performance requirements. For example, you might need 10.4 Mbytes/sec performance for a selected application, and each disk might deliver approximately 4 Mbyte/sec. Based on this formula, then determine how many disk spindles you need to stripe across:10.4 Mbyte/sec / 4 Mbyte/sec = 2.6Therefore, you need three disks capable of performing I/O operations in parallel. RAID-0 volumes provide the fundamental building blocks for creating more complex storage configurations or for building mirrors. The following example, drawing on the scenario explained in Chapter 5, Configuring and Using Solaris Volume Manager (Scenario), describes how RAID-0 volumes can provide larger storage spaces and allow you to construct a mirror of existing file systems, including root (/). The sample system in the scenario has a collection of relatively small (9 Gbyte) disks, but specific applications would likely require larger storage spaces. To create larger spaces (and improve performance), you can create a stripe that spans multiple disks. For example, each one of the following disks, c1t1d0, c1t2d0, c1t3d0, c2t1d0, c2t2d0, and c2t3d0, could be formatted with a slice 0 that spans the entire disk. Then, a stripe including all three of the disks from one controller could provide approximately 27 Gbytes of storage and allow faster access. The second stripe, from the second controller, could be used for redundancy, as described in Chapter 11, RAID-1 (Mirror) Volumes (Tasks) and specifically in the Scenario—RAID-1 Volumes (Mirrors).