Solaris 11操作系统的bug导致的RAC节点驱逐

在某些 Solaris 11 版本中，内核内存分配缓慢可能导致 RAC 节点被逐出。此问题影响 SPARC 和 x86 平台，并已在 Solaris 11.3.8.7.0 或更高版本中得到解决。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

来源于:
Solaris 11 may Experience RAC Node Evictions Due to Slowness in Kernel Memory Allocations (Doc ID 2213222.1)

APPLIES TO:

Sun Software - Generic
Solaris Operating System
Solaris x64/x86 Operating System
SPARC
x86
___________________________________________

Bug 22471289

Date of Resolved Release: 12-Dec-2016
___________________________________________

DESCRIPTION

Solaris 11 releases (as listed below), may experience slowness in allocation of kernel memory that could lead to RAC node evictions.

OCCURRENCE

This issue can occur in the following releases:

SPARC Platform

Solaris 11.1.0.24.2 through 11.3.7.6.0

x86 Platform

Solaris 11.1.0.24.2 through 11.3.7.6.0

Notes:

1. Solaris 10 and ZFS Storage Appliance (ZFSSA) Software are not impacted by this issue.
2. Solaris 8 and Solaris 9 will not be evaluated regarding the potential impact of the issue described in this document.

To determine the SRU level, enter the following command:

$ pkg info entire | grep Summary
Summary: entire incorporation including Support Repository Update (Oracle Solaris 11.1.0.24.2)

SYMPTOMS

If the described issue occurs, the stack of the thread in the 'breadline' queue will appear similar to the following:

> ::stacks -c fed_breadline
    THREAD           STATE   SOBJ   COUNT
    1003e8ff00c0   SLEEP   CV       1
    fed_default_sleep+8
    fed_breadline+0x4a8
    fed_fill_mnode+0x1c0
    fed_fill+0x310
    wallet_fill_common+0x190
    wallet_fill+0x18
    page_create_va_large+0x10c
    segkmem_page_create_large+0x88
    segkmem_xalloc_lp+0x148
    segkmem_alloc_lpi+0x94
    vmem_xalloc+0x670
    vmem_alloc+0x21c
    segkmem_alloc_lp+0x258
    vmem_xalloc+0x658
    vmem_alloc+0x21c
    kmem_slab_create+0x48
    kmem_slab_alloc+0x40
    kmem_cache_alloc+0x2b0
    dbuf_create+0x14
    dbuf_create_bonus+0x14
    dmu_bonus_hold+0x74
    zfs_zget+0x2c
    zfs_dirent_lock+0x480
    zfs_dirlook+0x28c
    zfs_lookup+0x3b8
    fop_lookup+0x15c
    lookuppnvp+0x378
    lookuppnatcred+0x118

Also, 'Encage' failures similar to the ones shown below will be seen:

    > ::predict -l
    EVENT TIMESTAMP MN K SZC P TARGET
    Encage_Tilelet_Failed T- 4.246732s 3 k 256m 0 70a (31792 -= 0)
    Encage_Tilelet_Failed T- 4.398510s 3 k 256m 0 70b (31792 -= 0)
    Encage_Tilelet_Failed T- 4.547170s 3 k 256m 0 70c (31792 -= 0)
    Encage_Tilelet_Failed T- 4.698513s 3 k 256m 0 70d (31792 -= 0)
    Encage_Tilelet_Failed T- 4.851972s 3 k 256m 0 70e (31792 -= 0)