host-managed-band · shipping · also host-managed zone, sequential write required zone

Host-managed band (SMR)

In host-managed shingled recording, the host tracks each sequentially written band, called a zone in the standards, and must write it strictly at its write pointer.

A host-managed zoned block device reports peripheral device type 14h, must support sequential write required zones and may add conventional and sequential write preferred zones. A host-aware device reports 00h and must not support sequential write required zones. [2]

Writes to a sequential write required zone must start at its write pointer and end on a physical-block boundary, or fail with UNALIGNED WRITE COMMAND. A write crossing the zone end gets WRITE BOUNDARY VIOLATION, and a read at or past the pointer gets ATTEMPT TO READ INVALID DATA. Writing the last LBA makes the zone FULL, only a write pointer reset makes an invalid pointer valid, and after a failed write the pointer may be unknown to the host. [2]

Linux describes each zone by 64-bit start, length, write pointer and capacity, a type and one of eight conditions, from empty and open to full, read-only and offline. [4] Sequential zones accept random reads but no overwrite until reset. In one example a 15 TB host-managed SMR disk with 256 MB zones yields 55,356 sequential-zone files and a 140,391,743,488-byte conventional file, or 523 conventional zones of 256 MiB. [3]

Relations

related
Host-managed SMR (HM-SMR), ZBC, ZAC, Zoned block device (ZBD), Zone write pointer, Zone Reset, Zone capacity, Zone Finish

Citations

  1. Zoned Block Commands (ZBC), T10/BSR INCITS 536 Revision 1, working draft (accessed 2026-10-16)
  2. ZoneFS - Zone filesystem for Zoned block devices, Linux kernel documentation (accessed 2026-10-16)
  3. include/uapi/linux/blkzoned.h, Linux kernel source (accessed 2026-10-16)

Further reading

  1. Host-managed band (SMR) (accessed 2026-03-26)
Sources & caveats
  • c2 is ZBC revision 1, a T10 working draft (May 2014) with open editor's notes, not the approved standard; it does not use the word band or mention SMR.
  • The link between zones and SMR media comes from Linux documentation (c3).
  • No cited source gives the capacity gain, performance or cost of host-managed SMR.
  • Arithmetic: 140,391,743,488 / 268,435,456 = 523 conventional zones; 523 + 55,356 = 55,879 zones.

JSON: /data/terms/host-managed-band.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Host-managed band (SMR). Hesela. 2026-10-22. https://hesela.dev/terms/host-managed-band/