 |
 |  |
 |
 | NOTE: VxVM supports this feature for private disk groups,
but not for shareable disk groups in a cluster environment. You may need an additional license to use this feature. |
 |
 |  |
 |
You can create RAID-5
volumes by using either the vxassist command (recommended) or the
vxmake command. Both approaches are described below.
 |
 |  |
 |
 | NOTE: A RAID-5 volume requires space to be available on at
least as many disks in the disk group as the number of columns in
the volume. Additional disks may be required for any RAID-5 logs
that are created. |
 |
 |  |
 |
A RAID-5 volume contains a RAID-5 data plex that consists
of three or more subdisks located on three or more physical disks.
Only one RAID-5 data plex can exist per volume. A RAID-5 volume
can also contain one or more RAID-5 log plexes, which are used to
log information about data and parity being written to the volume.
For more information on RAID-5 volumes, see “RAID-5
(Striping with Parity)”.
 |
 |  |
 |
 | CAUTION: Do not create a RAID-5 volume with more than 8 columns
because the volume will be unrecoverable in the event of the failure
of more than one disk. |
 |
 |  |
 |
To create a RAID-5 volume, use the following command:
# vxassist [-b] [-g diskgroup] make volume length layout=raid5 \[ncol=number_columns] [stripewidth=size] [nlog=number] \[loglen=log_length]
For
example, to create the RAID-5 volume volraid together with 2 RAID-5
logs, use the following command:
# vxassist -b make volraid 10g layout=raid5 nlog=2
This creates a RAID-5 volume with the default stripe unit
size on the default number of disks. It also creates two RAID-5
logs rather than the default of one log.
 |
 |  |
 |
 | NOTE: If you require RAID-5 logs, you must use the logdisk
attribute to specify the disks to be used for the log plexes. |
 |
 |  |
 |
RAID-5 logs can be concatenated or striped plexes, and each
RAID-5 log associated with a RAID-5 volume has a complete copy of
the logging information for the volume. To support concurrent access
to the RAID-5 array, the log should be several times the stripe
size of the RAID-5 plex.
It is suggested that you configure a minimum of two RAID-5
log plexes for each RAID-5 volume. These log plexes should be located
on different disks. Having two RAID-5 log plexes for each RAID-5
volume protects against the loss of logging information due to the
failure of a single disk.
If you use ordered
allocation when creating a RAID-5 volume on specified storage, you
must use the logdisk
attribute to specify on which disks the RAID-5 log plexes should
be created. Use the following form of the vxassist command to specify
the disks from which space for the logs is to be allocated:
# vxassist [-b] [-g diskgroup] -o ordered make volume length \ layout=raid5 [ncol=number_columns] [nlog=number] \ [loglen=log_length] logdisk=disk[,disk,...] storage_attributes
For example, the following command creates a 3-column RAID-5
volume with the default stripe unit size on disks disk04, disk05
and disk06. It also creates two RAID-5 logs on disks disk07 and
disk08.
# vxassist -b make volraid 10g layout=raid5 ncol=3 nlog=2 \ logdisk=disk07,disk08 disk04 disk05 disk06
 |
 |  |
 |
 | NOTE: The number of logs must equal the number of disks specified
to logdisk. |
 |
 |  |
 |
For more information about ordered allocation, see “Specifying
Ordered Allocation of Storage to Volumes” and the vxassist(1M) manual
page.
If you need to add more logs to a RAID-5 volume at a later
date, follow the procedure described in “Adding
a RAID-5 Log”.