Dynamically Enabling or Disabling qlc extended logging, via mdb Command qlc_elog, Can Cause the System to Panic (Doc ID 2114352.1)

Last updated on OCTOBER 05, 2022

Applies to:

Symptoms

The system can panic after enabling qlc extended logging (dynamically) via mdb.

Note. This has been observed only on one customer system with Solaris 11.2 sparc , but we think this could happen on other Solaris versions if the system IO load is high.

Using the mdb dcmd 'qlc_elog' to dynamically enable or disable qlc extended logging can result in a panic.

The panic message and stack trace will look similar to the following:

Changes

The problem is more likely to be seen when enabling or disabling qlc extended logging via mdb when

the system IO load is high. The panic can only occur if there is IO being completed by the qlc driver

at the same time that qlc extended logging is enabled or disabled dynamically.

Cause

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