updating a corrupt error log prevents draining of deferred spacemap on export leading to a server panic
(Doc ID 2423376.1)
Last updated on JULY 07, 2023
Applies to:
Solaris Operating System - Version 11 to 11.3 [Release 11.0]Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
Symptoms
updating a corrupt error log prevents draining of deferred spacemap on export
This can lead to a panic when attempting next boot or next export. The panic string and stack will be similar to this:
panic[cpu63]/thread=30090093900: assertion failed: sm->sm_space == 0 (0x6400 == 0x0), file: ../../common/fs/zfs/space_map.c, line: 60
genunix:assfail3
zfs:space_map_destroy
zfs:metaslab_fini
zfs:vdev_metaslab_fini
zfs:vdev_free
zfs:vdev_free
zfs:spa_unload
zfs:spa_export_common
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 |