{ -vserver <vserver name> - Vserver: This parameter specifies the Vserver containing the lock.
-volume <volume name> - Volume: This parameter specifies the name of the volume containing the lock.
[-lif <lif-name>] - Logical Interface: This parameter specifies the logical interface through which the lock was established.
[-lif-id <integer>] - Logical Interface ID: This parameter specifies the logical interface id through which the lock was established.
-path <text> - Object Path: This parameter specifies a path to the lock.
| -lockid <UUID> - Lock UUID }: This parameter specifies the universally unique identifier (UUID) for the lock. Queries and wildcard characters are not supported.
-owner-id <text> - Owner ID: This parameter specifies an owner ID for a lock. This parameter must be used with the query notation { } exhibited in the second example.
-protocol <lock protocol> - Lock Protocol: This parameter specifies the protocol that was used to establish a lock. This parameter must be used with the query notation { } exhibited in the second example.
-client-address <IP Address> - Client Address: This parameter specifies a client address associated with a lock. This parameter must be used with the query notation { } exhibited in the second example.
-client-address-type {ipv4|ipv6|ipv6z} - Client Address Type: This parameter specifies the type of ip address a client used to create its lock (ipv4, ipv6). This parameter must be used with the query notation { } exhibited in the second example.
-flexcache-volume <text> - FlexCache Volume Name: This parameter specifies the name of the FlexCache volume. This parameter must be used with the query notation { } exhibited in the third example.
-flexcache-vserver <text> - FlexCache Vserver Name: This parameter specifies the name of the Vserver hosting the FlexCache volume. This parameter must be used with the query notation { } exhibited in the third example.
-flexcache-cluster <text> - FlexCache Cluster Name: This parameter specifies the name of the cluster hosting the FlexCache volume. This parameter must be used with the query notation { } exhibited in the third example.

Examples

The following example breaks the locks on all objects on the Vserver named vs0 in the volume named vol0, regardless of the paths to the locked objects and the logical interface through which the locks were established.

cluster1::*> vserver locks break -vserver vs0 -volume vol0 -path * -lif *
WARNING: Breaking file locks can cause applications to become unsynchronized
         and may lead to data corruption.
Do you want to continue? {y|n}: y
1 entry was acted on.

The vserver locks break command can also be issued using a query on the parameters available to the vserver locks show command. The following example breaks all NLM protocol lock objects locked by the client at address 12.34.56.78.

cluster1::*> vserver locks break { -protocol nlm -client-address 12.34.56.78 }
Warning: Breaking file locks can cause applications to become unsynchronized
         and may lead to data corruption.
Do you want to continue? {y|n}: y
1 entry was acted on.

The following example breaks all FlexCache lock objects locked for FlexCache volume "fc1" in Vserver "vs12".

cluster1::*> vserver locks break { -flexcache-volume fc1 -flexcache-vserver vs12 -flexcache-cluster cluster2 }
Warning: Breaking file locks can cause applications to become unsynchronized
         and may lead to data corruption.
Do you want to continue? {y|n}: y
1 entry was acted on.