A fix is available
APAR status
Closed as program error.
Error description
When running applications that use blocking locks, it is possible that NFSv4 client systems use a lot of memory. This happens when the blocking lock requests are denied thereby causing the client to have to keep retrying the operation. This is _not_ a memory leak, since the memory will get freed when the lock operation succeeds. So as long as the lock request is not satisfied the memory usage could grow.
Local fix
Allow the lock request to be satisfied by causing the current owner of the lock to release it. Or, stop the process that is blocked on the lock request, so that the lock request is not retried.
Problem summary
When a process blocks waiting for a lock on a file in NFS, memory usage increases till the process aquires the lock.
Problem conclusion
Made code changes to reuse memory instead of allocating over and over again.
Temporary fix
Comments
APAR Information
APAR number
IZ98667
Reported component name
AIX 5.3
Reported component ID
5765G0300
Reported release
530
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Submitted date
2011-04-11
Closed date
2011-04-11
Last modified date
2013-04-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
AIX 5.3
Fixed component ID
5765G0300
Applicable component levels
R530 PSY U841150
UP11/06/16 I 1000
PTF to Fileset Mapping
U841150 bos.net.nfs.client 5.3.12.4
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG11P","label":"APARs - AIX 5.3 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"530","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
16 April 2013