メインコンテンツまでスキップ

E-Seriesコントローラのパニック:AltはsetTempDriveExtentsAltを無視

Views:
8
Visibility:
Public
Votes:
0
Category:
e-series-systems
Specialty:
esg
Last Updated:

環境

NetApp SANtricity OS 11.70.1x以下

問題

コントローラがリブートしました 。これにより、コアダンプがトリガーされ、その後リブートしてリカバリが開始されます。

Alt ignored setTempDriveExtentsAlt call, this controller must reboot


--bt--
#0  dcd::CoreDumpManager::captureCoreDump (this=0xffff8000025f3710, type=dcd::CoreDumpManagement::FULL_DUMP, rebootReason=458754) at dcdCoreDumpMgr.cc:2023
#1  0xffffffff81bc671a in dcd::CoreDumpManager::triggerCoreDump (this=0xffff8000025f3780, dumpType=458754, rebootReason=458754) at dcdCoreDumpMgr.cc:1223
#2  0xffffffff81bc2ecd in dcdCoreDumpCallback (dumpInfo=0xffff8000025f3710, isRecursive=0, rsv1=<optimized out>, rsv2=<optimized out>) at dcdCoreDumpMgr.cc:389
#3  0xffffffff80273555 in sxCallback4 (cbType=<optimized out>, arg1=18446603336260990848, arg2=458754, arg3=458754, arg4=0) at sxCallback.c:271
#4  0xffffffff802508dd in sxReboot (startType=39794448) at sxLib.c:350
#5  0xffffffff8021a217 in sysToMonitor (startType=39794448) at /u/symsm/ccm_wa/symbios/RAIDCore-4301.1.23/m3_e10_840_5600-08.40.30.04/Platform/System/Kernel/BSP/itl_nehalem_64/sysLib.c:1879
#6  0xffffffff80587d32 in reboot ()
#7  0xffffffff802e2e76 in _vkiLogMsg (ctl=0xffff8000025f3710, fmt=<optimized out>, argptr=0x70002) at vkiLog.c:560
#8  0xffffffff802e3264 in _vkiCmnErr (level=<optimized out>, format=<optimized out>) at vkiLog.c:338
#9  0xffffffff8157f511 in vdm::CrushOperation::prepareNewCStripe (this=0xffff8000025f3710, distribution=<optimized out>) at vdmCrushOperation.cc:853
#10 0xffffffff8157f63f in vdm::CrushOperation::begin (this=0x0, executeOp=<optimized out>, distribution=<optimized out>) at vdmCrushOperation.cc:622
#11 0xffffffff8158f314 in vdm::CrushRAIDVolume::startOperation (this=0xffff8000025f3780, dist=0xffff800051a6cc10, stripe=0xffff8000025f3710) at vdmCrushRAIDVolume.cc:5880
#12 0xffffffff815902bb in vdm::CrushRAIDVolume::startOperation (this=0xffff8000025f3710, dist=<optimized out>) at vdmCrushRAIDVolume.cc:5778
#13 0xffffffff815b4b47 in vdm::CrushVolumeGroup::processWorkingState (this=0xffff8000025f3710) at vdmCrushVolumeGroup.cc:5407
#14 0xffffffff815a2167 in vdm::CrushWorkSetupTaskManager::processQueue (this=0x70002) at vdmCrushTask.cc:677
#15 0xffffffff820b0c69 in vdm::CrushTask<vdm::CrushVolumeGroup>::task (this=0xffff8000025f3710) at vdmCrushTask.h:710
#16 0xffffffff820b0d82 in vdm::CrushTask<vdm::CrushVolumeGroup>::taskEntry (taskInstance=0xffff8000025f3710) at vdmCrushTask.h:670
#17 0xffffffff802e66f6 in vkiTask (pCtrl=<optimized out>) at vkiTask.c:847
#18 0xffffffff8054483a in vxTaskEntry ()

D? stackShow
ffffffff80544838 vxTaskEntry      +0x58  : vkiTask +0x89 ()
ffffffff802e66f3 vkiTask        +0xb3  : _ZN3vdm9CrushTaskINS_16CrushVolumeGroupEE9taskEntryEPS2_ ()
ffffffff820b0d7d _ZN3vdm9CrushTaskINS_16CrushVolumeGroupEE9taskEntryEPS2_+0xd   : _ZN3vdm9CrushTaskINS_16CrushVolumeGroupEE4taskEv ()
ffffffff820b0c66 _ZN3vdm9CrushTaskINS_16CrushVolumeGroupEE4taskEv+0x16  : _ZN3vdm25CrushWorkSetupTaskManager12processQueueEv ()
ffffffff815a2162 _ZN3vdm25CrushWorkSetupTaskManager12processQueueEv+0x162 : _ZN3vdm16CrushVolumeGroup19processWorkingStateEv ()
ffffffff815b4b42 _ZN3vdm16CrushVolumeGroup19processWorkingStateEv+0x142 : _ZN3vdm15CrushRAIDVolume14startOperationEPN3adp12DistributionE ()
ffffffff815902b6 _ZN3vdm15CrushRAIDVolume14startOperationEPN3adp12DistributionE+0x1b6 : _ZN3vdm15CrushRAIDVolume14startOperationEPN3adp12DistributionEPNS_11CrushStripeE ()
ffffffff8158f30f _ZN3vdm15CrushRAIDVolume14startOperationEPN3adp12DistributionEPNS_11CrushStripeE+0x16f : _ZN3vdm14CrushOperation5beginEbPN3adp12DistributionE ()
ffffffff8157f63a _ZN3vdm14CrushOperation5beginEbPN3adp12DistributionE+0x6a  : _ZN3vdm14CrushOperation17prepareNewCStripeEPN3adp12DistributionE ()
ffffffff8157f50c _ZN3vdm14CrushOperation17prepareNewCStripeEPN3adp12DistributionE+0xa4c : _vkiCmnErr ()
ffffffff802e325f _vkiCmnErr      +0xbf  : vkiEnableTaskEventDetection +0x450 ()
ffffffff802e2e71 vkiEnableTaskEventDetection+0x721 : _vkiReboot ()
ffffffff80587d2d reboot        +0x1dd : sysToMonitor ()
ffffffff8021a212 sysToMonitor     +0x12  : sxReboot ()
ffffffff802508d8 sxReboot       +0xe8  : sxCallback4 ()
ffffffff80273553 sxCallback4      +0xa3  : _ZNK3dcd15CoreDumpManager12getNotesSizeEv +0x8 ()
ffffffff81bc2ecb dcdCoreDumpCallback +0xfb  : _ZN3dcd15CoreDumpManager15triggerCoreDumpENS_18CoreDumpManagement8DumpTypeEi ()
ffffffff81bc6715 _ZN3dcd15CoreDumpManager15triggerCoreDumpENS_18CoreDumpManagement8DumpTypeEi+0xe5  : _ZN3dcd15CoreDumpManager15captureCoreDumpENS_18CoreDumpManagement8DumpTypeEi ()
ffffffff81bc5d8c _ZN3dcd15CoreDumpManager15captureCoreDumpENS_18CoreDumpManagement8DumpTypeEi+0x2c  : (current instruction)


$4 = (vdm::CrushRAIDVolume * const) 0xffff8000025f3780
(gdb) p *this
$5 = {
. . .
. . .
     m_Ssid = 1162223657,     <<<<<<<<<<
     m_BufCount = 959524162,
     m_QueueDepth = 825242157,
     m_State = 0x412036303a32343a,
     m_IsOwned = 77,

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.