Sun Storage 7000 Unified Storage System: Possible cause of NFS Lock Issue

Asset ID:	1-72-1375378.1
Update Date:	2018-01-08
Keywords:

Solution Type Problem Resolution Sure

Solution 1375378.1 : Sun Storage 7000 Unified Storage System: Possible cause of NFS Lock Issue

Applies to:

Sun Storage 7210 Unified Storage System - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 7110 Unified Storage System - Version Not Applicable to Not Applicable [Release N/A]
Sun ZFS Storage 7120 - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 7410 Unified Storage System - Version Not Applicable to Not Applicable [Release N/A]
Sun ZFS Storage 7320 - Version Not Applicable to Not Applicable [Release N/A]
7000 Appliance OS (Fishworks)
NAS head revision : [2010.Q3 and below]
BIOS revision : [not dependent]
ILOM revision : [not dependent]
JBODs Model : [not dependent]
CLUSTER related : [not dependent]

Symptoms

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Disk Storage ZFS Storage Appliance Community

When trying to mount an nfs share on a Linux client you may see:

Error: Can't get exclusive lock on file
'/svn/franksdk/db/transactions/314-1.txn/rev-lock': No locks available

On a (java) application, you may see :

java.io.IOException: No locks available
at sun.nio.ch.FileChannelImpl.lock0(Native Method)
at sun.nio.ch.FileChannelImpl.lock(FileChannelImpl.java:842)
at java.nio.channels.FileChannel.lock(FileChannel.java:860)
at com.inquira.util.io.FileBasedLock.lock(FileBasedLock.java:103)

Cause

The issue is caused by the parameter NFS_LOCKD being set to 20 by default. This was already the case in the older Solaris versions.

Solution

The solution to this is to set the parameter LOCKD_SERVERS to a higher value than the default of 20. The advice is to set it to 128.
This can be done by issuing a workflow which can be provided by Oracle Customer Support on request.
The workflow only runs on 2010.Q3.X versions of the ak-software.
It should be issued during a period of low activity on the server since it will restart NFS and therefore client mounts will be suspended for a short period of time.

Upgrading to appliance software update version 2011.1.1.1 or later (2011.1.2.1 or later for 7x10 Systems with SAS-1 HBAs) is the preferred solution to this problem.

The workflow is attached to <Bug 6998119> or can be found at http://monaco.sfbay.sun.com/download/net/swsblss1.central.sun.com/attach/bugtraq/cr/6/9/6998119/set_lockd_value.akwf.zip

As per CR 6998119, the following commands should work on any NAS head release (even 2011.1)

CLI> confirm shell svccfg -s nlockmgr:default setprop nfs-props/lockd_servers=128 || (cd /usr/lib/ak/svc/stencil/etc/default && sed '/LOCKD_SERVERS/s/.*$/LOCKD_SERVERS=128/' nfs >/tmp/nfs.$$ && mount -o remount,rw / && cp /tmp/nfs.$$ nfs && mount -o remount,ro /) || (mount -o remount,ro / && echo failed)

Since the release of ak version 2013.1.0 the number of NFS LOCKD_SERVERS is increased to 1024, so this document is no longer applicable for 2013.1.0 and higher versions.

Back to <Document 1402579.1> Sun Storage 7000 Unified Storage System: How to Troubleshoot NFS Problems.

References

<BUG:6998119> - DO NOT USE DEPRECATED DESCRIBESHAREDLIBRARY API FROM SHARED LIBRARY SERVICE
<NOTE:1402579.1> - Sun Storage 7000 Unified Storage System: How to Troubleshoot Problems with the NFS Service

Attachments

This solution has no attachment