メインコンテンツへスキップ

SVMでoplockを無効にしたあとにoplockが存在するのはなぜですか?

Views:
7
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
NAS
Last Updated:

環境

  • ONTAP 9
  • CIFS
  • トレリクスAV

回答

  • oplock要求はTrellixサーバから送信され、ONTAPはoplock要求を確認応答してNULLのoplockを返します。
  • ONTAP共有でoplockが無効になっているため、Trellixはデータをローカルにキャッシュできません。
  • SVMでoplockが無効になっている

::>vserver cifs share properties show -vserver svm -share-name share

Vserver: svm
Share: share
Share Properties: browsable
changenotify
show-previous-versions

  • vserver locks showの出力にoplockが存在すると表示される

::> vserver locks show -vserver svm -volume vol

Vserver: svm
Volume Object Path LIF Protocol Lock Type Client
-------- ------------------------- ----------- --------- ----------- ----------
Oplock Level: null
/share cifs share-level x.x.x.x
Sharelock Mode: none-deny_none
op-lock x.x.x.x

 

追加情報

AdditionalInformation_text

 

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.