libnvme(2)

hey bestie 💖 welcome to libnvme(2) — aka the API Manual. today we're decoding enum nvme_status_field, which is literally every part of the NVMe status field: the status code, the status code type, and any extra flags. no cap.

🎀 NAME 🎀

enum nvme_status_field — this enum defines all the pieces of the nvme status field: the status code, the status code type, and additional flags. 🦋

✨ SYNOPSIS ✨

       enum nvme_status_field {
           NVME_SCT_GENERIC ,
           NVME_SCT_CMD_SPECIFIC ,
           NVME_SCT_MEDIA ,
           NVME_SCT_PATH ,
           NVME_SCT_VS ,
           NVME_SCT_MASK ,
           NVME_SCT_SHIFT ,
           NVME_SC_MASK ,
           NVME_SC_SHIFT ,
           NVME_SC_SUCCESS ,
           NVME_SC_INVALID_OPCODE ,
           NVME_SC_INVALID_FIELD ,
           NVME_SC_CMDID_CONFLICT ,
           NVME_SC_DATA_XFER_ERROR ,
           NVME_SC_POWER_LOSS ,
           NVME_SC_INTERNAL ,
           NVME_SC_ABORT_REQ ,
           NVME_SC_ABORT_QUEUE ,
           NVME_SC_FUSED_FAIL ,
           NVME_SC_FUSED_MISSING ,
           NVME_SC_INVALID_NS ,
           NVME_SC_CMD_SEQ_ERROR ,
           NVME_SC_SGL_INVALID_LAST ,
           NVME_SC_SGL_INVALID_COUNT ,
           NVME_SC_SGL_INVALID_DATA ,
           NVME_SC_SGL_INVALID_METADATA ,
           NVME_SC_SGL_INVALID_TYPE ,
           NVME_SC_CMB_INVALID_USE ,
           NVME_SC_PRP_INVALID_OFFSET ,
           NVME_SC_AWU_EXCEEDED ,
           NVME_SC_OP_DENIED ,
           NVME_SC_SGL_INVALID_OFFSET ,
           NVME_SC_HOSTID_FORMAT ,
           NVME_SC_KAT_EXPIRED ,
           NVME_SC_KAT_INVALID ,
           NVME_SC_CMD_ABORTED_PREMEPT ,
           NVME_SC_SANITIZE_FAILED ,
           NVME_SC_SANITIZE_IN_PROGRESS ,
           NVME_SC_SGL_INVALID_GRANULARITY ,
           NVME_SC_CMD_IN_CMBQ_NOT_SUPP ,
           NVME_SC_NS_WRITE_PROTECTED ,
           NVME_SC_CMD_INTERRUPTED ,
           NVME_SC_TRAN_TPORT_ERROR ,
           NVME_SC_PROHIBITED_BY_CMD_AND_FEAT ,
           NVME_SC_ADMIN_CMD_MEDIA_NOT_READY ,
           NVME_SC_INVALID_KEY_TAG ,
           NVME_SC_HOST_DISPERSED_NS_NOT_ENABLED ,
           NVME_SC_HOST_ID_NOT_INITIALIZED ,
           NVME_SC_INCORRECT_KEY ,
           NVME_SC_FDP_DISABLED ,
           NVME_SC_INVALID_PLACEMENT_HANDLE_LIST ,
           NVME_SC_LBA_RANGE ,
           NVME_SC_CAP_EXCEEDED ,
           NVME_SC_NS_NOT_READY ,
           NVME_SC_RESERVATION_CONFLICT ,
           NVME_SC_FORMAT_IN_PROGRESS ,
           NVME_SC_INVALID_VALUE_SIZE ,
           NVME_SC_INVALID_KEY_SIZE ,
           NVME_SC_KV_KEY_NOT_EXISTS ,
           NVME_SC_UNRECOVERED_ERROR ,
           NVME_SC_KEY_EXISTS ,
           NVME_SC_CQ_INVALID ,
           NVME_SC_QID_INVALID ,
           NVME_SC_QUEUE_SIZE ,
           NVME_SC_ABORT_LIMIT ,
           NVME_SC_ABORT_MISSING ,
           NVME_SC_ASYNC_LIMIT ,
           NVME_SC_FIRMWARE_SLOT ,
           NVME_SC_FIRMWARE_IMAGE ,
           NVME_SC_INVALID_VECTOR ,
           NVME_SC_INVALID_LOG_PAGE ,
           NVME_SC_INVALID_FORMAT ,
           NVME_SC_FW_NEEDS_CONV_RESET ,
           NVME_SC_INVALID_QUEUE ,
           NVME_SC_FEATURE_NOT_SAVEABLE ,
           NVME_SC_FEATURE_NOT_CHANGEABLE ,
           NVME_SC_FEATURE_NOT_PER_NS ,
           NVME_SC_FW_NEEDS_SUBSYS_RESET ,
           NVME_SC_FW_NEEDS_RESET ,
           NVME_SC_FW_NEEDS_MAX_TIME ,
           NVME_SC_FW_ACTIVATE_PROHIBITED ,
           NVME_SC_OVERLAPPING_RANGE ,
           NVME_SC_NS_INSUFFICIENT_CAP ,
           NVME_SC_NS_ID_UNAVAILABLE ,
           NVME_SC_NS_ALREADY_ATTACHED ,
           NVME_SC_NS_IS_PRIVATE ,
           NVME_SC_NS_NOT_ATTACHED ,
           NVME_SC_THIN_PROV_NOT_SUPP ,
           NVME_SC_CTRL_LIST_INVALID ,
           NVME_SC_SELF_TEST_IN_PROGRESS ,
           NVME_SC_BP_WRITE_PROHIBITED ,
           NVME_SC_INVALID_CTRL_ID ,
           NVME_SC_INVALID_SEC_CTRL_STATE ,
           NVME_SC_INVALID_CTRL_RESOURCES ,
           NVME_SC_INVALID_RESOURCE_ID ,
           NVME_SC_PMR_SAN_PROHIBITED ,
           NVME_SC_ANA_GROUP_ID_INVALID ,
           NVME_SC_ANA_ATTACH_FAILED ,
           NVME_SC_INSUFFICIENT_CAP ,
           NVME_SC_NS_ATTACHMENT_LIMIT_EXCEEDED ,
           NVME_SC_PROHIBIT_CMD_EXEC_NOT_SUPPORTED ,
           NVME_SC_IOCS_NOT_SUPPORTED ,
           NVME_SC_IOCS_NOT_ENABLED ,
           NVME_SC_IOCS_COMBINATION_REJECTED ,
           NVME_SC_INVALID_IOCS ,
           NVME_SC_ID_UNAVAILABLE ,
           NVME_SC_INVALID_DISCOVERY_INFO ,
           NVME_SC_ZONING_DATA_STRUCT_LOCKED ,
           NVME_SC_ZONING_DATA_STRUCT_NOTFND ,
           NVME_SC_INSUFFICIENT_DISC_RES ,
           NVME_SC_REQSTD_FUNCTION_DISABLED ,
           NVME_SC_ZONEGRP_ORIGINATOR_INVLD ,
           NVME_SC_INVALID_CONTROLER_DATA_QUEUE ,
           NVME_SC_NOT_ENOUGH_RESOURCES ,
           NVME_SC_CONTROLLER_SUSPENDED ,
           NVME_SC_CONTROLLER_NOT_SUSPENDED ,
           NVME_SC_CONTROLLER_DATA_QUEUE_FULL ,
           NVME_SC_BAD_ATTRIBUTES ,
           NVME_SC_INVALID_PI ,
           NVME_SC_READ_ONLY ,
           NVME_SC_CMD_SIZE_LIMIT_EXCEEDED ,
           NVME_SC_INCOMPATIBLE_NS ,
           NVME_SC_FAST_COPY_NOT_POSSIBLE ,
           NVME_SC_OVERLAPPING_IO_RANGE ,
           NVME_SC_INSUFFICIENT_RESOURCES ,
           NVME_SC_CONNECT_FORMAT ,
           NVME_SC_CONNECT_CTRL_BUSY ,
           NVME_SC_CONNECT_INVALID_PARAM ,
           NVME_SC_CONNECT_RESTART_DISC ,
           NVME_SC_CONNECT_INVALID_HOST ,
           NVME_SC_DISCONNECT_INVALID_QTYPE ,
           NVME_SC_DISCOVERY_RESTART ,
           NVME_SC_AUTH_REQUIRED ,
           NVME_SC_ZNS_INVALID_OP_REQUEST ,
           NVME_SC_ZNS_ZRWA_RESOURCES_UNAVAILABLE ,
           NVME_SC_ZNS_BOUNDARY_ERROR ,
           NVME_SC_ZNS_FULL ,
           NVME_SC_ZNS_READ_ONLY ,
           NVME_SC_ZNS_OFFLINE ,
           NVME_SC_ZNS_INVALID_WRITE ,
           NVME_SC_ZNS_TOO_MANY_ACTIVE ,
           NVME_SC_ZNS_TOO_MANY_OPENS ,
           NVME_SC_ZNS_INVAL_TRANSITION ,
           NVME_SC_WRITE_FAULT ,
           NVME_SC_READ_ERROR ,
           NVME_SC_GUARD_CHECK ,
           NVME_SC_APPTAG_CHECK ,
           NVME_SC_REFTAG_CHECK ,
           NVME_SC_COMPARE_FAILED ,
           NVME_SC_ACCESS_DENIED ,
           NVME_SC_UNWRITTEN_BLOCK ,
           NVME_SC_STORAGE_TAG_CHECK ,
           NVME_SC_ANA_INTERNAL_PATH_ERROR ,
           NVME_SC_ANA_PERSISTENT_LOSS ,
           NVME_SC_ANA_INACCESSIBLE ,
           NVME_SC_ANA_TRANSITION ,
           NVME_SC_CTRL_PATH_ERROR ,
           NVME_SC_HOST_PATH_ERROR ,
           NVME_SC_CMD_ABORTED_BY_HOST ,
           NVME_SC_CRD ,
           NVME_SC_MORE ,
           NVME_SC_DNR

       };

