What does errno 52 (EXFULL) in Solaris mean?

EXFULL

EXFULL is not ENOSPC

EXFULL is errno 52 in Solaris-compatible headers. The current Oracle errno catalog labels it Message tables full, while the illumos header retains the older comment exchange full in the convergent-error block. Both sources place it outside ordinary filesystem capacity errors.

The difference between these source descriptions shows that this is legacy interface vocabulary whose exact resource is defined by the producer; it does not mean that free disk blocks, socket buffers, or process file descriptors are exhausted. POSIX does not define this errno.

Investigate the bounded table or exchange resource

• Identify the old service, driver, or compatibility API returning errno 52 and locate the table/exchange object it manages.
• Capture occupancy, configured limits, and object lifetime for that resource before retrying.
• Keep this errno distinct from ENOSPC, ENOBUFS, and EMFILE; those errors describe other exhausted resources.

References

• Oracle Solaris intro(2) errno catalog
• illumos sys/errno.h ABI definitions
• POSIX Issue 8 errno.h