SMR garbage collection
SMR garbage collection relocates live data to reclaim space or consolidate free tracks while respecting shingled-write constraints.
In drive-managed implementations, cleaning may run during idle periods or interleave with foreground requests. Measuring only post-workload activity can omit cleaning already performed during the run. [5]
A fixed host-write byte threshold does not describe every implementation. Placement locality, mapping resources and cache allocation affect when space must be reclaimed. [4]
Research designs reclaim different resources: Virtual Guard returns protected neighboring tracks from cache to their home bands, while SMaRT consolidates fragmented free tracks. Neither mechanism is fully described as merely draining incoming writes from a cache. [6] [7]
Relations
- related
- Device-managed SMR (DM-SMR), Shingled magnetic recording (SMR), Shingled band, SMR persistent cache, Shingle translation layer, Virtual Guard, SMaRT (SMR translation)
Citations
- Hesela: SMR stalls, cache limits and the errors SMART can miss
- Aghayev et al. Evolving Ext4 for Shingled Disks. FAST 2017, sections 2.1 and 4.3
- Shafaei and Desnoyers. Virtual Guard: A Track-Based Translation Layer for Shingled Disks. HotStorage 2017, sections 2-4
- He and Du. SMaRT: An Approach to Shingled Magnetic Recording Translation. FAST 2017, sections 4-5
Further reading
- SMR garbage collection
- Aghayev and Desnoyers: Skylight, FAST 2015, sections 4.5-4.6
- Zoned Storage: Shingled Magnetic Recording Hard Disks
Sources & caveats
- Evolving Ext4 evaluated four DM-SMR drives from two vendors. Its explanation of one drive's mapping strategy was an inference, not a confirmed universal firmware design.