static-wear-leveling · shipping · also static wear levelling

Static wear leveling

Static wear leveling relocates infrequently updated data so that lightly worn occupied flash blocks can return to the write-allocation pool.

Related Observatory article: Static wear leveling on hesela.com

Linux UBI illustrates migration from a less-erased used block to a more-erased free block; this is distinct from bit-flip scrubbing. [1]

The destination must still satisfy retention needs. Persistent code placed in blocks near their wear limit can lose retention margin. [2]

Relocation adds flash writes; cold here describes update frequency, not temperature. [3]

OBP, DP and PWL are the static policies evaluated in Jiao and Yang's 2025 extension. That evaluation excludes dynamic wear leveling, so it cannot establish that every dynamic policy has the same tradeoffs. [5]

Relations

related
Wear leveling, Dynamic wear leveling, Flash translation layer (FTL), Flash data retention, Write amplification

Citations

  1. Linux UBI wear-leveling implementation, introductory comments (pinned source revision). (accessed 2026-10-18)
  2. Macronix. Wear Leveling in NAND Flash Memory. AN0289, revision 1, March 10, 2014, p. 2. (accessed 2026-10-18)
  3. Jiao, Bhimani and Kim. Wear Leveling in SSDs Considered Harmful. HotStorage 2022, sections 1-2. DOI 10.1145/3538643.3539750. (accessed 2026-10-18)
  4. Jiao and Yang. Wear Leveling in SSDs Considered Harmful: A Case for Capacity Variance. Electronics 14, 4169 (2025), sections 3-5. (accessed 2026-10-18)

Further reading

  1. Hesela: Wear Leveling, mechanisms and tradeoffs (accessed 2026-10-18)

JSON: /data/terms/static-wear-leveling.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Static wear leveling. Hesela. 2026-10-18. https://hesela.dev/terms/static-wear-leveling/