Solaris Volume Manager (SVM): Host may panic with BAD TRAP type 31 when deleting a soft partition with metaclear (Doc ID 1377086.1)

Last updated on DECEMBER 07, 2016

Applies to:

Sun Solaris Volume Manager (SVM) - Version 11.9.0 to 11.10.0 [Release 11.0]
Solstice DiskSuite Software - Version 4.2.1 to 4.2.1 [Release 4.0]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)

Symptoms

It is possible for a system to panic when trying to remove a Solaris Volume Manager (SVM) soft partition.

If a soft partition built from a one-way mirror is in a "Needs maintenance" state and the physical disk is inaccessible, the system may panic.

The panic string below is a result of running metaclear to remove a soft partition configured on a disk that had been removed from the system:

panic[cpu1]/thread=30001f735c0: BAD TRAP: type=31 rp=2a100bc92e0 addr=308000c8ff8 mmu_fsr=0

metaclear: trap type = 0x31
addr=0x308000c8ff8
pid=207, pc=0x10e32b4, sp=0x2a100bc8b81, tstate=0x880001602, context=0x1
g1-g7: 13983bc, 0, 20000, 5c8ff80, 88, 1, 30001f735c0

000002a100bc9000 unix:die+9c (31, 2a100bc92e0, 308000c8ff8, 0, 2a100bc90c0, e25d8017)
%l0-3: 00000000c0800000 0000000000000031 0000000001000000 0000000000002000
%l4-7: 0000000000100000 0000060019fd9860 0000000000000000 000000000109d000
000002a100bc90e0 unix:trap+9e0 (2a100bc92e0, 0, 1fff, 6, 308000c8000, 1)
%l0-3: 0000000000000000 0000060019fd9860 0000000000000031 0000000000001c00
%l4-7: 0000000000000000 0000000000000001 ffffffffffffe000 0000000000000006
000002a100bc9230 unix:ktl0+48 (0, 101, ffffffffffffffff, 60011e68e98, ffffffff, ffffffffffffffff)
%l0-3: 0000000000000003 0000000000001400 0000000880001602 000000000101bd10
%l4-7: 0000000005200170 0000000005200000 0000000000000000 000002a100bc92e0
000002a100bc9380 md:md_call_strategy+5c (60011e68db8, 18cb800, ffffffff, ffffffff, ffffffff, ffffffffffffffff)
%l0-3: 0000000000000000 000006001063cbf8 0000000001907400 0000000000000000
%l4-7: 0000000002000000 0000000000000000 00000300000c9000 00000007fffffff8
000002a100bc9430 md_stripe:md_stripe_strategy+2fc (6001200d0f0, 600107a6548, 60011e68d78, 6001063cb70, 809, 1)
%l0-3: 000000000190d890 0000000000000000 0000000000000200 0000000005ac01e0
%l4-7: 00000600107a65a0 0000000000000000 0000000000000001 0000060011e68db8
000002a100bc9510 md_mirror:mirror_write_strategy+83c (6001de38f40, 1, 0, 600107a3630, 6001200d0b8, 809)
%l0-3: 000006001200d0f0 000006001070b740 0000000000000000 0000000000000004
%l4-7: 00000600107a3598 000006001058e000 0000000000000000 000000000190dd78
000002a100bc95c0 md_sp:sp_update_watermarks+270 (6001281a190, 808, 6001de38f78, 6001de38f80, 6001de38f40, 96)
%l0-3: 0000000000000100 0000000000000200 000006001281a1a8 00000600181203e8
%l4-7: 0000000000000000 0000000000000008 000006001cb00340 0000000000000000
000002a100bc9690 md_sp:sp_admin_ioctl+3b0 (e, ffbffa58, 100000, 2a100bc98c0, ff00000, 102003)
%l0-3: 0000000000000010 0000000000005681 000006001281a190 0000000000000060
%l4-7: 0000000000000040 0000000000005641 0000000000005400 0000000000100000
000002a100bc9740 md:md_admin_ioctl+130 (190c800, 19, ffbffa58, 102003, 2a100bc98c0, 5681)
%l0-3: 0000000000000010 000000000190efd8 00000300014abdc8 000000000190c800
%l4-7: 0000000000000002 00000000013b4420 000000000190efd8 00000300014abdc8
000002a100bc9810 md:mdioctl+f4 (550003ffff, 5681, ffbffa58, 102003, 60010423140, 1f)
%l0-3: 0000000000000055 000000000003ffff 0000000000000055 000000000190c000
%l4-7: 0000060011e0e308 000000000003ffff 000000000003fc00 000006001de61740


This is an example of a configuration in which this can occur.  In this example, disk c0t3d0 has been physically removed from the system:

# metastat -p
d40 -m d41 1
d41 1 1 /dev/dsk/c0t3d0s0
d501 -p d40 -o 35392 -b 40960
d500 -p d40 -o 14880 -b 20480

# metastat
< . . . . >
d40: Mirror
    Submirror 0: d41
      State: Needs maintenance

 

Changes

This appears to happen only if the disk fails completely, or is physically removed, and then the server is rebooted, and then  metaclear is run.  A reboot seems to be required for the panic to occur.

Cause

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