NetApp – removing NFS locks

Ssh to the filer and enter in advanced mode:

priv set advanced

Get a list of locks arranged by file via the command:

lock status -f

Note that this can be run on a vfiler also:

vfiler run <vfiler name> lock status -f

Running this against vfiler0 is the same as running against physical filer. You can also list via protocol -p (NFSv3 = NLM) or host -h use FQDN.

filer1a*> vfiler run vnas-vfiler02 lock status -h mysql-12.rejected.io

===== vnas-vfiler02
======== NLM host mysql-12.rejected.io
4992 0x827ac1a5:0x001be870 0:0 1 GRANTED (0xffffff048611bd58)
4992 0x827ac1a5:0x001be86f 0:0 1 GRANTED (0xffffff02ea3cc038)
21998 0x827ac1a5:0x00052ec6 0:0 1 GRANTED (0xffffff03f03c9ab8)
21998 0x827ac1a5:0x002d4146 0:0 1 GRANTED (0xffffff04446f0038)
21998 0x827ac1a5:0x000cb182 0:0 1 GRANTED (0xffffff02ec2b1578)
5118 0x827ac1a5:0x002db7fb 0:0 1 GRANTED (0xffffff03f6a17578)
5118 0x827ac1a5:0x002db7fa 0:0 1 GRANTED (0xffffff02b852f818)
5118 0x827ac1a5:0x002db7f9 0:0 1 GRANTED (0xffffff02dbbc2ab8)
PFS: Filtering of locks by host/owner not implemented.
filer1a*>

To remove lock using 7.1 and above you use:

lock break -h <FQDN of client>

filer1a*> vfiler run vnas-vfiler02 lock break -h mysql-12.rejected.io
===== vnas-vfiler02
PFS: Filtering of locks by host/owner not implemented.
filer1a *>

However when I try I keep seeing the above error, the clearing of the locks still works:

filer1a*> vfiler run vnas-vfiler02 lock status -h mysql-12.rejected.io
===== vnas-mysqldata02
======== NLM host mysql-12.rejected.io
PFS: Filtering of locks by host/owner not implemented.
filer1a *>

 

One thought on “NetApp – removing NFS locks”

  1. Hello I know this is kind of old but the message Filtering of locks by host/owner not implemented.is just telling you that you are not using additional filters, if you do lock status -h 192.168.20.2 -p CIFS it will not display that message.

Leave a Reply

Your email address will not be published. Required fields are marked *