Hesela / Structured knowledge

Storage Knowledge Corpus

Storage definitions, connected to their evidence.

866 terms · Page 17 of 29

A-Z

  1. Term

    NVMe reclaim unit

    An FDP storage abstraction within a reclaim group that the controller can physically erase independently of other reclaim units.

    JSON

  2. Term

    NVMe reclaim unit handle

    An FDP controller resource that references one reclaim unit in each reclaim group of an endurance group.

    JSON

  3. Term

    NVMe reservation

    An NVMe reservation applies a selected host-access policy to an NVMe namespace.

    JSON

  4. Term

    NVMe reservation persistence

    NVMe reservation persistence determines whether a namespace retains its reservations and registrations across power loss.

    JSON

  5. Term

    NVMe sanitize

    NVMe Sanitize starts a controller-managed sanitization operation using a supported Block Erase, Overwrite or Crypto Erase action.

    JSON

  6. Term

    NVMe Scatter Gather List

    An NVMe Scatter Gather List describes a command's data transfer using typed descriptors for buffers or descriptor segments.

    JSON

  7. Term

    NVMe SMART log

    The NVMe SMART log is the standardized log page containing controller health indicators and cumulative usage, endurance and error counters.

    JSON

  8. Term

    NVMe subsystem NQN

    An NVMe subsystem NQN is the NVMe Qualified Name identifying an NVM subsystem, distinct from a host NQN and from individual namespace identifiers.

    JSON

  9. Term

    NVMe Unexpected Power Losses

    NVMe Unexpected Power Losses is the SMART / Health Information log counter of main-power losses that meet the specification's incomplete-shutdown conditions.

    JSON

  10. Term

    NVMe Warning Composite Temperature Time

    NVMe Warning Composite Temperature Time is a cumulative health-log duration in minutes governed by composite-temperature thresholds and, in supporting revisions and configurations, temperature hysteresis.

    JSON

  11. Term

    NVMe-MI

    NVMe-MI is the NVMe Management Interface specification: it defines a command set and message format for monitoring and managing NVMe SSDs and enclosures out of band over MCTP (on SMBus/I2C, I3C or PCIe vendor-defined messages) and in band through NVMe Admin commands, without using the host data path.

    JSON

  12. Term

    NVMe/FC

    NVMe/FC is the transport binding that carries NVMe capsules and data over Fibre Channel.

    JSON

  13. Term

    NVMe/RDMA

    NVMe/RDMA is an NVMe transport binding that uses reliable RDMA queue pairs for capsule delivery and direct data placement.

    JSON

  14. Term

    NVMe/TCP

    NVMe/TCP is an NVMe transport binding that carries commands, responses and data as protocol data units over TCP connections.

    JSON

  15. Term

    NVMe/TCP digest

    An NVMe/TCP digest is an optional CRC32C error-detection value protecting a protocol data unit's header or data after negotiation at connection establishment.

    JSON

  16. Term

    O_APPEND

    O_APPEND is a file-status flag that combines positioning at the current end of a file with each write as one atomic operation.

    JSON

  17. Term

    O_DSYNC

    O_DSYNC is an open-file status flag requiring write operations to complete with synchronized I/O data integrity, covering data and the metadata needed to retrieve it.

    JSON

  18. Term

    O_SYNC

    O_SYNC is an open-file status flag requiring write operations to complete with synchronized I/O file integrity, covering data and associated file metadata.

    JSON

  19. Term

    O_TMPFILE

    O_TMPFILE is a Linux open flag that creates a regular file without a directory entry in a specified directory's filesystem.

    JSON

  20. Term

    Object lock

    An object lock enforces retention restrictions on a specified object version through a retention policy or hold.

    JSON

  21. Term

    Object storage

    Object storage organizes data as independently addressed objects with associated metadata, accessed through object identifiers or keys rather than a block-device interface.

    JSON

  22. Term

    Object version ID

    An object version ID is a service-assigned identifier used with a bucket and key to select an S3 object version.

    JSON

  23. Term

    Object versioning

    Object versioning retains separately identifiable revisions of an object under the same key.

    JSON

  24. Term

    Oblivious pseudorandom function

    An oblivious pseudorandom function protocol lets a client obtain a keyed function's output while hiding the input from the server and the server key from the client.

    JSON

  25. Term

    Oligonucleotide dropout

    Oligonucleotide dropout is the absence of an intended DNA sequence identity from the reads available for reconstruction.

    JSON

  26. Term

    Open file description

    An open file description is a system-wide open-file object referenced by one or more file descriptors and holding state such as the current file offset and file status flags.

    JSON

  27. Term

    Open NAND block

    An open NAND block is a partially programmed erase block whose remaining pages have not yet completed programming.

    JSON

  28. Term

    Open-channel SSD

    An open-channel SSD exposes media parallelism and placement controls so host software can manage data placement and I/O scheduling.

    JSON

  29. Term

    Open-file-description lock

    An open-file-description lock is a byte-range file lock owned by an open file description rather than by a process.

    JSON

  30. Term

    Open-loop load

    An open-loop load model schedules request arrivals independently of earlier request completions.

    JSON