Solved!
Go to Solutionvdev sizing
I haven't been able to find an answer to this.
I need to create vdev devices and pair them with R2 devices. The R2 devices are tdev meta's. In creating the vdev devices, do they have to be the same size/geometry as the R2 tdev device(s)?
Ie: if the R2 is 960GB (4*240GB), do I create 4 vdev devices at 240GB and create a meta from them and then use that meta vdev to pair to the R2?
Thanks.
Jim,
if you are on the latest symcli use this command to build new VDEVs
symconfigure -sid 123 -cmd "configure 6 devices copying dev 188A overriding CONFIG=VDEV;" commit
this will build 6 VDEVs that will match 188A configuration (striped meta, meta member size ..etc)
it failed on the VDEV config, apparently.
>symconfigure -sid 96 -cmd "configure 2 devices copying dev 0315 overriding CONFIG=VDEV;" preview -nop
A Configuration Change operation is in progress. Please wait...
Establishing a configuration change session...............Established.
Processing symmetrix 000192606096
Performing Access checks..................................Allowed.
Checking Device Reservations..............................Allowed.
Validating configuration changes..........................Failed.
Error occurred while Validating
Cannot use the device for this function because it is a Virtual Device
Closing configuration change request......................Closed.
Terminating the configuration change session..............Done.
The configuration change session has failed.
ahh..bummer. Do you have a non-rdf device of the same construct ?
The 'source' device 0AAA has the dyn_rdf attribute set i.e is it an RDF1_OR_RDF2_Capable device. This attribute will prevent Solutions Enabler from creating new vdevs. Customer must specify a different 'source' device that is not RDF1_OR_RDF2_Capable.
dynamox
11 Legend
•
20419 Posts
•
87439 Points
500
0
Posted September 26th, 2014 11:00
that is correct, VDEVs must be build identically to source devices.