NFS File Lock Issues Caused By Increasing Unused LockStateID Entries In ZFS Storage Appliance In Exalogic
(Doc ID 1540532.1)
Last updated on FEBRUARY 20, 2019
Applies to:Oracle Exalogic Elastic Cloud Software - Version 18.104.22.168.0 to 22.214.171.124.2
Oracle Exalogic Elastic Cloud Software - Version 126.96.36.199.0 to 188.8.131.52.2
Oracle Exalogic Elastic Cloud Software - Version 184.108.40.206.0 to 220.127.116.11.0
In following Exalogic releases with NFSv4 shares on Client Linux Compute Nodes mounted on ZFS Storage appliance, intermittent file lock issues are observed when accessing files on NFSv4 shares.
- Exalogic Physical Releases: 18.104.22.168.1, 22.214.171.124.2, 126.96.36.199.3, 188.8.131.52.1, 184.108.40.206.2
- Exalogic Virtual Releases: 2.0.1.X, 2.0.4.X
This issue is observed even with all the following recommendations in place:
- IPMP Failback disabled
- NFSv4 delegation disabled on Storage Appliance
- Working NIS configuration
- Working NTP settings
Due to this, any application process or WebLogic process startup on NFSv4 file system fails with unable to obtain lock exception. Below is a snippet of the WebLogic server log showing failed startup because of file lock issue.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document