Controller Object Commands
www.3ware.com
58
v0=
n
or
vol=
a:b:c:d
may be used to divide the unit up into multiple volumes.
v0=
n
can be used if you only want two volumes, in which case
v0=
n
is used
to define the size of the first volume, and the second volume will use the
remaining space. One way in which this can be useful is if you want to create
a special volume to function as a boot volume, with a separate volume for
data.
vol=
a:b:c:d
can be used to specify sizes for up to four volumes.
The value(s) should be positive integer(s) in units of gigabytes (GB), with a
maximum of 32 TB. If you specify a size that exceeds the size of the unit, the
volume will be left “uncarved.”
Both
v0=
n
or
vol=
a:b:c:d
work in conjunction with auto-carving, if that
feature is enabled. When auto-carving is used,
v0=
n
and
vol=
a:b:c:d
are
used to specify the size of the first few volumes, after which the auto-carve
size is used for additional volumes. (For more about auto-carving, see “/cx set
autocarve=on|off” on page 70 and “/cx set carvesize=[1024..32768]” on
page 71.)
Example of RAID 5 unit created with first volume set to 10 GB:
//localhost> /c0 add type=raid5 disk=2-5 v0=10
Creating new unit on Controller /c0 ... Done. The new unit is /
c0/u0.
Setting write cache=ON for the new unit ... Done.
Setting default Command Queuing Policy for unit /c0/u0 to [on]
... Done.
After the unit creation, a subsequent
show
command for the unit shows the
the volume size(s):
//localhost> /c0/u0 show
Unit UnitType Status %RCmpl %V/I/M VPort Stripe Size(GB)
--------------------------------------------------------------
u0 RAID-5 OK - - - 64K 1117.56
u0-0 DISK OK - - p2 - 372.519
u0-1 DISK OK - - p3 - 372.519
u0-2 DISK OK - - p4 - 372.519
u0-3 DISK OK - - p5 - 372.519
u0/v0 Volume - - - - - 10
u0/v1 Volume - - - - - 1107.56
Notes:
Once the
rapidrecovery
policy has been disabled for a unit, it cannot be
changed again. Disabling this policy is required if you want to move a unit to a
controller that does not have the 9.5.1 firmware.
There is some system overhead from setting rapidrecovery to
all.
If you have a
BBU, you can set rapid recovery to
rebuild,
as a BBU provides protection against
data loss in the event of an unclean shutdown.
This attribute is only for redundant units created on controller models 9650SE and
9690SA, with the 9.5.1 firmware or later.
