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

1つ以上のアグリゲートのギブバック処理がロックマネージャによって拒否されました

Views:
970
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
cloud
Last Updated:

環境

  • ONTAP 9
  • ONTAP Select
  • Cloud Volumes ONTAP
  • SMB
  • CIFS

問題

  • ノードのリブート後、いずれかのデータアグリゲートがホームノードに戻りません。

::>storage failover show

                Takeover
Node       Partner     Possible State Description
-------------- -------------- -------- -------------------------------------
node1       node2       true    Connected to node2
node2       node1       true    Connected to node1, Giveback of
                             one or more SFO aggregates failed

2 entries were displayed.

  • Lock_managerによってSFO(ストレージフェイルオーバー)が拒否されたため、ノードが部分的なギブバック状態になっています。

::>storage failover show-giveback

               Partner
Node           Aggregate         Giveback Status
-------------- ----------------- ---------------------------------------------
node1
                                 No aggregates to give back
node2
               CFO Aggregates    Done
               aggr_node1        Failed: Operation was vetoed by
                                 lock_manager.
Giveback failed during lock
                                 manager veto checks or the pre-commit phase.
                                 For veto failures, use the "vserver cifs
                                 session file show -hosting-aggregate
                                 <aggregate list> -continously-available No"
                                 command to view the open files that have
                                 CIFS sessions with non-CA locks established.
                                 <aggregate list> is the list of aggregates
                                 sent home as a result of the giveback
                                 operation. If lock state disruption for all
                                 existing non-CA locks is acceptable, retry
                                 the giveback operation by specifying
                                 "-override-vetoes true". Warning: Overriding
                                 vetoes to perform a giveback can be
                                 disruptive. For pre-commit failure, search
                                 for the lmgr.precommit.oplock.recall EMS
                                 variant for information on how to proceed
                                 using the "event log show -event
                                 lmgr.precommit.oplock.recall.*" command. If
                                 the error persists, contact technical
                                 support for assistance.
2 entries were displayed.

  • 次のようなメッセージがEMSに記録されることがあります。

[node2: cf_giveback: gb.sfo.veto.lmgr.nonCA.locks:error]: Could not complete giveback because of non-CA locks on volume vol_node1@vserver:123a-123a-123a-123a-123a-1234567890ab SFO aggregate aggr_node1.

[node2: cf_giveback: sfo.sendhome.subsystemAbort:alert]: The giveback operation of 'aggr_DATA' was aborted by 'lock_manager'.
[node2: cf_giveback: ha.giveback.totalVetoChk:debug]: Total time taken to check whether to veto the giveback of aggregate 'aggr_DATA' was 5 msecs.

  • BlueXP Canvasにアラートが表示されます:

"Working Environment is degraded" on the "XXX" systemに関するNetAppのドキュメントを参照してください。

 

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.