Start a Conversation

Unsolved

This post is more than 5 years old

2995

March 5th, 2014 06:00

can't create vdev on dmx4

Hi,

I have DMX4-24/5773. Few days ago I've created few vdevs, but today I need much more of them ( ~250 ).

I've tryed with count 220, 10 and 5, but get error below:

$ symconfigure -sid xxxx -cmd "create dev count=5, size=29491 cyl,  emulation=fba, config=vdev;" -v comm

Execute a symconfigure operation for symmetrix '000290103837' (y/ ) ? y

A Configuration Change operation is in progress. Please wait...

    Establishing a configuration change session...............Established.

    Processing symmetrix 000xxxxxxxxxx

    {

      create dev count=5, size=29491 cyl, emulation=FBA, config=VDEV,

        mvs_ssid=0;

    }

    Performing Access checks..................................Allowed.

    Checking Device Reservations..............................Allowed.

    Submitting configuration changes..........................Submitted

    Validating configuration changes..........................Validated.

      New symdevs: 09F7:09FB

    Initiating PREPARE of configuration changes...............Prepared.

    Initiating COMMIT of configuration changes................Queued.

    COMMIT requesting required resources......................No Progress.

    Error occurred while Committing

    The configuration change COMMIT failed. Please see the SYMAPI log file for more information

    Closing configuration change request......................Closed.

    Terminating the configuration change session..............Done.

The configuration change session has failed.

In symapi log we have few minutes repeating:

1 EMC:SYMCONFIGURE      cfgSwAbortSession Retrying...

Can anyone help?

we have some snap sessions already active, so vdevs can be created...

Regards

1 Rookie

 • 

52 Posts

March 5th, 2014 10:00

There can be a multitude of reasons for the configuration change failure.  The API log will only provide part of the answer, please open a Service Request with the Symmetrix Support Center for further investigation.

Regards,

Chris

March 6th, 2014 01:00

I guess its a script which is stuck. PSE will need to recover it by dialing in to the box.

24 Posts

March 6th, 2014 03:00

I know that command is ok, I run it few weeks ago, when I created some vdevs.

Is there some commands to see "system readynes" or something?

110 Posts

March 6th, 2014 03:00

There is nothing wrong in the command, please review the symapi logs, and open a case with EMC.

I have tested your commands, and i got 5 new vdev's. There may be some scripts malfunctioning or something else... its better to check with PSE.

110 Posts

March 6th, 2014 03:00


The prepare does't for you, it does verifies the array readiness. The commit does include the prepare and fails, if the array is not ready. Most of the time the preview will pass, but it will fail at commit.

symconfigure -sid xxxx -cmd "create dev count=5, size=29491 cyl,  emulation=fba, config=vdev;" -v prepare

24 Posts

March 6th, 2014 03:00

no locks at all.

$ symcfg list -lock

               S Y M M E T R I X      L O C K S

                              Lock       Lock    Lock                Time

    SymmID       Attachment   Status     Number  Usage               Held (Sec)

    0002xxxxxxxxx Local        N/A        N/A     N/A                 N/A

$ symcfg list -lockn all

               S Y M M E T R I X      L O C K S

                              Lock       Lock    Lock                Time

    SymmID       Attachment   Status     Number  Usage               Held (Sec)

    000xxxxxxxx Local        N/A        N/A     N/A                 N/A

Is it possible that there is to less cache on sym box:

$ symcfg list

                                S Y M M E T R I X

                                       Mcode    Cache      Num Phys  Num Symm

    SymmID       Attachment  Model     Version  Size (MB)  Devices   Devices

    000xxxxxxxx Local       DMX4-24   5773       49152       224      2551

24 Posts

March 6th, 2014 03:00

preview and prepare end successfully, but commit don't

108 Posts

March 6th, 2014 03:00

You've tried a symcfg discover first, also you can see if you have any lock in symmetrix:

symcfg list -lock

symcfg list -lockn all

24 Posts

March 6th, 2014 04:00

local emc partner was aweare of this, but this isn't our production storage any more and this is low priority.

9 Legend

 • 

20.4K Posts

March 6th, 2014 04:00

could be a hot spare process running, until it finishes can't do any changes. I get that often on our DMX4.

24 Posts

March 6th, 2014 04:00

$ symdev list -lock

Symmetrix ID: 000xxxxxxxxxx

No devices are locked

24 Posts

March 6th, 2014 04:00

but ecc basicaly use solution enabler to "talk" with symm.

Maybe to remove /var/symapi/db/symapi_db.bin and do the symcfg disc again?

108 Posts

March 6th, 2014 04:00

You can to rename symapi_ db for symapi_db.old.

108 Posts

March 6th, 2014 04:00

For the answer of dynamox, you can check:

symdisk -sid xxx list -failed -v

9 Legend

 • 

20.4K Posts

March 6th, 2014 04:00

symdisk does not always show failed drives. I have seen many instances where ECC will report drive failure and hot spare kicking in, yet symdisk says everything is ok.

No Events found!

Top