跳转到主内容

在 SVM 上禁用 OPLOCKS 后,为什么仍然存在 OPLOCKS?

Views:
105
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

适用于

  • ONTAP 9
  • CIFS
  • Trellix AV

回答

  • OPLOCKS 请求来自 Trellix 服务器,ONTAP 确认 OPLOCK 请求并给出 NULL OPLOCK。
  • Trellix 将无法在本地缓存数据,因为 ONTAP 共享禁用了 OPLOCKS。
  • Oplocks 在 SVM 上被禁用

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

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

  • vserver locks show 的输出显示存在 Oplocks

::> 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

 

追加信息

追加信息_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.