NVME-TOSHIBA-VS-I(1)

📦
version 3.2 · 14 versions
, in arch rolling

✨ NVME-TOSHIBA-VS-I(1) ✨

okay so this is a page from the NVMe Manual — hi bestie, welcome 💅 this one's all about nvme-toshiba-vs-internal-log, and yes it's a mouthful, we love her anyway 🎀

🌸 NAME 🌸

nvme-toshiba-vs-internal-log — the vibe here is: go grab a Toshiba device's vendor-specific internal log, and then either save it to a file or just dump the whole thing out. that's it, that's the job 🫶

🦋 SYNOPSIS 🦋

nvme [<global-options>] toshiba vs-internal-log <device>
                        [--output-file=<FILE>, -O <FILE>] (optional)
                        [--saved-log, -s] (optional)

💖 DESCRIPTION 💖

okay so you give it an NVMe device, and it sends off the Toshiba internal device log request. then it either saves the result to a file or dumps the content to stdout. pick your fighter ✨

the <device> parameter is literally mandatory, no skipping it babes — and it can be either the NVMe character device (like /dev/nvme0) or a namespace block device (like /dev/nvme0n1) 🧚

the log is associated with the controller, not with any namespaces. important distinction, iykyk.

there are two logs — the current log and the previous log. two icons, both iconic 💅

⚠️ this will only work on Toshiba devices that support this feature. no cap, if your device isn't one of those, it's a no from her.
💀 heads up bestie: the logs are quite large — typically 100's of MB. like, huge. this command can take several minutes to complete 😭 a progress runner is included when data is written to file, and a page count is included in the stdout dump. she's thorough.

🎀 OPTIONS 🎀

  • -O <FILE>, --output-file=<FILE> — output binary file. defaults to text-formatted dump to stdout 📄
  • -p, --prev-log — use the previous log contents instead. defaults to the current log contents 👑

🌈 GLOBAL OPTIONS 🌈

these ones live at the top-level nvme command and are available to this subcommand too, so they're kinda like the group chat everyone's in 🫶

  • --dry-run — print the command that would be executed, but do not actually execute it. fake it till you make it, but like, on purpose 🙈
  • --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 ⭐
  • --output-format-version=<version> — select the output format version. version 1 uses the original field naming, while version 2 (the 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 🤫
  • --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) ⏳
  • -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity 🗣️

these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file — flag wins, periodt 👑

🔥 EXAMPLES 🔥

  1. get the current log from the device and dump it to stdout:
# nvme toshiba internal-log /dev/nvme0
  1. get the previous log from the device and save to a binary file:
# nvme toshiba internal-log /dev/nvme0 --output-file=log.bin --prev-log

👑 NVME 👑

part of the nvme-user suite. she runs with a whole crew 💜

and that's the whole page bestie!! 🌸 this was NVMe manual material dated 10/30/2026 — mwah, go log something huge 🦋✨

📦 where this page comes from