![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Problem Resolution Sure Solution 1375378.1 : Sun Storage 7000 Unified Storage System: NFS Lock Issue
In all ak software versions up to 2011.1 the number of NFS LOCKD_SERVERS is set to 20. In environments with a high amount of nfs clients this may be insufficient and needs to be increased. In this Document
Created from <SR 3-4898138603> Applies to:Sun Storage 7410 Unified Storage System - Version Not Applicable to Not Applicable [Release N/A]Sun Storage 7310 Unified Storage System - Version Not Applicable to Not Applicable [Release N/A] 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] 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] SymptomsTo 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 - 7000 Series ZFS Appliances
Error: Can't get exclusive lock on file'/svn/franksdk/db/transactions/314-1.txn/rev-lock': No locks available
java.io.IOException: No locks availableat 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) CauseThe issue is caused by the parameter NFS_LOCKD being set to 20 by default. This was already the case in the older Solaris versions. SolutionThe 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. 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 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)
Back to <Document 1402579.1> Sun Storage 7000 Unified Storage System: How to Troubleshoot NFS Problems. References@ <BUG:6998119> - LOCKD SERVERS NEEDS TO DEFAULT TO 512<NOTE:1402579.1> - Sun Storage 7000 Unified Storage System: How to Troubleshoot NFS Problems Attachments This solution has no attachment |
||||||||||||||||||
|