ViPR Controller:  Failed Create block volume - Error 12000: Operation failed due to the following error: Smis job failed: string ErrorDescription = "The operation failed because another process has the device reservation exclusive lock on the Symmetrix".

           

   Article Number:     502611                                   Article Version: 4     Article Type:    Break Fix 
   

 


Product:

 

ViPR Controller

 

Issue:

 

 

   

      When Catalog Service "Create Block Volume for a Host" is submitted, the Order fails on Step "Add Volumes To Export" with the following Error:     
     
      com.emc.vipr.client.exceptions.ServiceErrorException: Error 12000: Operation failed due to the following error: Smis job failed: string ErrorDescription = "The operation failed because another process has the device reservation exclusive lock on the Symmetrix";     
          at com.emc.vipr.client.core.impl.TaskUtil.checkForError(TaskUtil.java:84)     
          at com.emc.vipr.client.Task.waitFor(Task.java:141)     
          at com.emc.sa.service.vipr.tasks.LongRunningTask.executeTask(LongRunningTask.java:35)     
          at com.emc.sa.service.vipr.tasks.LongRunningTask.executeTask(LongRunningTask.java:9)     
          at com.emc.sa.engine.ExecutionUtils.execute(ExecutionUtils.java:80)     
          at com.emc.sa.engine.ExecutionUtils.execute(ExecutionUtils.java:71)     
          at com.emc.sa.service.vipr.ViPRExecutionUtils.execute(ViPRExecutionUtils.java:41)     
          at com.emc.sa.service.vipr.block.BlockStorageUtils.addVolumesToExport(BlockStorageUtils.java:347)     
          at com.emc.sa.service.vipr.block.CreateBlockVolumeForHostHelper.exportVolumes(CreateBlockVolumeForHostHelper.java:76)     
          at com.emc.sa.service.vipr.block.CreateBlockStorageForHostService.execute(CreateBlockStorageForHostService.java:53)     
          at com.emc.sa.engine.ExecutionEngineImpl.execute(ExecutionEngineImpl.java:190)     
          at com.emc.sa.engine.ExecutionEngineImpl.runService(ExecutionEngineImpl.java:128)     
          at com.emc.sa.engine.ExecutionEngineImpl.executeOrder(ExecutionEngineImpl.java:72)     
          at com.emc.sa.engine.ExecutionEngineDispatcher.processOrder(ExecutionEngineDispatcher.java:50)     
          at com.emc.sa.engine.ExecutionEngineDispatcher$Consumer.consumeItem(ExecutionEngineDispatcher.java:91)     
          at com.emc.sa.engine.ExecutionEngineDispatcher$Consumer.consumeItem(ExecutionEngineDispatcher.java:85)     
          at com.emc.storageos.coordinator.client.service.impl.DistributedQueueConsumer$1.run(DistributedQueueConsumer.java:80)     
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)     
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)     
          at java.lang.Thread.run(Thread.java:745)     
          

                                                             

 

 

Cause:

 

 

   

      ​-The operation failed because another process has the device reservation exclusive lock on the Symmetrix device being used in the mentioned service.     
          

                                                             

 

 

Resolution:

 

 

   

      To Resolve this issue the lock needs to be released.     
     
      Steps:   

   

      1-Log into the SMIs Provider Host connected to the Array inquestion.     
      2-From Solutions Enabler SYMCLI Run the following command : symcfg -sid <symmid> -lockn all list     
      3-This will display all the locks list. Example:   

   

      symcfg -sid <symmid> -lockn all list returns:   

   
     

        Symmetrix ID: 000000000000     

     

                       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)
     

     

            000000000000  Local        Locked    242     Device Reservations   822     

   
   

      4-The locks can be released using the following command : symcfg -sid <symmid> -lockn 242 release , Lock number "242" can be different, substitute accordingly in the command to release.     
      5-Retry/Resubmit the Order from ViPR Controller.   

                                                             

 

 

Notes:

 

 

   

      Reservations are only active for the duration of the configuration activity. During this time, no other users are allowed to make configuration changes to the reserved device. If a problem occurs during configuration and a device reservation becomes an "orphaned lock," you can release that lock using the Release Device Reservation dialog box.     
      Often a lock 242 may be a config lock remaining from a failed script or activity that has completed, so if there are no scripts running, it may be removed.     
     
      The Following KB Article is from Symmetrix and addresses "Locks" in general:     
      https://support.emc.com/kb/328167       
        https://support.emc.com/kb/
329673     
      https://support.emc.com/kb/347718     
     
      -Other KBs can also be found in the kb database.