How Shingled Recording Actually Works
Every hard drive has a fundamental asymmetry between its read and write heads. Flipping the magnetic polarity of a spot on a platter takes a comparatively strong field, so the write head has to be physically wide enough to generate one. Sensing that same spot's polarity to read it back takes far less — modern read heads can be built dramatically narrower than the write head that put the data there in the first place.
Conventional drives — CMR, for Conventional Magnetic Recording — deal with this by spacing tracks apart wide enough that the write head's full footprint fits between them with room to spare. Every track is a fully independent lane. You can rewrite track 400 at 3am without touching track 399 or track 401 at all.
Shingled Magnetic Recording throws that spacing away. Each new track is written so it partially overlaps the track before it, the way each course of shingles on a roof overlaps the course below it. The result is a much narrower effective track pitch, because what actually gets read back is only the sliver of each track that wasn't paved over by its neighbor. Pack the tracks tighter, and more of them fit on the same platter — that's the entire mechanism SMR uses to buy extra capacity for free from the same physical media.
Every track stands alone
Tracks are spaced with a gap wide enough for the write head. Rewriting any single track is a self-contained operation — it never disturbs the tracks on either side of it.
Tracks overlap like shingles
Each track is laid down partially on top of the last one. That's what shrinks the pitch and buys the density — but it also means writing to a track destroys the part of the neighboring track it overlaps, unless something rewrites that whole overlapping run in order.
That last sentence is the entire story of SMR. It is a fantastic trade of write flexibility for density — as long as something, somewhere, respects the order those overlapping tracks have to be written in. Whether that "something" is the drive's own firmware or the host operating system is exactly what the word "managed" refers to, and it's the difference between a drive that behaves and one that quietly ruins your afternoon.
Three Ways an SMR Drive Can Be Managed
"SMR" on a spec sheet doesn't tell you who is responsible for respecting the shingle order. That's a separate axis entirely, and it's the one that actually determines whether the drive is safe to put into your workflow unmodified.
lsblk -o NAME,ZONED reports host-managed or none, and smartctl -a /dev/sdX will usually surface the zoned device model. If neither says "zoned," and it's a spinning drive shipped after roughly 2015, don't assume — a good number of drive-managed models never advertise SMR at all.In 2020, independent testers discovered that several major manufacturers had been quietly shipping drive-managed SMR models inside NAS-branded product lines — without disclosing it on the spec sheet. Owners running RAID and ZFS arrays started seeing rebuilds that should take hours stretch into days, because a rebuild is exactly the sustained-write workload that DM-SMR firmware handles worst. It's the reason "is it actually SMR, and which kind" became a question storage-conscious buyers now ask before every purchase.
Zones, Write Pointers, and the One Rule You Can't Break
On a host-managed drive, capacity isn't one flat address space — it's divided into zones, typically 256MB, each of which is a strict sequential-write region. Every zone has exactly one thing it tracks about itself: a write pointer, marking the next address that's legal to write to. You can append at the pointer. You cannot write anywhere else in that zone. Try, and the drive returns an error instead of touching the platter.
A zone moves through a small number of states over its life, and the entire host-managed contract is about respecting that lifecycle instead of fighting it.
zone_append lands at the write pointer. The zone transitions to Open, and every subsequent write must continue from wherever the pointer now sits — never before it, never after a gap.Notice what's missing from that error: any mention of what went wrong at a higher level, or any attempt by the drive to fix it for you. Host-managed drives don't negotiate. That's the whole point — and it's exactly why nothing should be allowed to write to one without knowing the rule above by heart.
What Goes Wrong When SMR Isn't Managed Properly
Both flavors of SMR fail badly when they're mismatched with the workload sitting on top of them — they just fail in different, equally unpleasant ways.
The Density Payoff: Why Bother With Any of This
Given everything above, it's fair to ask why anyone deals with SMR at all. The answer is that the density gain is real and it's substantial — shingled tracks routinely pack roughly 15–20% more areal density onto the same platters and read/write heads as the conventional drive sitting one generation behind it. Same manufacturing process, same number of platters, meaningfully more usable capacity per drive.
That density gain doesn't move manufacturing cost much — it's largely the same platters, heads, and motor as the CMR sibling. What it moves is cost per usable terabyte, because you're getting meaningfully more terabytes out of roughly the same bill of materials. At the scale of a single desktop drive, that's a modest saving. At archive scale — racks of drives holding hundreds of terabytes or more — it compounds into a real difference in what an archive costs to build and to keep running.
The catch is that this payoff is conditional. You only get to keep the density gain if whatever writes to the drive respects the sequential contract the density was bought with — either by trusting DM-SMR firmware to handle it invisibly (with the risks from the previous section), or by managing the zones properly yourself. That second option is where a system like HuskHoard, which already sits at exactly the right layer to enforce write ordering, earns its keep.
HuskHoard as a Host-SMR Manager
HuskHoard already lives at the seam described in our piece on how the filesystem presents a false picture of where your data really is: a Rust daemon in user space, watching a directory tree via fanotify, deciding what happens the moment something tries to touch a file. That's not a coincidence of architecture — it turns out to be exactly the position you need to occupy to keep an SMR drive happy, without ever having to speak its native zone protocol.
HuskHoard doesn't issue raw SCSI/SATA zone commands or query hardware zones via libzbd at all. Instead, it treats an SMR drive exactly the way it already treats an LTO tape drive: as a target for large, sequential, append-only containers written through the mounted filesystem. Because it never overwrites in place and never needs to, it naturally keeps SMR firmware happy — drive-managed or host-managed — without HuskHoard having to implement a block-level zone manager at all.
This sidesteps both failure modes from earlier in one move, without HuskHoard ever having to write a block-level zone manager. Its tape-like, sequential-only write pattern inherently tames even the cheapest drive-managed disks — it never issues a random write, so it never triggers the DM-SMR performance cliff in the first place. And there's no RAID rebuild disaster waiting to happen, because HuskHoard doesn't put SMR drives behind a block-level RAID controller at all; redundancy is handled at the catalog and volume layer, the same layer that already tracks checksums for tape. Replacing a failed drive means re-migrating the files the catalog says were on it — a controlled, sequential operation, not a monolithic resync that saturates every zone on the replacement drive simultaneously.
Configuring an SMR Archive Pool
SMR pools are configured almost exactly the same way as the tape tiering policies covered previously — a declarative policy, plus a pool of target mount points HuskHoard is allowed to manage exclusively.
Once the policy has run, checking on the pool looks a lot like checking on a tape volume — the catalog already tracks state per unit, it just tracks it per container instead of per physical cartridge.
The density SMR provides was never in question — the physics behind it has been solid for a decade. What decides whether that density is a bargain or a liability is entirely a question of whether the writes hitting the drive ever break the sequential contract. Leave that to firmware you can't see into on a heavy random-write workload, and you inherit a performance cliff at the worst possible moment. Put a daemon that already treats every archive write as a sequential, append-only stream in charge instead, and the density gain is just — free.