libnvme(9)

💖 NAME 💖

okay bestie, welcome to the libnvme(9) page from the API Manual — this one is all about enum libnvme_connect_err, aka the nvme connect error codes. if your connect attempt is acting up, this enum is the roster of what each code is trying to tell you, no cap. 💅

✨ SYNOPSIS ✨

here’s the whole enum in order, copied exactly so nothing gets lost:

       enum libnvme_connect_err {
           ENVME_CONNECT_RESOLVE ,
           ENVME_CONNECT_ADDRFAM ,
           ENVME_CONNECT_TRADDR ,
           ENVME_CONNECT_TARG ,
           ENVME_CONNECT_AARG ,
           ENVME_CONNECT_OPEN ,
           ENVME_CONNECT_WRITE ,
           ENVME_CONNECT_READ ,
           ENVME_CONNECT_PARSE ,
           ENVME_CONNECT_INVAL_TR ,
           ENVME_CONNECT_LOOKUP_SUBSYS_NAME ,
           ENVME_CONNECT_LOOKUP_SUBSYS ,
           ENVME_CONNECT_ALREADY ,
           ENVME_CONNECT_INVAL ,
           ENVME_CONNECT_ADDRINUSE ,
           ENVME_CONNECT_NODEV ,
           ENVME_CONNECT_OPNOTSUPP ,
           ENVME_CONNECT_CONNREFUSED ,
           ENVME_CONNECT_ADDRNOTAVAIL ,
           ENVME_CONNECT_IGNORED ,
           ENVME_CONNECT_NOKEY ,
           ENVME_CONNECT_DRY_RUN

       };

🌟 Constants 🌟

okay so now we go through every single constant, because we do not skip the “boring” parts in this house. every code gets its moment. 🫶

• ENVME_CONNECT_RESOLVE — the host resolve failed — the lookup just did not land 😭
• ENVME_CONNECT_ADDRFAM — unrecognized address family — the address family was not recognized
• ENVME_CONNECT_TRADDR — failed to get traddr — getting the traddr did not work
• ENVME_CONNECT_TARG — you need to give it a transport argument, aka -t
• ENVME_CONNECT_AARG — you need to give it an address argument, aka -a
• ENVME_CONNECT_OPEN — failed to open the nvme-fabrics device
• ENVME_CONNECT_WRITE — failed to write to the nvme-fabrics device
• ENVME_CONNECT_READ — failed to read from the nvme-fabrics device
• ENVME_CONNECT_PARSE — failed to parse ctrl info
• ENVME_CONNECT_INVAL_TR — invalid transport type
• ENVME_CONNECT_LOOKUP_SUBSYS_NAME — failed to look up the subsystem name
• ENVME_CONNECT_LOOKUP_SUBSYS — failed to look up the subsystem
• ENVME_CONNECT_ALREADY — the connect attempt failed because it was already connected
• ENVME_CONNECT_INVAL — invalid arguments/configuration
• ENVME_CONNECT_ADDRINUSE — hostnqn is already in use
• ENVME_CONNECT_NODEV — invalid interface
• ENVME_CONNECT_OPNOTSUPP — not supported
• ENVME_CONNECT_CONNREFUSED — connection refused
• ENVME_CONNECT_ADDRNOTAVAIL — cannot assign requested address
• ENVME_CONNECT_IGNORED — the connect attempt is ignored due to configuration
• ENVME_CONNECT_NOKEY — no TLS PSK or KX-HMAC-CHAP secret available
• ENVME_CONNECT_DRY_RUN — not connected; the context is in dry-run mode 🧚

that’s the whole page, bestie 💖 October 2026 · enum libnvme_connect_err · libnvme(9) — mwah 💋