Solaris 11.3 Sammkfs Triggers BAD TRAP occurred in module "unix" due to a NULL pointer dereference - physical block size changes
Last updated on OCTOBER 24, 2017
Applies to:Solaris Operating System - Version 10 6/06 U2 and later
Information in this document applies to any platform.
This is a Solaris 11.3 x86 SRU 126.96.36.199.0 Oracle server with 8GB Oracle Qlogic FC HBAs, connected to the SAN to access a new Disk Storage array:
a standard, self "assembled" Linux box (Supermicro based) with a ZFS/Zvol exported via a QLogic FC to the SAN (FC/SCSI Stack based on SCST (Generic SCSI Target Subsystem for Linux) with T10-ALUA).
We tested this new FC SAN storage device and tried to run sammkfs on it which reproducible triggers a kernel panic:
1) 1st panic at "Jun 15 10:17:14 " (almost identical panic stack as 4th panic at "Jun 15 11:16:47" , see below)
See also: Solaris Panics with a Data Access MMU Miss in the ssd Module (Doc ID 2071994.1)
Customer have been playing around with different settings/blocksizes for the new Storage , specially with block and sector sizes, as they we want to benchmark these settings to settle down on a stable and fast set-up for the future.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms