CLI Guide

Table 333. Creating Virtual Disks (continued)
Mandatory Options
and Arguments
Optional Parameters Valid Parameters
Arguments
Description
○ RAID 10: 100 MB
NOTE: If this option is not provided,
RAIDCFG determines the maximum virtual
disk size and creates it.
-ctrl -ac=cvd -
c=id -ad=
ch:targ,ch:targ,
... [or
ch:targ:encl,...]
or
controller
action=
createvdisk
controllerid= id
adisk=
channel:target:
lun,...
channel:target:
lun,... [or
channel:target:
enclosure,...]
-vdpi or
vdiskprotectionin
fo
0,1
Creates a virtual disk with the T10 Protection
Information (PI) feature enabled.
NOTE: This option is supported only on PERC
9 controllers.
Example:
A:>raidcfg -ctrl -ac=cvd
-c=2
-ad=1:4,1:8 -vdpi=1
RAIDCFG Command successful!
-wp or
writepolicy
wb, wt, wc, nwc, fwb
Sets the write policy for the virtual disk. The valid
arguments are:
● wb — Write-Back caching sets the controller
to send a write-request completion signal as
soon as the data is in the controller cache but
has not yet been written to disk.
● wt — Write-Through caching sets the
controller to send a write-request completion
signal only after the data is written to the
disk.
NOTE: The wb and wt options are supported
on the following RAID controllers only:
● PERC 5/E Adapter, PERC 5/I Integrated,
PERC 5/i Adapter
● PERC 6/i Integrated, PERC 6/i Adapter,
PERC 6/E Adapter
● PERC 7, PERC 8, and PERC 9
●
wc — Write-Caching sets the controller to
send a write-request completion signal only
after the data is written to the disk.
● nwc — No-Write-Caching specifies that the
controller does not send a write-request
completion signal after the data is written to
the disk.
● fwb — Force write-back caching, enables the
write cache regardless of whether the
controller has a battery. If the controller does
not have a battery and force write-back
caching is used, data loss may occur in the
event of a power failure
RAIDCFG
175