nvmet.namespace.create¶
Create a NVMe target namespace in a subsystem (subsys).
This will expose the namespace to any hosts permitted to access the subsystem.
No Additional Items
Tuple Validation
Parameter 1: nvmet_namespace_create
nvmet_namespace_create
Type: objectNVMe-oF namespace configuration data for creation.
No Additional PropertiesNsid
Default: nullNamespace ID (NSID).
Each namespace within a subsystem has an associated NSID, unique within that subsystem.
If not supplied during namespace creation then the next available NSID will be used.
Value must be greater or equal to 1 and strictly lesser than 4294967295
Device Type
Type: enum (of string)Type of device (or file) used to implement the namespace.
Must be one of:
- "ZVOL"
- "FILE"
Device Path
Type: stringNormalized path to the device or file for the namespace.
Must be at least 1 characters long
Filesize
Default: nullWhen device_type is "FILE" then this will be the size of the file in bytes.
Enabled
Type: boolean Default: trueIf enabled is False then the namespace will not be accessible.
Some namespace configuration changes are blocked when that namespace is enabled.
Subsys Id
Type: integerID of the NVMe-oF subsystem to contain this namespace.
NVMetNamespaceEntry
Type: objectThe created NVMe-oF namespace configuration.
No Additional PropertiesId
Type: integerUnique identifier for the NVMe-oF namespace.
Nsid
Default: nullNamespace ID (NSID).
Each namespace within a subsystem has an associated NSID, unique within that subsystem.
If not supplied during namespace creation then the next available NSID will be used.
Value must be greater or equal to 1 and strictly lesser than 4294967295
NVMe-oF subsystem that contains this namespace.
Device Type
Type: enum (of string)Type of device (or file) used to implement the namespace.
Must be one of:
- "ZVOL"
- "FILE"
Device Path
Type: stringPath to the device or file being used to implement the namespace.
When device_type is:
- "ZVOL":
device_pathis e.g. "zvol/poolname/zvolname" - "FILE":
device_pathis e.g. "/mnt/poolmnt/path/to/file". The file will be created if necessary.
Must be at least 1 characters long
Dataset
The ZFS dataset containing the file-based namespace (e.g., 'tank/nvmet'). Returns null for ZVOL-based namespaces or if the FILE path cannot be resolved yet (encrypted dataset not unlocked, etc.). This is a read-only field automatically populated from "device_path".
Relative Path
The path of the file-based namespace relative to the dataset mountpoint (e.g., 'namespaces/ns1.img'). An empty string indicates the file is at the dataset root. Returns null for ZVOL-based namespaces or if the path cannot be resolved yet. This is a read-only field automatically populated from "device_path".
Filesize
Default: nullWhen device_type is "FILE" then this will be the size of the file in bytes.
Device Uuid
Type: stringUnique device identifier for the namespace.
Must be at least 1 characters long
Device Nguid
Type: stringNamespace Globally Unique Identifier for the namespace.
Must be at least 1 characters long
Enabled
Type: boolean Default: trueIf enabled is False then the namespace will not be accessible.
Some namespace configuration changes are blocked when that namespace is enabled.
Locked
Reflect the locked state of the namespace.
The underlying device_path could be an encrypted ZVOL, or a file on an encrypted dataset. In either case locked will be True if the underlying entity is locked.
Required roles: SHARING_NVME_TARGET_WRITE