Skip to main content
NetApp Knowledge Base

Why are OPLOCKS present after OPLOCKS have been disabled on the SVM?

  1. Last updated
  2. Save as PDF
Views:
61
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
NAS
Last Updated:

Applies to

  • ONTAP 9
  • CIFS
  • Trellix AV

Answer

  • The OPLOCKS request is coming from the Trellix server and ONTAP acknowledges the OPLOCK request and gives a NULL OPLOCK.
  • Trellix will not be able to cache the data locally as OPLOCKS are disabled for the ONTAP Share.
  • Oplocks are diabled on an SVM

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

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

  • Output of vserver locks show displays Oplocks present

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

 

Additional Information

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.