Write lifetime hint
A write lifetime hint describes the relative expected time before written data are overwritten or erased, without guaranteeing device placement.
API meaning: SHORT, MEDIUM, LONG and EXTREME are relative classes, not durations in seconds. The Linux manual describes inode hints and open-file-description hints, but imposes no functional guarantee on how storage consumes them. [1]
Version boundary: Linux v6.12 fs/fcntl.c dispatches F_GET_RW_HINT and F_SET_RW_HINT to inode state. It has no F_GET_FILE_RW_HINT or F_SET_FILE_RW_HINT cases, even though those names appear in the manual. Header constants and documentation are not a runtime capability test. [2]
Measured example: On Linux 6.8.0-149-generic, two separately opened descriptors observed the same inode hint. An invalid value returned EINVAL without changing it; both per-file-description commands returned EINVAL. The probe uses one newly created temporary file and records only syscall results and stored values, not physical placement, WAF or endurance. [4]
Practical use: Check the actual command result and trace the filesystem, block layer, driver and device path before claiming that a hint separates NAND writes. A read-back value establishes stored metadata only.
Relations
- related
- Multi-stream SSD, FStream
Citations
- Linux man-pages 6.19: F_GET_RW_HINT(2const), relative lifetime classes
- Linux v6.12 fs/fcntl.c: inode hint accessors and fcntl command dispatch
- Hesela: write-hint syscall observations, 2026-11-16
Further reading
Sources & caveats
- One local API observation on x86_64 with filesystem type 0xef53; this is not a multi-stream SSD experiment.
- The reviewed upstream source is v6.12; the native observation is from the separately identified 6.8 Ubuntu kernel. Do not conflate them.