APAR status
Closed as program error.
Error description
Here is a scenario where the force unmount of a J2 filesystem was taking longer than expected: 1. The NFS server hosts 17 J2 filesystems, which are exported to an NFS client. 2. One of these J2 filesystems on the NFS server contains approximately 300,000 files. 3. The NFS client mounts all 17 filesystems and runs a scanner application on them. 4. After the scanner application completes its task, the filesystems are unmounted on both the NFS client and the NFS server. 5. On the NFS server, the filesystems are force unmounted. However, the force unmount of the specific J2 filesystem is taking longer than usual.
Local fix
Problem summary
On a AIX LPAR when a j2 filesystem is exported as nfs share, then fter unmounting the nfs share and when unmounting the j2 using force unmount option, the unmount will take aroung 30-35 mins.
Problem conclusion
The vnc cache will be purged, before proceeding to cleanup the inodes of the FS.
Temporary fix
Comments
APAR Information
APAR number
IJ53140
Reported component name
AIX V7.3
Reported component ID
5765CD300
Reported release
730
Status
CLOSED PER
HIPER
NoHIPER
Submitted date
2024-12-05
Closed date
2024-12-05
Last modified date
2025-12-10
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 V7.3
Fixed component ID
5765CD300
Applicable component levels
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SG11T","label":"AIX 7.3 HIPERS- APARs and Fixes"},"Platform":[{"code":"PF053","label":"Power Systems"}],"Version":"730","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]
Document Information
Modified date:
10 December 2025