Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

1097

September 26th, 2014 10:00

vdev 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.

9 Legend

 • 

20.4K Posts

September 26th, 2014 11:00

that is correct, VDEVs must be build identically to source devices.

9 Legend

 • 

20.4K Posts

September 26th, 2014 11:00

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)

1 Rookie

 • 

89 Posts

September 26th, 2014 11:00

we're on 76 code and se76. thanks. I'll give that a try.

1 Rookie

 • 

89 Posts

September 26th, 2014 11:00

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.

1 Rookie

 • 

89 Posts

September 26th, 2014 11:00

Thanks Dynamox.

I figured as much but it would save me time if i could use a std size., so I asked.

You rock!

9 Legend

 • 

20.4K Posts

September 26th, 2014 12:00

what kind of device is 0315 ?

1 Rookie

 • 

89 Posts

September 26th, 2014 12:00

0315 is a concatenated tdev R2.

9 Legend

 • 

20.4K Posts

September 26th, 2014 12:00

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.

9 Legend

 • 

20.4K Posts

September 26th, 2014 12:00

yep, if you were building hundreds of VDEVs that would make sense.

1 Rookie

 • 

89 Posts

September 26th, 2014 12:00

all our devices are created with the dyn_rdf attribute set.

Oh well. Thanks, that is still a great cli feature add to know. I could work around it by creating a 'dummy' meta to use as the copy device, though.

No Events found!

Top