The following
table displays how to specify the
omconfig storage controller
action=createvdisk
parameters:
Table 1. Parameters And
Types
Parameters |
Type |
controller=id |
Required |
raid=<c | r0 | r1 | r1c | r5 | r6 | r10 | r50 | r60> |
Required |
size=<number | max | min> |
Required |
pdisk=<connector:targetID,connector:targetID,.....> |
Required |
[stripesize=<2k b| 4kb | 8kb | 16kb | 32kb | 64kb | 128kb>] |
Optional |
[cachepolicy=<d | c>] |
Optional |
[readpolicy=<ra | nra | ara | rc | nrc>] |
Optional |
[writepolicy=<wb | wt | wc | nwc | fwb>] |
Optional |
[name=<string>] |
Optional |
[spanlength=<n>] parameter |
Optional |
controller=id parameter
Specify
the controller ID as reported by the omreport storage controller command.
For example,
controller=2
raid=<c
| r0 | r1 | r1c | r5 | r6 | r10 | r50 | r60>
Use the
raid=<c | r0 | r1 | r1c | r5 | r6 | r10 | r50 | r60> parameter
to specify concatenation or a RAID level for a virtual disk. Different
controllers support different RAID levels. For more information about
RAID levels a controller supports and for general information about
RAID levels and concatenation, see the
Dell OpenManage Online Help. The following table displays how to specify the
raid=n parameter for each RAID level and concatenation.
Table 2. Raid Level And
Concatenation
RAID Level or Concatenation |
raid=n Parameter Specification |
RAID-0 |
raid=r0 |
RAID-1 |
raid=r1 |
RAID-5 |
raid=r5 |
RAID-6 |
raid=r6 |
RAID-10 |
raid=r10 |
RAID-50 |
raid=r50 |
RAID-60 |
raid=r60 |
RAID-1-concatenated |
raid=r1c |
Concatenation |
raid=c |
size=<number | max | min>
The following table displays how to specify the size=<number
| max | min>
Table 3. Size Parameter
size=<number | max | min> Parameter Specification |
Description |
size=<n> |
Use this specification to indicate a specific size for the
virtual disk. The virtual disk size is specified in b (bytes), m (megabytes),
or g (gigabytes). For example,
size=500m indicates
that the virtual disk is 500 MB.
|
size=max |
To create a virtual disk that is the maximum size possible,
specify
size=max. When creating a RAID-50 virtual
disk, this parameter is specified as
size=max.
|
size=min |
To create a virtual disk that is the minimum size possible,
specify
size=min.
|
PDISKID=<connector:enclosureID:targetID
| connector:targetID>
Use this parameter to specify
the physical disks to be included in the virtual disk.
When
reconfiguring a virtual disk, you must specify all physical disks
to include in the reconfigured virtual disk. The physical disk specification
applies to physical disks in the original virtual disk and continues
in the reconfigured virtual disk and to any new physical disks being
added to the reconfigured virtual disk. Some controllers allow you
to remove a physical disk from a virtual disk. In this case, do not
specify to remove the physical disk.
The
pdisk=<PDISKID> parameter indicates a physical disk by specifying either
connector:enclosureID:targetID or connector:targetID.
stripesize=<2kb | 4kb | 8kb | 16kb | 32kb | 64kb |
128kb>
Different controllers support different stripe
sizes. For more information on stripe sizes supported for a controller,
see the
Dell OpenManage Online Help. All stripe sizes are specified
in kilobytes. For example, when specifying 128 KB as the stripe size,
type:
stripesize=128kb
cachepolicy=<d
| c>] parameter
Different controllers support different
cache policies. The following table displays how to specify the [cachepolicy=<d
| c>] parameter for each of the cache policies.
Table 4. Cache Policy
Parameters
Cache Policy |
cachepolicy=d | c Parameter Specification |
Direct I/O |
cachepolicy=d |
Cache I/O |
cachepolicy=c |
diskcachepolicy=<disabled | enabled>
Different controllers support different disk cache policies.
The following table indicates how to specify the [diskcachepolicy=<disabled
| enabled>] parameter for each of the cache policies.
Table 5. Disk Cache Policy
Parameters
Disk Cache Policy |
diskcachepolicy=disabled | enabled Parameter
Specification
|
Disabled |
diskcachepolicy=disabled |
Enabled |
diskcachepolicy=enabled |
readpolicy=ra | nra | ara | rc | nrc>
Different controllers support different read policies. The
following table displays how to specify the readpolicy=<ra | nra
| ara | rc | nrc> parameter for each of the read policies.
Table 6. Read Policy
Parameters
Read Policy |
readpolicy=ra | ara | nra | rc | nrc Parameter
Specification
|
Read ahead |
readpolicy=ra |
Adaptive read ahead |
readpolicy=ara |
No read ahead |
readpolicy=nra |
Read cache |
readpolicy=rc |
No read cache |
readpolicy=nrc |
writepolicy=<wb | wt | wc | nwc>]
Different controllers support different write policies. The
following table displays how to specify the writepolicy=<wb | wt
| wc | nwc | fwb> parameter for each of the write policies.
Table 7. Write Policy
Parameters
Write Policy |
writepolicy=wb | wt | wc | fwb | nwc Parameter
Specification
|
Write-back cache |
writepolicy=wb |
Write-through cache |
writepolicy=wt |
Write cache |
writepolicy=wc |
Force write back |
writepolicy=fwb |
No write cache |
writepolicy=nwc |