| Previous | Next |
| EMULTIHOP | EPROGMISMATCH |
EOVERFLOW
Usually an application representation problem
EOVERFLOW often means that the underlying object is valid but the program cannot represent one of its values. A classic case is a 32-bit application using a narrow off_t or older struct stat layout against a file larger than 2 GiB. The same category includes inode numbers, block counts, and other metadata that do not fit in the types exposed by the compiled interface.
This is not the same as a disk-full condition or a corrupted file. The server or filesystem may be functioning correctly; the consumer chose an ABI that cannot express the returned information. The failure can appear on stat(), open(), directory enumeration, or an application-level conversion after a successful system call.
How to fix it
- Record the architecture, C library, compiler flags, and sizes of the types receiving file metadata.
- On 32-bit Linux, use the documented large-file configuration consistently across all translation units and dependencies.
- Do not truncate inode numbers, offsets, or file sizes to make the error disappear; that can address the wrong object.
- Test with large files and large inode values in CI when portable tooling must support old ABIs.
References
Looking for a different code? Search another status or error code.