Users Guide
[writepolicy=<wb | wt | wc | nwc | fwb>] Parameter (Optional)
Different controllers support different write policies. See "Write Policy" for more information. The following table indicates how to specify the [writepolicy=<wb|
wt| wc| nwc | fwb>] parameter for each of the write policies.
[name=<string>] Parameter (Optional)
Use this parameter to specify a name for the virtual disk. For example:
name=VirtualDisk1
[spanlength=<n>] Parameter (Required for RAID 50 and RAID 60 and optional for RAID 10)
Use this parameter to specify the number of physical disks to be included in each stripe. This parameter only applies to RAID 50 and RAID 60 virtual disks. If
you are not creating a RAID 50 or RAID 60 virtual disk, do not specify this parameter.
For example:
spanlength=3
For RAID 10 on SAS controllers with firmware version 6.1 and later, spanlength is optional. Also, you can now specify the spanlength as an even number with a
maximum of 8 spans with 32 physical disks each. For example,
omconfig storage controller action=createvdisk controller=1 raid=r10 size=min pdisk= 1:1:0,1:1:1,1:1:3,1:1:4,1:1:6,1:1:7,1:1:8,1:1:9
spanlength=4
Example Syntax
For example, you may want to create a RAID 5 virtual disk on a PERC 3/QC controller. To understand which read, write, and cache policies are supported by
this controller, you would refer to "RAID Controller Read, Write, Cache, and Disk Cache Policy". In this example, you decide to create a virtual disk with the
following read, write, and cache policy:
l Read-ahead
l Write-through caching
l Cache I/O
No read ahead
readpolicy=nra
Read cache
readpolicy=rc
No read cache
readpolicy=nrc
Write Policy
writepolicy=wb | wt | wc | nwc | fwb Parameter Specification
Write-back cache
writepolicy=wb
Write-through cache
writepolicy=wt
Write cache
writepolicy=wc
No write cache
writepolicy=nwc
Force write back
writepolicy=fwb
NOTE: The CERC SATA1.5/2s controller does not allow you to specify a virtual disk name. The virtual disk will be created with a default name.