![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||
Solution Type Problem Resolution Sure Solution 1494369.1 : Sun Storage 7000 Unified Storage System: BUI unavailable and seeing errors like "failed to update kstat chain: Not enough space"
In this Document
Created from <SR 3-6245745571> Applies to:Sun Storage 7410 Unified Storage System - Version Not Applicable to Not Applicable [Release N/A]Sun Storage 7310 Unified Storage System - Version Not Applicable to Not Applicable [Release N/A] Sun Storage 7210 Unified Storage System - Version Not Applicable to Not Applicable [Release N/A] Sun Storage 7110 Unified Storage System - Version Not Applicable to Not Applicable [Release N/A] Sun ZFS Storage 7420 - Version Not Applicable to Not Applicable [Release N/A] 7000 Appliance OS (Fishworks) SymptomsBUI access hangs or generates log errors of the form: Thu Mar 22 23:27:37 2012: asynchronous error on statistics module 'mem': failed to update kstat chain: Not enough space These errors will also be seen in the akd.ak error log CLI access may also be lost - but sometimes may still be available The management interface (akd) will usually have been running without having been restarted for months Take a core dump of akd and check vmem: # gcore -o akd.core `pgrep -ox akd` # mdb akd.core.<PID> >::vmem ADDR NAME INUSE TOTAL SUCCEED FAIL To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - 7000 Series ZFS Appliances
CauseThis is most likely a known problem where the akd process that controls the management interface runs out of memory because of memory fragmentation due to large number of oversize allocations. If unsure, please raise a call with Oracle Support who will be able to verify if you are hitting this issue. The likely cause for this is CR 7157268. SolutionThe workaround for this is to restart the management interface (akd) to alleviate the heap fragmentation. If the CLI is still available, it is possible to restart the management interface from there: S7000:> maintenance system restart Please note that if you have a cluster then you should verify that the cluster is in a sane state before restarting the management interface on any one head to prevent a takeover happening. You can check this by checking the cluster configuration:
Valid states for the cluster head and peer are AKCS_CLUSTERED, AKCS_OWNER and AKCS_STRIPPED. In these states restarting the management interface will not cause any takeover by the other head. Restarting the management interface will not have any effect on access to the shares. If the CLI is not available, please raise a service request with Oracle Support to restart the menagement interface.
Note as of the time of writing 2011.04.24.5.0 was not yet available. If an urgent fix is required then it is also available as an IDR based on 2011.1.4.0 (IDR 2011.04.24.4.0,1-2.21.10.1). Access to this IDR will need to be obtained from RPE. Attachments This solution has no attachment |
||||||||||||||||
|