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:Solaris Operating System - Version 10 3/05 and later
Information in this document applies to any platform.
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:
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.
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