4.Create the RAID 0 volume.

#raidctl -c –r 0 disk1 disk2

The creation of the RAID volume is interactive, by default. For example:

#raidctl -c -r 0 c0t0d0 c0t1d0

Creating RAID volume c0t1d0 will destroy all data on member disks, proceed

(yes/no)? yes

Volume ’c0t0d0’ created

#

When you create a RAID striped volume, the other member drives (in this case, c0t1d0) disappear from the Solaris device tree.

As an alternative, you can use the –foption to force the creation if you are sure of the member disks, and sure that the data on all other member disks can be lost. For example:

#raidctl -f-c-r 0 c0t0d0 c0t1d0 Volume ’c0t0d0’ created

5.Check the status of a RAID striped volume.

# raidctl

 

 

 

RAID

Volume

RAID

RAID

Disk

Volume

Type

Status

Disk

Status

--------------------------------------------------------

c0t0d0 IS

OK

c0t0d0

OK

 

 

c0t1d0

OK

The example shows that the RAID striped volume is online and functioning.

Under RAID 0 (disk striping),there is no replication of data across drives. The data is written to the RAID volume across all member disks in a round-robin fashion. If any disk is lost, all data on the volume is lost. For this reason, RAID 0 cannot be used to ensure data integrity or availability, but can be used to increase write performance in some scenarios.

For more information about the raidctl utility, see the raidctl(1M) man page.

Chapter 3 Managing Disk Volumes 49