What Makes UltraSMR Different?

(blog.westerndigital.com)

16 points | by bluedino 3 days ago ago

17 comments

  • ejiblabahaba 2 hours ago

    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.

    • undersuit an hour ago

      SMR drives are the worst, even had issue resilvering a 2TB mirror.

      What's frustrating is even just a little info from the manufactures would be beneficial, like the size of a shingle so the computer could batch writes, or even if the drive is shingled!

      • ejiblabahaba 26 minutes ago

        That's why libzbc exists. Host-aware and host-managed SMR give you the tools to optimize I/O around the batching needed. It doesn't change the fundamental outlook - you still have to organize writes in these huge blocks and do some math to figure out the best timing to commit cache to re-writes - but it's at least a tractable problem compared to chucking everything over the wall with device-managed SMR.

        In any case, I don't think hobbyists get to play with the non-disk-managed drives, and anyone with the money and the special disks is probably not using ZFS because it's a bit of an uphill battle to fit SMR to a copy-on-write filesystem.

        • p_l 12 minutes ago

          Handling SMRs well probably would require a custom replacement for SPA (block layer) component in ZFS, talking directly with DMU (object storage).

          Could also expose the drives as SCSI object storage devices

      • fmajid 35 minutes ago

        And all of that for a pretty paltry gain in capacity.

    • accrual an hour ago

      I read a nice write-up of Dropbox's use of SMR drives here:

      https://dropbox.tech/infrastructure/four-years-of-smr-storag...

    • dist-epoch 13 minutes ago

      When SSDs appeared, many filesystems performed badly on them, or degraded them much more quickly than needed, because they were not SSD-aware. It took a while to fix the issues, add TRIM, etc.

      Sounds like ZFS has the same problem today, it's not aware of SMR, and it treats those drives as if they are regular hard-drives.

  • creatonez 2 hours ago

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

    • addaon 17 minutes ago

      Which also makes it super clear that the intended use case is customers willing to use SMR-aware software to get a generation or two of density-per-bay improvement, not folks trying to jam it into current workflows.

    • shadowpho 2 hours ago

      Thanks. Looks like SMR drives will get a bit more dense, but with the same limitations as before — no update in place without bunch of rewriting.

      Means they are still bad in RAID setups

      • dcan 2 hours ago

        Host-Managed SMR is a good middle-ground, but the file system support is still poor.

        • fc417fc802 9 minutes ago

          Exactly. I already use a CoW filesystem so SMR ought to be a non-issue but last I checked the software side of things wasn't ready yet.

      • dist-epoch 11 minutes ago

        Hardware-RAID doesn't make sense for more than 10 years now.

  • londons_explore 2 hours ago

    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.

    • kvemkon an hour ago

      > any writes that happened before a power failure can always be completed

      It can be also the data milliseconds after loosing power. The minimal amount of data in question is the data that the drive has acknowledged to the OS after a special command.

      Anyway, this problem is already solved at least few years ago.

  • loeg 14 minutes ago

    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.

  • formerly_proven an hour ago

    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.