NVME-FEAT-HOST-BE(1)

πŸ“¦ version 3.2, in arch rolling

πŸ’… NVME-FEAT-HOST-BE(1) β€” nvme-feat-host-behavior-support πŸ’…

okay bestie, welcome to the nvme-feat-host-behavior-support page, from the NVMe Manual ✨ this is the one that grabs and sets the host behavior support feature πŸŽ€


✨ NAME ✨

nvme-feat-host-behavior-support β€” get and set the host behavior support feature, no cap 🫢


🌸 SYNOPSIS 🌸

nvme [<global-options>] feat host-behavior-support <device>
                        [--acre=<acre> | -a <acre>]
                        [--etdas=<etdas> | -e <etdas>]
                        [--lbafee=<lbafee> | -l <lbafee>]
                        [--hdisns=<hdisns>]
                        [--cdfe=<cdfe> | -c <cdfe>]
                        [--sel=<select> | -S <select>] [--save | -s]

πŸ¦‹ DESCRIPTION πŸ¦‹

Get and set the host behavior support feature. That's the whole vibe πŸ’«

The <device> parameter is mandatory β€” like, you literally cannot skip it, bestie 😭. It can be either the NVMe character device (ex: /dev/nvme0), or a namespace block device (ex: /dev/nvme0n1).

So here's the tea β˜•: if you specify any of the setting options (--acre, --etdas, --lbafee, --hdisns, or --cdfe), the command will update the host behavior support feature fields accordingly. But if none of these options are specified, it will just retrieve and display the current configuration β€” a little read-only moment πŸ‘‘.

On success it returns 0, and an error code otherwise. periodt.


πŸŽ€ OPTIONS πŸŽ€

  • -a <acre>, --acre=<acre> β€” Advanced Command Retry Enable (0 or 1). iconic little toggle πŸ’…
  • -e <etdas>, --etdas=<etdas> β€” Extended Telemetry Data Area 4 Supported (0 or 1).
  • -l <lbafee>, --lbafee=<lbafee> β€” LBA Format Extension Enable (0 or 1).
  • --hdisns=<hdisns> β€” Host Dispersed Namespace Support (0 or 1). yes, this one has no short flag, she's independent like that πŸ™ˆ
  • -c <cdfe>, --cdfe=<cdfe> β€” Copy Descriptor Formats Enable bitmask.
  • -S <select>, --sel=<select> β€” Select (SEL): this field specifies which value of the attributes to return in the provided data:
    • 0 β†’ current β†’ Current
    • 1 β†’ default β†’ Default
    • 2 β†’ saved β†’ Saved
    • 3 β†’ supported β†’ Supported capabilities
  • -s, --save β€” Save the attribute so that it persists through all power states and resets. she stays saved, fr fr πŸ’–

🌈 GLOBAL OPTIONS 🌈

The following options are defined at the top-level nvme command and are available to this subcommand β€” they're like the main character energy that trickles down to everybody ✨

  • --dry-run β€” Print the command that would be executed, but do not actually execute it. manifesting without acting 🧚
  • --no-ioctl-probing β€” Disable probing for 64-bit IOCTL support.
  • --no-retries β€” Disable retry logic on transient errors.
  • -o <fmt>, --output-format=<fmt> β€” Set the reporting format to normal, tabular, json, or binary. Only one output format may be used at a time β€” pick one, bestie, you can't have all four 😭
  • --output-format-version=<version> β€” Select the output format version. Version 1 uses the original field naming, while version 2 (default) provides more consistent and script-friendly field names. Other versions are rejected πŸ’€
  • --quiet β€” Suppress informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. the way it shuts --verbose down entirely, obsessed 🫢
  • --set-options=<key=value>[,<key=value>...] β€” Set libnvme library options for this invocation. Supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir.
  • --timeout=<ms> β€” Set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). no clock, no problem ⏳
  • -v, --verbose β€” Increase the level of detail in the output. May be specified multiple times to further increase verbosity. stack 'em like bracelets πŸ’«
These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file β€” CLI stays on top, as she should πŸ‘‘

πŸ”₯ EXAMPLES πŸ”₯

  1. Has the program issue a feat host-behavior-support to get the current configuration:
# nvme feat host-behavior-support /dev/nvme0
  1. Has the program issue a feat host-behavior-support to set fields with saving enabled:
# nvme feat host-behavior-support /dev/nvme0 --acre=1 --lbafee=1 --save

πŸ‘‘ NVME πŸ‘‘

Part of the nvme-user suite. you're in the family now 🫢


alright that's the whole page bestie, go forth and feature-set responsibly πŸ’–βœ¨πŸŽ€ this little number is from the NVMe Manual, dated 10/30/2026 β€” version info straight from the source, no edits, iykyk πŸ¦‹πŸ’…

πŸ“¦ where this page comes from