Applications, Such As NetBackup, That Traverse The Filesystem Of An Exalogic Compute Node Cause An Unexpected Panic From The megaraid_sas Kernel Module
Last updated on AUGUST 30, 2013
Applies to:Oracle Exalogic Elastic Cloud Software - Version 220.127.116.11.1 and later
Information in this document applies to any platform.
You have an Exalogic system running version 18.104.22.168.1 of the Exalogic Elastic Cloud Software (EECS) in a physical configuration. You have an application that iterates through the local file system, possibly evaluating the last modification timestamp of files or copying data as part of a backup related task, possibly creating a backup of files using a backup related application such as NetBackup or other similar tool. At some point during the application's activity it may access a special file (e.g. /sys/class/scsi_host/host0/max_sectors) after which a kernel panic occurs with the stack trace below and forces the compute node to reboot.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms