What Makes UltraSMR Different?

23 points28 comments3 days ago
Telaneo

I want to like SMR disks, but WD pushing SMR disks into product lines where it doesn't belong, and the disks not being host-aware makes actually using them a losing proposition. Not to mention that SMR disks often aren't actually cheaper than equivalent CMR disks, at least in the consumer channels (the opposite is almost certainly the case in B2B, but I don't care about that).

If the disks were host-aware, Linux (and preferably ZFS) could handle host-aware SMR disks non-catastrophically, and SMR disks were part of a separate product line with prices and capacities that make some sort of sense when you compare with the CMR line, I'd be all over them as cold storage, or just treating them as (re)write-once-read-many drives.

But it's clear WD and Seagate don't care about the consumers. They're just a rounding error in comparison to B2B sales, especially given the current times.

ejiblabahaba

As a relatively unserious data hoarder with a ZFS NAS, SMR drives are unusable, and are famous for resilver times ranging from weeks to never (drive times out). I'm sure there are workloads where they make sense (maybe archiving huge binary blobs). A while back Dropbox was using mostly SMR drives, so maybe the firmware and software ecosystem available for enterprise use cases is more approachable than I thought. And with the AI-driven price explosion for storage, perhaps the total cost of ownership even with the software investment starts to make sense.

show comments
creatonez

I could only find an explanation of what it actually is here: https://documents.westerndigital.com/content/dam/doc-library...

show comments
numpad0

THE issue with SMR is that they use designated area on the disk on the same head as disk as staging area.

They do like "ls /sda0/dirty-tracks/ | xargs -P 1 dd if=/sda0/dirty-tracks/{} of=/dev/sda{} size=512M && rm /sda0/{}", but onboard the disk, not on the host, and that's both wildly slow and imcompatible with anything but super light or niche use cases.

If only they at least used a NAND flash for that staging or at least coordinated with the host system, but no, HDD industry chose not to cooperate with anyone and to hide the fact that some disks are DM-SMRs.

show comments
loeg

More capacity density, if you completely ignore IO density. But many HDD workloads were already IO bound, and SMR is much, much worse. (HDD vendors won't sell CMR to hyperscalers anymore -- it's like they are trying to get us to buy QLC flash instead of their products.)

Think of SMR as "fast tape with random reads" rather than anything like a CMR product.

londons_explore

I think the future of hard drives involves absolutely huge error correction block sizes - 1 gigabyte or more.

The way it would work is:

* The underlying disk would do sequential writes only, in 1Gb blocks, rather like a log filesystem.

* The large block size enables much better information density due to being able to tolerate far more errors.

* Random reads within blocks can usually be done - but occasionally most or all of the whole block will need to be read to decode the data.

* A small capacitor+disk momentum ensures any writes that happened before a power failure can always be completed - either to the real disk or to flash.

* The OS still only sees 4k pages - versioning, packing those into 1Gb blocks, mappings and garbage collection are all handled inside the drive.

show comments
skibbityboop

SMR is honestly just an "avoid at all costs" technology, abysmal performance in any application.

formerly_proven

Has Western Digital found yet another way to further degrade the performance of their drives beyond their initial deployment of OptiNAND and SMR? At this rate the tail latency of a tape robot is going to outperform WD spinning rust.