Shingled Magnetic Recording

SMR

Higher TB per platter when writes are sequential or the stack is SMR-aware; a poor fit for unmanaged random-write pools.

In one minute

SMR increases HDD areal density by writing new tracks partially overlapping previous ones—like roof shingles—so each pass narrows the writable track width. Reads stay random-access, but rewriting a sector often requires reading and rewriting entire shingled bands, so vendors expose SMR through drive-managed firmware or host-visible zoning (ZAC/ZBC).

SMR is a recording layout choice, not a new kind of disk. Platters still spin; heads still fly. The trick is to accept that tracks overlap so you can pack more of them per inch. That bargain only works if writes mostly march forward along a zone, or if firmware hides the shingling from you.

The industry split into three interface personalities. Drive-managed disks pretend to be ordinary drives and garbage-collect in the background. Host-aware disks look like normal disks but expose optional ZAC/ZBC commands for optimization. Host-managed disks are a different device class: the host must respect write pointers or the drive will reject I/O.

That is why SMR drama on forums is rarely about the physics—it is about surprise. A DMSMR disk in a ZFS resilver behaves differently than a CMR sibling. An HM-SMR shelf without zonefs or an SMR-aware object layer will never reach its datasheet happiness. Knowing which model you bought matters more than the acronym on the label.

Compared to neighbors

CMR keeps non-overlapping tracks for predictable random writes. SMR trades rewrite simplicity for density. HAMR/MAMR attack bit-cell size on the media; SMR attacks how tracks are laid out—combinations like HAMR+SMR appear in vendor nearline lines.

Strengths

Higher areal density than CMR on the same mechanical platform — vendors position SMR for capacity-first tiers (Seagate product matrix lists SMR SKUs above many CMR lines).
Standards-based host models — ZAC (ATA) and ZBC (SCSI) define zone commands for host-aware and host-managed drives (SNIA / zonedstorage.io).
Drive-managed SMR can appear as a normal block device — WD documents DMSMR for client/NAS lines that hide zoning from the host.
Strong fit for append-heavy workloads — Seagate and WD both describe archives, object tiers, and sequential media as typical SMR targets.

Limits

Random rewrite cost — overlapping tracks mean in-place updates can trigger read-modify-write across shingled regions (WD SMR white paper).
Host-managed SMR needs zoned software — HM drives reject writes outside the zone write pointer; Linux exposes them as zoned block devices (zonedstorage.io).
Mixed-SKU confusion — consumer NAS lines may ship DMSMR while RAID/ZFS pools expect CMR; WD advises CMR Red Plus/Pro for sustained random rewrite workloads.
Performance variability on drive-managed models — firmware needs idle time for background relocation; sustained random writes without idle can stall (WD support note).

Typical fits

Hyperscale object and backup tiers with append-heavy writers
Large media libraries and compliance archives with infrequent rewrite
Host-managed nearline shelves with zoned filesystems or custom writers
Low-duty-cycle SOHO NAS when vendor documents DMSMR behavior matches the workload

Uncertainty notes

Exact first mass-market SMR SKU dates vary by vendor and region; this card does not state a single global firstSeen year.
Seagate and WD marketing claims about reliability and TCO on SMR pages are vendor-published.

Sources

01Seagate — CMR and SMR hard drive list · accessed 2026-10-06
02Zoned Storage — Shingled Magnetic Recording (SMR) introduction · accessed 2026-10-06
03SNIA — Shingled Magnetic Recording models, standardization, and applications (tutorial) · accessed 2026-10-06
04Western Digital — Shingled Magnetic Recording (SMR) HDD technology white paper · accessed 2026-10-06
05Western Digital — WD Red SMR vs CMR NAS drive information · accessed 2026-10-06
06Seagate Surveillance HDD v2 manual — SMR zones and ZAC commands · accessed 2026-10-06