1つ以上のアグリゲートのギブバックに失敗しました：lock_managerによって拒否された処理
環境
- ONTAP 9
- ONTAP Select
- Cloud Volumes ONTAP for Azure の略
- Cloud Volumes ONTAP for AWS
- Cloud Volumes ONTAP for GCPの略
問題
- ノードのリブート後、一方のデータアグリゲートがホームノードに戻りません。
cluster1::> 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（ストレージフェイルオーバー）が拒否されたため、ノードが部分的なギブバック状態になっています。
cluster1::> 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.