How To
Summary
During file transfer operations to a cloud object store, the transfer may fail if there is insufficient space available in the /tmp directory.
The following error is observed on the STAT/ Work logs located inside /{CD_Install_dir}/work/{nodename}/Syyyymmdd.nnn where y represents year, m represents month, d represents the date and n is the log rolling number:
Failed to create temporary file for /com/sun/jna/linux-x86-64/libjnidispatch.so library
No space left on device
This issue occurs because the Java Native Access (JNA) library attempts to create temporary files in the default /tmp location, which does not have sufficient disk space.
Objective
To provide remediation steps for resolving the temporary file creation error encountered during file transfers to cloud object storage.
Environment
Red Hat Enterprise Linux (RHEL)
Steps
To resolve the issue, configure JNA to use an alternative temporary directory with sufficient space.
Steps
Open the initparm configuration file.
Navigate to the S3 IO Exit plugin section.
Add the following JVM system property:
-Djna_tmpdir=<folder_location>
Replace <folder_location> with a directory path that:
Has sufficient free disk space.
Grants execute permissions to the user performing the file transfer. Ensure appropriate permissions are set:
Example
Additional Information
Root cause:
By default, the JNA library extracts native components (such as libjnidispatch.so) into the system /tmp directory.
If /tmp is full or lacks sufficient space, the library fails to initialize, resulting in the transfer failure.
If you know about Java, you can also look at the link: https://javadoc.io/doc/net.java.dev.jna/jna/latest/com/sun/jna/Native.html#getTempDir()
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
16 February 2026
UID
ibm17260617