KVS-RETRIEVE(1)

πŸ“¦ version 0.7.5, in alpine 3.24, epel 9, fedora 43, fedora 44

πŸ’– KVS-RETRIEVE(1) πŸ’–

okay bestie, so this is a page from the xNVMe manual β€” yes, that xNVMe β€” and it's all about a lil command called kvs-retrieve. it's giving "get me my value back" energy and honestly? we're obsessed. let's get into it 🫢


✨ NAME ✨

kvs-retrieve β€” Execute a KV Retrieve Command

like, that's it. that's the whole job. you ask, it retrieves. iconic behavior fr fr πŸ’…


🌸 SYNOPSIS 🌸

kvs retrieve <uri> [<args>]

πŸ¦‹ DESCRIPTION πŸ¦‹

Execute a KV Retrieve Command

(yeah, that's literally all the original says here β€” short and sweet, main character energy, no notes 😌)


πŸ‘‘ REQUIRED πŸ‘‘

these are not optional, bestie. you need these. no skipping, no cap.

  • <uri> β€” the Device URI, i.e. where your device lives. examples include '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', and '\.PhysicalDrive1'. it's the address of the thing you're talking to, periodt πŸ“
  • --key STRING β€” the KV Pair Key. this is the key whose value you're retrieving. the whole point of the operation, honestly. the moment πŸ”‘

🌈 OPTIONAL 🌈

these are the lil extras, the accessories to the outfit. cute but not mandatory ✨

  • [ --nsid 0xNUM ] β€” Namespace Identifier for Command Construction
  • [ --data-output FILE ] β€” Path to data output-file
  • [ --dev-nsid 0xNUM ] β€” Namespace Identifier for Device Handle
  • [ --be STRING ] β€” xNVMe backend, e.g. 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows'
  • [ --admin STRING ] β€” xNVMe admin. command-interface, e.g. 'nvme', 'block'
  • [ --sync STRING ] β€” xNVMe sync. command-interface, e.g. 'nvme', 'block'
  • [ --help ] β€” Show usage / help. your bestie when you're lost, we love a support system πŸ₯Ί
real talk: everything in OPTIONAL is in square brackets in the synopsis for a reason β€” it's optional. the REQUIRED stuff is not. don't get it twisted πŸ’€

πŸŽ€ SEE ALSO πŸŽ€

Full documentation at: <https://xnvme.io/>

go read it, iykyk πŸ“š


πŸ’œ AUTHOR πŸ’œ

Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung


okay that's the whole page, you ate that πŸ“

this was the xNVMe manual, dated 09 September 2024 β€” mwah, bye bestie πŸ’…βœ¨

πŸ“¦ where this page comes from