💅 Constants 💅

• NVME_SCT_GENERIC — generic errors that apply to multiple opcodes, not just one. 🌈
• NVME_SCT_CMD_SPECIFIC — errors associated to one specific opcode. 🎯
• NVME_SCT_MEDIA — errors associated with media and data integrity. 💾
• NVME_SCT_PATH — errors associated with the paths connection. 🛣️
• NVME_SCT_VS — vendor specific errors — your hardware brand's own lil' special sauce. 🏷️
• NVME_SCT_MASK — the mask to get the value of the Status Code Type. 🎭
• NVME_SCT_SHIFT — the shift value to get the value of the Status Code Type. ✨
• NVME_SC_MASK — the mask to get the value of the status code. 🕵️‍♀️
• NVME_SC_SHIFT — the shift value to get the value of the status code. 🔢
• NVME_SC_SUCCESS — Successful Completion: the command completed without error. periodt. ✅
• NVME_SC_INVALID_OPCODE — Invalid Command Opcode: a reserved coded value or an unsupported value in the command opcode field. 🚫
• NVME_SC_INVALID_FIELD — Invalid Field in Command: a reserved coded value or an unsupported value in a defined field. 🙅‍♀️
• NVME_SC_CMDID_CONFLICT — Command ID Conflict: the command identifier is already in use. 💥
• NVME_SC_DATA_XFER_ERROR — Data Transfer Error: transferring the data or metadata associated with a command experienced an error. 😭
• NVME_SC_POWER_LOSS — Commands Aborted due to Power Loss Notification: the command was aborted due to a power loss notification. 🔌
• NVME_SC_INTERNAL — Internal Error: the command was not completed successfully due to an internal error. 💀
• NVME_SC_ABORT_REQ — Command Abort Requested: the command was aborted due to an Abort command being received that specified the Submission Queue Identifier and Command Identifier of this command. 🛑
• NVME_SC_ABORT_QUEUE — Command Aborted due to SQ Deletion: the command was aborted due to a Delete I/O Submission Queue request received for the Submission Queue to which the command was submitted. 🗑️
• NVME_SC_FUSED_FAIL — Command Aborted due to Failed Fused Command: the command was aborted due to the other command in a fused operation failing. 💔
• NVME_SC_FUSED_MISSING — Aborted due to Missing Fused Command: the fused command was aborted due to the adjacent submission queue entry not containing a fused command that is the other command. 👻
• NVME_SC_INVALID_NS — Invalid Namespace or Format: the namespace or the format of that namespace is invalid. 🚷
• NVME_SC_CMD_SEQ_ERROR — Command Sequence Error: the command was aborted due to a protocol violation in a multi-command sequence. 🔄
• NVME_SC_SGL_INVALID_LAST — Invalid SGL Segment Descriptor: the command includes an invalid SGL Last Segment or SGL Segment descriptor. 📝
• NVME_SC_SGL_INVALID_COUNT — Invalid Number of SGL Descriptors: there is an SGL Last Segment descriptor or an SGL Segment descriptor in a location other than the last descriptor of a segment based on the length indicated. 📏
• NVME_SC_SGL_INVALID_DATA — Data SGL Length Invalid: this may occur if the length of a Data SGL is too short. This may occur if the length of a Data SGL is too long and the controller does not support SGL transfers longer than the amount of data to be transferred as indicated in the SGL Support field of the Identify Controller data structure. 📐
• NVME_SC_SGL_INVALID_METADATA — Metadata SGL Length Invalid: this may occur if the length of a Metadata SGL is too short. This may occur if the length of a Metadata SGL is too long and the controller does not support SGL transfers longer than the amount of data to be transferred as indicated in the SGL Support field of the Identify Controller data structure. 📐
• NVME_SC_SGL_INVALID_TYPE — SGL Descriptor Type Invalid: the type of an SGL Descriptor is a type that is not supported by the controller. 🚫
• NVME_SC_CMB_INVALID_USE — Invalid Use of Controller Memory Buffer: the attempted use of the Controller Memory Buffer is not supported by the controller. 🧠
• NVME_SC_PRP_INVALID_OFFSET — PRP Offset Invalid: the Offset field for a PRP entry is invalid. 📍
• NVME_SC_AWU_EXCEEDED — Atomic Write Unit Exceeded: the length specified exceeds the atomic write unit size. 📏
• NVME_SC_OP_DENIED — Operation Denied: the command was denied due to lack of access rights. Refer to the appropriate security specification. 🔒
• NVME_SC_SGL_INVALID_OFFSET — SGL Offset Invalid: that offset you put in a descriptor? not valid bestie 💀. happens when you're doing capsule data transfers in NVMe over Fabrics implementations and you slide an invalid offset into the capsule.
• NVME_SC_HOSTID_FORMAT — Host Identifier Inconsistent Format: the NVM subsystem caught you using 64-bit and 128-bit Host Identifier values at the same time on different controllers. pick a lane ✋.
• NVME_SC_KAT_EXPIRED — Keep Alive Timer Expired: the Keep Alive Timer ran out. she's gone, she expired 🌸.
• NVME_SC_KAT_INVALID — Keep Alive Timeout Invalid: the Keep Alive Timeout value you specified is simply not it.
• NVME_SC_CMD_ABORTED_PREMEPT — Command Aborted due to Preempt and Abort: the command got aborted because of a Reservation Acquire command. rip.
• NVME_SC_SANITIZE_FAILED — Sanitize Failed: the most recent sanitize operation flopped and no recovery action has been successfully completed yet 😭.
• NVME_SC_SANITIZE_IN_PROGRESS — Sanitize In Progress: whatever function you're asking for (like, a command) is prohibited while a sanitize operation is in progress. just wait babes ⏳.
• NVME_SC_SGL_INVALID_GRANULARITY — SGL Data Block Granularity Invalid: the Address alignment or the Length granularity for an SGL Data Block descriptor is invalid. off-grid, not slaying.
• NVME_SC_CMD_IN_CMBQ_NOT_SUPP — Command Not Supported for Queue in CMB: this implementation doesn't support submitting the command to a Submission Queue in the Controller Memory Buffer, and it doesn't support command completion to a Completion Queue in the Controller Memory Buffer either. both, no 💅.
• NVME_SC_NS_WRITE_PROTECTED — Namespace is Write Protected: command is prohibited while the namespace is write protected, which happens as a result of a change in the namespace write protection state as defined by the Namespace Write Protection State Machine. she said no 🚫.
• NVME_SC_CMD_INTERRUPTED — Command Interrupted: command processing got interrupted and the controller can't successfully complete the command. the host should retry the command, fr fr 🔁.
• NVME_SC_TRAN_TPORT_ERROR — Transient Transport Error: a transient transport error was detected. if you retry on the same controller the command is likely to succeed. but listen — a command that fails with a transient transport error four or more times should be treated as a persistent transport error, which is not likely to succeed if retried on the same controller. so. know when to stop 😤.
• NVME_SC_PROHIBITED_BY_CMD_AND_FEAT — Command Prohibited by Command and Feature Lockdown: the command was aborted because command execution is prohibited by the Command and Feature Lockdown. lockdown era 🔒.
• NVME_SC_ADMIN_CMD_MEDIA_NOT_READY — Admin Command Media Not Ready: the Admin command needs access to media and the media is not ready. she's not up yet 🙈.
• NVME_SC_INVALID_KEY_TAG — the command was aborted because of an invalid KEYTAG field value. wrong tag, no entry 🎀.
• NVME_SC_HOST_DISPERSED_NS_NOT_ENABLED — the command is prohibited while the Host Disperesed Namespace Support (HDISNS) field is not set to 1h in the Host Behavior Support feature. (yes, "Disperesed" — we keep the original spelling, character for character, we don't fix it 💖.)
• NVME_SC_HOST_ID_NOT_INITIALIZED — Host Identifier Not Initialized. that's it, that's the whole thing. go initialize her ✨.
• NVME_SC_INCORRECT_KEY — the command was aborted because the key associated with the KEYTAG field is incorrect. wrong key bestie 🔑.
• NVME_SC_FDP_DISABLED — the command is not allowed when Flexible Data Placement is disabled. fdp off = command off 🙅‍♀️.
• NVME_SC_INVALID_PLACEMENT_HANDLE_LIST — the Placement Handle List is invalid, and hear me out, this happens because of an invalid Reclaim Unit Handle Identifier or because you gave a valid Reclaim Unit Handle Identifier but it's restricted — or the Placement Handle List number of entries exceeded the maximum number allowed. three ways to be wrong, iconic 😭.
• NVME_SC_LBA_RANGE — LBA Out of Range: the command references an LBA that exceeds the size of the namespace. out of bounds, out of pocket 📏.
• NVME_SC_CAP_EXCEEDED — Capacity Exceeded: executing the command has caused the capacity of the namespace to be exceeded. too much, too full 🫃.
• NVME_SC_NS_NOT_READY — Namespace Not Ready: the namespace is not ready to be accessed, and specifically because of a condition other than a condition that is reported as an Asymmetric Namespace Access condition. very specific about that ✍️.
• NVME_SC_RESERVATION_CONFLICT — Reservation Conflict: the command was aborted due to a conflict with a reservation held on the accessed namespace. she's taken 💅.
• NVME_SC_FORMAT_IN_PROGRESS — Format In Progress: a Format NVM command is in progress on the namespace. currently busy formatting, do not perceive her.
• NVME_SC_INVALID_VALUE_SIZE — the value size is not valid. that one's pretty self-explanatory bestie.
• NVME_SC_INVALID_KEY_SIZE — the KV key size is not valid. key too small, key too big, key just wrong 📐.
• NVME_SC_KV_KEY_NOT_EXISTS — the Store If Key Exists (SIKE) bit is set to exists. yeah, that's what the original says. if you needed it to exist and it doesn't — this is your girl 😭.
• NVME_SC_UNRECOVERED_ERROR — there was an unrecovered error when reading from the meidum. (original spelling, "meidum", we're keeping it, no cap 🎀.) genuinely not a good time.
• NVME_SC_KEY_EXISTS — the Store If No Key Exists (SINKE) bit is set to '1' in the Store Option field and the KV key exists. you wanted it to not exist. it exists. awkward 💀.
• NVME_SC_CQ_INVALID — Completion Queue Invalid: the Completion Queue identifier specified in the command does not exist. there is no such queue babes.
• NVME_SC_QID_INVALID — Invalid Queue Identifier: creating the I/O Completion Queue failed because the queue identifier specified as part of the command was invalid. an invalid queue identifier is one that's currently in use, or one that's outside the range supported by the controller. two flavors of nope 🚫.
• NVME_SC_QUEUE_SIZE — Invalid Queue Size: the host tried to create an I/O Completion Queue with an invalid number of entries. wrong amount, babe.
• NVME_SC_ABORT_LIMIT — Abort Command Limit Exceeded: the number of concurrently outstanding Abort commands has blown past the limit indicated in the Identify Controller data structure. too many aborts at once 🔥.
• NVME_SC_ABORT_MISSING — Abort Command is missing: the abort command is missing. where is she. she's not here 😭.
• NVME_SC_ASYNC_LIMIT — Asynchronous Event Request Limit Exceeded: the number of concurrently outstanding Asynchronous Event Request commands has been exceeded. again: too many, too at once ✋.
• NVME_SC_FIRMWARE_SLOT — Invalid Firmware Slot: the firmware slot indicated is invalid or read only. this error is indicated if the firmware slot exceeds the number supported. also she cannot be written to, mind you.
• NVME_SC_FIRMWARE_IMAGE — Invalid Firmware Image: the firmware image specified for activation is invalid and was not loaded by the controller. not loaded, not welcome 🚪.
• NVME_SC_INVALID_VECTOR — Invalid Interrupt Vector: creating the I/O Completion Queue failed because of an invalid interrupt vector specified as part of the command. vector said no 💅.
• NVME_SC_INVALID_LOG_PAGE — Invalid Log Page: the log page indicated is invalid. this error condition is also returned if a reserved log page is requested. so like, double trouble 📄.
• NVME_SC_INVALID_FORMAT — Invalid Format: the LBA Format specified is not supported. pick a supported one bestie 💖.
• NVME_SC_FW_NEEDS_CONV_RESET — Firmware Activation Requires Conventional Reset: the firmware commit was successful — slay — however, activation of the firmware image requires a conventional reset. congrats, now go reset 🎉.
• NVME_SC_INVALID_QUEUE — Invalid Queue Deletion: invalid I/O Completion Queue specified to delete. can't delete what isn't right 🗑️.
• NVME_SC_FEATURE_NOT_SAVEABLE — Feature Identifier Not Saveable: the Feature Identifier specified does not support a saveable value. no saving for you 💾❌.
• NVME_SC_FEATURE_NOT_CHANGEABLE — Feature Not Changeable: the Feature Identifier is not able to be changed. she's immutable babes 🔒.
• NVME_SC_FEATURE_NOT_PER_NS — Feature Not Namespace Specific: the Feature Identifier specified is not namespace specific — the Feature Identifier settings apply across all namespaces. global girl 🌍.
• NVME_SC_FW_NEEDS_SUBSYS_RESET — Firmware Activation Requires NVM Subsystem Reset: the firmware commit was successful, however, activation of the firmware image requires an NVM Subsystem. (yes, the original sentence just ends there — we keep it exactly, character for character, no embellishing 💖.) you still need that reset though.
• NVME_SC_FW_NEEDS_RESET — Firmware Activation Requires Controller Level Reset: the firmware commit was successful; however, the image specified does not support being activated without a reset. no reset, no activation, periodt ✨.
• NVME_SC_FW_NEEDS_MAX_TIME — Firmware Activation Requires Maximum Time Violation: the image specified, if it were activated immediately, would exceed the Maximum Time for Firmware Activation (MTFA) value reported in Identify Controller. too slow to be allowed right now ⏰.
• NVME_SC_FW_ACTIVATE_PROHIBITED — Firmware Activation Prohibited: the image specified is being prohibited from activation by the controller for vendor specific reasons. vendor said no, and that's all we know 🤷‍♀️.
• NVME_SC_OVERLAPPING_RANGE — Overlapping Range: the downloaded firmware image has overlapping ranges. she's stepping on her own toes 🦶.
• NVME_SC_NS_INSUFFICIENT_CAP — Namespace Insufficient Capacity: creating the namespace requires more free space than is currently available. you're broke, capacity-wise 💸.
• NVME_SC_NS_ID_UNAVAILABLE — Namespace Identifier Unavailable: the number of namespaces supported has been exceeded. you ran out of namespace ids babe 🎀.
• NVME_SC_NS_ALREADY_ATTACHED — Namespace Already Attached: the controller is already attached to the namespace specified. she's already yours 💅.
• NVME_SC_NS_IS_PRIVATE — Namespace Is Private: the namespace is private and is already attached to one controller. one controller only, that's the whole vibe 🔐.
• NVME_SC_NS_NOT_ATTACHED — Namespace Not Attached: the request to detach the controller could not be completed because the controller is not attached to the namespace. can't detach what was never attached bestie 😭.
• NVME_SC_THIN_PROV_NOT_SUPP — Thin Provisioning Not Supported: thin provisioning is not supported by the controller. not supported, not happening 🚫.
• NVME_SC_CTRL_LIST_INVALID — Controller List Invalid: the controller list provided contains invalid controller ids. bad ids, bad list 📝.
• NVME_SC_SELF_TEST_IN_PROGRESS — Device Self-test In Progress: the controller or NVM subsystem already has a device self-test operation in process. she's doing her little tests, leave her be 🧪.
• NVME_SC_BP_WRITE_PROHIBITED — Boot Partition Write Prohibited: bestie the command is literally trying to modify a Boot Partition that's locked. Rude. Denied. 💀
• NVME_SC_INVALID_CTRL_ID — Invalid Controller Identifier 🫠
• NVME_SC_INVALID_SEC_CTRL_STATE — Invalid Secondary Controller State
• NVME_SC_INVALID_CTRL_RESOURCES — Invalid Number of Controller Resources
• NVME_SC_INVALID_RESOURCE_ID — Invalid Resource Identifier
• NVME_SC_PMR_SAN_PROHIBITED — Sanitize Prohibited While Persistent Memory Region is Enabled
• NVME_SC_ANA_GROUP_ID_INVALID — ANA Group Identifier Invalid: the ANA Group Identifier (ANAGRPID) you specified is not supported in the command you just submitted. ✨
• NVME_SC_ANA_ATTACH_FAILED — ANA Attach Failed: the controller is not attached to the namespace because of an ANA condition. It's giving uninvited 🥲
• NVME_SC_INSUFFICIENT_CAP — Insufficient Capacity: the operation you asked for needs more free space than is available rn. No room bestie, the closet is full 🎀
• NVME_SC_NS_ATTACHMENT_LIMIT_EXCEEDED — Namespace Attachment Limit Exceeded: attaching the ns to a controller pushes the max number of ns attachments allowed over the limit. Overflow era, but make it forbidden 💅
• NVME_SC_PROHIBIT_CMD_EXEC_NOT_SUPPORTED — Prohibition of Command Execution Not Supported
• NVME_SC_IOCS_NOT_SUPPORTED — I/O Command Set Not Supported
• NVME_SC_IOCS_NOT_ENABLED — I/O Command Set Not Enabled
• NVME_SC_IOCS_COMBINATION_REJECTED — I/O Command Set Combination Rejected
• NVME_SC_INVALID_IOCS — Invalid I/O Command Set
• NVME_SC_ID_UNAVAILABLE — Identifier Unavailable
• NVME_SC_INVALID_DISCOVERY_INFO — the discovery info you put in one or more extended discovery information entries just doesn't apply to the type of entity selected in the Entity Type (ETYPE) field of the Discovery Information Management command data portion's header. Mismatch, babes 🦋
• NVME_SC_ZONING_DATA_STRUCT_LOCKED — the Zoning data structure you requested is locked on the CDC. 🔒
• NVME_SC_ZONING_DATA_STRUCT_NOTFND — the Zoning data structure you requested does not exist on the CDC. Nowhere to be found, not even in the group chat 🙈
• NVME_SC_INSUFFICIENT_DISC_RES — the number of discover information entries you provided in the data portion of the Discovery Information Management command for a registration task (that's the TAS field cleared to 0h) exceeds the available capacity for new discovery information entries on the CDC or DDC. Heads up: this may be a transient condition, so don't spiral 🌀
• NVME_SC_REQSTD_FUNCTION_DISABLED — Fabric Zoning is not enabled on the CDC ✋
• NVME_SC_ZONEGRP_ORIGINATOR_INVLD — the NQN in the ZoneGroup Originator field does not match the Host NQN the DDC used to connect to the CDC. Identity crisis, but make it an error 😭
• NVME_SC_INVALID_CONTROLER_DATA_QUEUE — this error means the Controller Data Queue Identifier you specified is invalid for the controller processing the command. (Yes, the spelling CONTROLER is exactly as written. We don't fix it. We respect it. 👑)
• NVME_SC_NOT_ENOUGH_RESOURCES — this error means there are not enough resources in the controller to process the command. Low battery energy 🪫
• NVME_SC_CONTROLLER_SUSPENDED — the operation you asked for is not allowed if the specified controller is suspended 😴
• NVME_SC_CONTROLLER_NOT_SUSPENDED — the operation you asked for is not allowed if the specified controller is not suspended. Yes, the opposite one. Both exist. Periodt 💅
• NVME_SC_CONTROLLER_DATA_QUEUE_FULL — the controller detected that a Controller Data Queue became full. Packed house 🎀
• NVME_SC_BAD_ATTRIBUTES — Conflicting Dataset Management Attributes
• NVME_SC_INVALID_PI — Invalid Protection Information
• NVME_SC_READ_ONLY — Attempted Write to Read Only Range. It's read only, bestie, reading is the whole vibe 📖
• NVME_SC_CMD_SIZE_LIMIT_EXCEEDED — Command Size Limit Exceeded
• NVME_SC_INCOMPATIBLE_NS — Incompatible Namespace or Format: at least one source namespace and the destination namespace have incompatible formats. They're not compatible, it's not gonna work out 😔
• NVME_SC_FAST_COPY_NOT_POSSIBLE — Fast Copy Not Possible: the Fast Copy Only (FCO) bit was set to '1' in a Source Range entry, and the controller was not able to use fast copy operations to copy the specified data. The fast lane was closed 🚧
• NVME_SC_OVERLAPPING_IO_RANGE — Overlapping I/O Range: a source logical block range overlaps the destination logical block range. Personal space, please 🫶
• NVME_SC_INSUFFICIENT_RESOURCES — Insufficient Resources: a resource shortage prevented the controller from performing the requested copy. 💀
• NVME_SC_CONNECT_FORMAT — Incompatible Format: the NVM subsystem does not support the record format the host specified. 🌸
• NVME_SC_CONNECT_CTRL_BUSY — Controller Busy: the controller is already associated with a host. Taken. 🫠
• NVME_SC_CONNECT_INVALID_PARAM — Connect Invalid Parameters: one or more of the command parameters. (That's the whole sentence in the original, bestie, we keep it exactly as it is. Iconic minimalism ✨)
• NVME_SC_CONNECT_RESTART_DISC — Connect Restart Discovery: the NVM subsystem you requested is not available. 🚫
• NVME_SC_CONNECT_INVALID_HOST — Connect Invalid Host: either the host is not allowed to establish an association to any controller in the NVM subsystem, or the host is not allowed to establish an association to the specified controller. Either way, no entry 🎟️
• NVME_SC_DISCONNECT_INVALID_QTYPE — Invalid Queue Type: the command was sent on the wrong queue type. Wrong group chat 🙈
• NVME_SC_DISCOVERY_RESTART — Discover Restart: the snapshot of the records is now invalid or out of date. Refresh the feed 🌈
• NVME_SC_AUTH_REQUIRED — Authentication Required: NVMe in-band authentication is required and the queue has not yet been authenticated. Show your ID bestie 🪪
• NVME_SC_ZNS_INVALID_OP_REQUEST — Invalid Zone Operation Request: the operation you requested is invalid. This may be because of various conditions, including: attempting to allocate a ZRWA when a zone is not in the ZSE:Empty state, or an invalid Flush Explicit ZRWA Range Send Zone Action operation. Several ways to fail, all valid 💅
• NVME_SC_ZNS_ZRWA_RESOURCES_UNAVAILABLE — ZRWA Resources Unavailable: no ZRWAs are available. Zero. None. 🍓
• NVME_SC_ZNS_BOUNDARY_ERROR — Zone Boundary Error: the command specifies logical blocks in more than one zone. Stay in your lane 🛣️
• NVME_SC_ZNS_FULL — Zone Is Full: the accessed zone is in the ZSF:Full state. 🈵
• NVME_SC_ZNS_READ_ONLY — Zone Is Read Only: the accessed zone is in the ZSRO:Read Only state. 📖
• NVME_SC_ZNS_OFFLINE — Zone Is Offline: the accessed zone is in the ZSO:Offline state. 💤
• NVME_SC_ZNS_INVALID_WRITE — Zone Invalid Write: the write to a zone was not at the write pointer. 📍
• NVME_SC_ZNS_TOO_MANY_ACTIVE — Too Many Active Zones: the controller does not allow additional active zones. 🔥
• NVME_SC_ZNS_TOO_MANY_OPENS — Too Many Open Zones: the controller does not allow additional open zones. 🚪
• NVME_SC_ZNS_INVAL_TRANSITION — Invalid Zone State Transition: the request is not a valid zone state transition. Glow-up denied 🦋
• NVME_SC_WRITE_FAULT — Write Fault: the write data could not be committed to the media. 😭
• NVME_SC_READ_ERROR — Unrecovered Read Error: the read data could not be recovered from the media. Gone gone 💀
• NVME_SC_GUARD_CHECK — End-to-end Guard Check Error: the command was aborted due to an end-to-end guard check failure. 🛡️
• NVME_SC_APPTAG_CHECK — End-to-end Application Tag Check Error: the command was aborted due to an end-to-end application tag check failure. 🏷️
• NVME_SC_REFTAG_CHECK — End-to-end Reference Tag Check Error: the command was aborted due to an end-to-end reference tag check failure. 🔖
• NVME_SC_COMPARE_FAILED — Compare Failure: the command failed because of a miscompare during a Compare command. 😬
• NVME_SC_ACCESS_DENIED — Access Denied: access to the namespace and/or LBA range is denied due to lack of access rights. 🚫
• NVME_SC_UNWRITTEN_BLOCK — Deallocated or Unwritten Logical Block: the command failed because of an attempt to read from or verify an LBA range containing a deallocated or unwritten logical block. Nothing there bestie 👻
• NVME_SC_STORAGE_TAG_CHECK — End-to-End Storage Tag Check Error: the command was aborted due to an end-to-end storage tag check failure. 🎗️
• NVME_SC_ANA_INTERNAL_PATH_ERROR — Internal Path Error: the command was not completed as a result of a controller internal error that is specific to the controller processing the command. It's not you, it's the controller 🫠
• NVME_SC_ANA_PERSISTENT_LOSS — Asymmetric Access Persistent Loss: the requested function (like a command) is not able to be performed as a result of the relationship between the controller and the namespace being in the ANA Persistent Loss state. 💔
• NVME_SC_ANA_INACCESSIBLE — Asymmetric Access Inaccessible: the requested function (like a command) is not able to be performed as a result of the relationship between the controller and the namespace being in the ANA Inaccessible state. 🚪
• NVME_SC_ANA_TRANSITION — Asymmetric Access Transition: the requested function (like a command) is not able to be performed as a result of the relationship between the controller and the namespace transitioning between Asymmetric Namespace Access states. Mid-transition, don't perceive me 🌀
• NVME_SC_CTRL_PATH_ERROR — Controller Pathing Error: a pathing error was detected by the controller. 🛤️
• NVME_SC_HOST_PATH_ERROR — Host Pathing Error: a pathing error was detected by the host. 🛤️
• NVME_SC_CMD_ABORTED_BY_HOST — Command Aborted By Host: the command was aborted as a result of host action. 😶
• NVME_SC_CRD — Mask to get value of Command Retry Delay index 🎭
• NVME_SC_MORE — More bit. If set, there's more status information for this command as part of the Error Information log that may be retrieved with the Get Log Page command. There's always more lore 📜

---

okay and that's still not the whole list bestie, we're literally still going — hold on 💖

• NVME_SC_DNR — bestie this is the Do Not Retry bit and she is very serious about her job 💅. If this bit is set, then if that same command gets re-submitted to any controller in the NVM subsystem, that re-submitted command is expected to fail 😭. No take-backs, no "but I asked nicely", no second chances — the whole NVM subsystem is on the same page about it, fr fr. Like, that command is a flop in every controller's eyes 👑.

---

and that's the whole enum, bestie, we literally ate that entire status field one flag at a time 🍓✨

thanks for staying to the end of this absolute unit of a page, ily 🫶 source/version: enum nvme_status_field, dated July 2026, living in libnvme(2) 💖 go write some slay kernel-adjacent NVMe code 💖