| Previous | Next |
| EBADRQC | ENOBUFS |
ENOANO
ENOANO: Linux legacy errno
ENOANO (errno 3) reports that a legacy filesystem or communications interface cannot resolve the requested anode object. These names come from historical System V/XENIX compatibility interfaces; on modern Linux they usually point to a driver, STREAMS-compatibility layer, or legacy IPC contract rather than a general filesystem error.
Evidence to capture
Record anode identifier, owning filesystem/device, lookup call, and object generation. Save errno immediately after the failing call, together with its return value, because later library or logging calls can overwrite thread-local error state.
Focused test
Look up a known-existing anode through the same interface and compare the result. Keep the process, device/endpoint and deployed driver version fixed so the comparison changes only the suspected boundary.
Correction
correct the stale/missing anode reference or rebuild only the owning metadata if required. If the interface is provided by a compatibility driver, verify its documented ABI and object lifetime instead of assuming that a numerically similar errno from another UNIX has the same contract.
Verification
Repeat the original system call and confirm it passes the former ENOANO boundary with the same object identity. If another errno appears, preserve it as a separate result from the next failing operation.
Technical references
- Linux man-pages: errno(3)
- Linux kernel: asm-generic errno definitions
- GNU C Library: error codes
- illumos: STREAMS programming documentation
Looking for a different code? Search another status or error code.