libnvme(9)
π NAME
okay so bestie, gather round: enum nvme_id_ns_nmic β this is the field that literally tells you about multi-path I/O and namespace sharing capabilities of the namespace. it's giving "who gets to be attached to whom" energy and honestly? iconic.
(this whole page lives in the libnvme manual, section 9 β iykyk π«Ά)
β¨ SYNOPSIS β¨
enum nvme_id_ns_nmic {
NVME_NS_NMIC_SHARED
};
like yes, that's the whole enum, and yes, there's exactly one constant in it. we love a minimal queen π
π Constants π
NVME_NS_NMIC_SHAREDβ no cap, if this bad boy is set, then the namespace may be attached to two or more controllers in the NVM subsystem concurrently. shared girlie privileges fr fr πΈ
lowkey important: this is a "may be attached" situation β the flag being set is what unlocks the sharing, so don't sleep on it π¦
and that's the whole vibe check, bestie β¨ this was enum nvme_id_ns_nmic out of the libnvme manual as of October 2026 β go forth and slay your namespace capabilities πππ§
π¦ where this page comes from
- arch rolling: nvme-cli 3.2-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms