Hesela / Structured knowledge
Storage Knowledge Corpus
Storage definitions, connected to their evidence.
866 terms · Page 3 of 29
A-Z- JSON
Brier score
For a binary event, the Brier score is the mean squared difference between each forecast probability and its observed zero-or-one outcome.
- JSON
Btrfs filesystem du
A Btrfs command that uses FIEMAP to report extent usage and sharing for selected files and directory trees.
- JSON
Btrfs NODATASUM
Btrfs NODATASUM marks file data as excluded from the filesystem's data checksumming.
- JSON
Btrfs read-only subvolume
A Btrfs read-only subvolume is a subvolume whose ro property prevents modification of its file contents and directory hierarchy.
- JSON
Btrfs received UUID
A Btrfs received UUID is a subvolume metadata field recording the source subvolume identity associated with a received replication stream.
- JSON
Btrfs send stream
A Btrfs send stream is a versioned sequence of commands describing a subvolume or changes needed to reconstruct it from existing state.
- JSON
Btrfs tree log
The Btrfs tree log is a per-subvolume recovery structure that can persist file or directory changes for fsync without a full filesystem transaction commit.
- JSON
Bubble memory
Bubble memory is nonvolatile storage that represents bits by the presence or absence of movable cylindrical magnetic domains in a thin magnetic film.
- JSON
Buffered I/O
Buffered I/O is file access through an operating-system cache, allowing transfers between an application and storage to be decoupled.
- JSON
Buffered upsert
A buffered upsert encodes a deferred transformation of a key's value without first fetching that value.
- JSON
Byte hit ratio
Byte hit ratio is the fraction of requested payload bytes served from a cache under a stated request-accounting rule.
- JSON
Byte-addressable storage
Byte-addressable storage exposes individual byte locations rather than only block-sized addresses, without by itself specifying atomicity or durability.
- JSON
Cache admission
Cache admission is the decision to retain a fetched item in a cache or cache segment rather than bypass it.
- JSON
Cache inclusion property
The cache inclusion property requires the resident set at a smaller capacity to be contained in that at a larger capacity after each shared request prefix under the same replacement policy.
- JSON
Cache pollution
Cache pollution occurs when cached data displaces other data whose retention would provide greater benefit to the workload.
- JSON
Cause-specific hazard
A cause-specific hazard is the instantaneous rate of one event type among units still free of all modeled first events.
- JSON
CD block error rate (BLER)
CD BLER counts blocks containing detectable errors per second at the input to the C1 decoder.
- JSON
Chain replication
Chain replication orders replicas so that updates enter at a head, propagate along the chain and complete at a tail that also serves queries.
- JSON
Charge trap flash
A flash cell design that stores charge in localized traps within an insulating material rather than on a conductive floating gate.
- JSON
Checkpoint starvation
Checkpoint starvation is sustained inability to finish or reset a database log checkpoint because the required progress conditions keep being obstructed.
- JSON
Chunk fragmentation
Chunk fragmentation is the dispersion of chunks needed by a deduplicated restore across storage containers or an order poorly matched to the restore sequence.
- JSON
Class prevalence
Class prevalence is the proportion of observations belonging to a specified class in a defined population or evaluation sample.
- JSON
Clear sanitization
Clear sanitization uses logical operations across all user-addressable storage locations to resist simple, non-invasive recovery through the device interface available to the user, such as the host interface.
- JSON
CLOCK cache replacement
CLOCK is a cache replacement policy that gives referenced entries another chance by clearing their reference state during an eviction scan.
- JSON
Close-to-open consistency
Close-to-open consistency is a file-sharing cache policy that combines writeback at close with validation at a later open to support visibility of updates between sequential users.