My Oracle Support Banner

Unable to Present a New LUN from a Storage Array to an OVS Server with " Sending notification : {STORAGE} [CHANGE_DM_SD] (dm-XX) XX (failed:XX:XX) (Doc ID 2082677.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle VM - Version 3.0.1 and later
Information in this document applies to any platform.

Symptoms

 On Oracle VM, all 3.X.X releases, after some changes on a SAN, it is no longer possible to present newly created LUNs to Oracle VM Servers.

Any job attempting to present a new LUN to a VM Server gets aborted, and in the details of the jobs in the VM Manager GUI :

begin()
com.oracle.odof.exception.LockException: DGC (93) is locked. job info: time:1421759145034 name:ServerRefreshStorageLayerDbImpl_1421759145033 description:ServerRefreshStorageLayerDbImpl: Refresh Storage Layer for Server: ovs1, Storage array: Unmanaged FibreChannel Storage Array
Wed Jan 21 00:15:08 IST 2015 [@OvmAdmin]
at com.oracle.odof.core.storage.Transaction.acquireAccess(Transaction.java:220)
at com.oracle.odof.core.storage.Transaction.acquireVessel(Transaction.java:330)
at com.oracle.odof.core.storage.Transaction.invokeMethod(Transaction.java:837)
at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:92)
at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
at com.oracle.odof.core.storage.Transaction.processCommand(Transaction.java:601)
at com.oracle.odof.core.TransactionManager.processTransactionWork(TransactionManager.java:651)
at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:756)
at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:467)
at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:525)
at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
at java.lang.Thread.run(Thread.java:662)

Job Aborted from server, cleaning up client.

 The following kind of error messages can be witnessed on the VM Server that should get presented with the new LUN in the /var/log/ovs-agent.log log file :

[2015-01-19 21:00:35 18116] INFO (notificationserver:139) Sending notification: Jan 19 21:00:35 {STORAGE} [CHANGE_DM_SD] (dm-17) 36006016021b02200f06740620698e211-0:0:0:20 (active:0x5006016941e01dac:36006016021b02200f06740620698e211)
[2015-01-19 21:00:35 18116] INFO (notificationserver:139) Sending notification: Jan 19 21:00:35 {STORAGE} [CHANGE_DM_SD] (dm-17) 36006016021b02200f06740620698e211-0:0:1:20 (active:0x5006016041e01dac:36006016021b02200f06740620698e211)
[2015-01-19 21:00:36 18116] INFO (notificationserver:139) Sending notification: Jan 19 21:00:36 {STORAGE} [CHANGE_DM_SD] (dm-17) 36006016021b02200f06740620698e211-1:0:1:20 (failed:0x5006016141e01dac:36006016021b02200f06740620698e211)
[2015-01-19 21:00:36 18116] INFO (notificationserver:139) Sending notification: Jan 19 21:00:36 {STORAGE} [CHANGE_DM_SD] (dm-17) 36006016021b02200f06740620698e211-0:0:1:20 (failed:0x5006016041e01dac:36006016021b02200f06740620698e211)

 The following kind of multipathd errors may also be witnessed in the /var/log/messages on the VM server that should have been presented with the new LUN :

Jan 20 18:02:50 ovs1 multipathd: 360060160cdb02800862fe61aaf9fe411: sdcj - emc_clariion_checker: Logical Unit WWN has changed!
Jan 20 18:02:50 ovs1 multipathd: 360060160cdb02800862fe61aaf9fe411: sddq - emc_clariion_checker: Logical Unit WWN has changed!
Jan 20 18:02:55 ovs1 multipathd: 360060160cdb02800862fe61aaf9fe411: sdu - emc_clariion_checker: Logical Unit WWN has changed!
Jan 20 18:02:55 ovs1 multipathd: 360060160cdb02800862fe61aaf9fe411: sdbb - emc_clariion_checker: Logical Unit WWN has changed!
Jan 20 18:02:55 ovs1 multipathd: 360060160cdb02800862fe61aaf9fe411: sdcj - emc_clariion_checker: Logical Unit WWN has changed!
Jan 20 18:02:55 ovs1 multipathd: 360060160cdb02800862fe61aaf9fe411: sddq - emc_clariion_checker: Logical Unit WWN has changed!
Jan 20 18:03:00 ovs1 multipathd: 360060160cdb02800862fe61aaf9fe411: sdu - emc_clariion_checker: Logical Unit WWN has changed!
Jan 20 18:03:00 ovs1 multipathd: 360060160cdb02800862fe61aaf9fe411: sdbb - emc_clariion_checker: Logical Unit WWN has changed!
Jan 20 18:03:00 ovs1 multipathd: 360060160cdb02800862fe61aaf9fe411: sdcj - emc_clariion_checker: Logical Unit WWN has changed!
Jan 20 18:03:00 ovs1 multipathd: 360060160cdb02800862fe61aaf9fe411: sddq - emc_clariion_checker: Logical Unit WWN has changed!
Jan 20 18:03:05 ovs1 multipathd: 360060160cdb02800862fe61aaf9fe411: sdu - emc_clariion_checker: Logical Unit WWN has changed!
Jan 20 18:03:05 ovs1 multipathd: 360060160cdb02800862fe61aaf9fe411: sdbb - emc_clariion_checker: Logical Unit WWN has changed!

 Depending on the exact situation, the Storage server may also be locked in the VM Graphical User Interface, denoted by a lock icon next to the storage server's icon in the left pane.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.