In this article
NVMe SMART Available Spare is a normalized measure of remaining spare capacity, not filesystem free gigabytes. Read Spare Threshold, Percentage Used and critical warnings separately. These fields answer different operational questions and are not interchangeable.
NVMe SMART Available Spare is a normalized measure of remaining spare capacity, not filesystem free gigabytes. Read Spare Threshold, Percentage Used and critical warnings separately. These fields answer different operational questions and are not interchangeable.
Preserve identity and scope
Record model, appropriately handled serial, firmware, controller/namespace and tool version. Some SMART information is controller-wide, while namespace-specific reporting depends on device capability. Do not merge different scopes into one history. Preserve raw values and units so parser upgrades cannot silently change meaning. Use the installed tool’s documented SMART-log interface; command names and formats can differ across CLI versions.
Separate three percentages
Available Spare represents normalized remaining spare capacity. Spare Threshold supplies the related warning boundary. Percentage Used is a vendor-specific estimate of consumed endurance. Reaching 100 does not necessarily mean immediate failure, and the defined value can exceed 100. None directly reports how much space remains for another model file. Inspect namespaces, block devices, filesystems and quotas separately for logical capacity, retaining their own accounting scopes.
Examine independent states
Suppose a filesystem is nearly full while Available Spare remains high. Deleting temporary cache frees logical space; it does not “refill spare.” Alternatively, logical space may remain available while SMART indicates declining reserve and a warning at its boundary. Removing a directory does not replace device-health assessment. These examples do not prescribe universal replacement thresholds or estimate remaining operating time from one percentage.
| Metric | Question answered |
|---|---|
| Filesystem available | Can the required file be written? |
| Available Spare | What normalized reserve remains? |
| Spare Threshold | Has the stated boundary been crossed? |
| Percentage Used | What endurance consumption is estimated? |
Interpret warnings in context
Compare critical_warning bits, media errors, I/O failures and vendor guidance. Warning fields describe corresponding current conditions rather than replace historical records. Preserve trends and field-support evidence before deciding. Do not convert unsupported values to zero for a green dashboard. Do not run format, sanitize or other modifying operations to “test spare”; this is a read-and-interpret procedure, not destructive restoration guidance.
Preserve separate response plans
For filesystem exhaustion, investigate data placement and storage lifecycle. For health warnings, follow backup and maintenance planning appropriate to artifact importance. Verify that a recovery copy is actually usable. Retain SMART scope, raw fields, filesystem usage and the decision rationale. Another operator can then distinguish freed logical blocks from hardware reserve changes and avoid treating free disk space as proof of NVMe health. Repeat the record after firmware or monitoring-tool changes so missing support is not mistaken for a sudden improvement in the device.
Related operational reading: nvme for model serving; storage optimized hosting.