Solaris 11 can panic with BAD TRAP in nvlist_add_common() if the dataset is already close to the MAXNAMELEN mark
(Doc ID 2410720.1)
Last updated on JULY 07, 2023
Applies to:
Solaris Operating System - Version 11.3 to 11.3 [Release 11.0]Information in this document applies to any platform.
Symptoms
The panic string and stack will be similar to this:
panic[cpu48]/thread=1000c51e0440: BAD TRAP: type=30 rp=2a10723d1d0
addr=61001000c567a000 mmu_fsr=10009
zpool: data access exception:
MMU sfsr=10009: Data or instruction address out of range context 0x1
pid=2141, pc=0x10285e70, sp=0x2a10723ca71, tstate=0x4480001607, context=0x359
g1-g7: 12073b88, 30000769558, 30000769500, 58, b, 0, 1000c51e0440
genunix:nvlist_add_common
zfs:dsl_prop_nvlist_add_hasrecvd
zfs:dsl_prop_get_all
zfs:zfs_ioc_objset_stats_impl
zfs:zfs_ioc_objset_stats
zfs:zfs_ioc_dataset_list_next
zfs:zfsdev_ioctl
genunix:fop_ioctl
genunix:ioctl
Cause
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
| Symptoms |
| Cause |
| Solution |