4 ms·
> SMR does not have a great reputation SMR is fine if you know what SMR is and what you're doing. It might even be fine given a sufficiently advanced translat
by rwmj 6y ago
> SMR does not have a great reputation
SMR is fine if you know what SMR is and what you're doing. It might even be fine given a sufficiently advanced translation layer (which apparently doesn't exist yet). The problem isn't SMR, it's selling a product which uses SMR and hiding that fact from the consumer, and I can't forgive WD for that.
- yjftsjthsd-h 6y ago> It might even be fine given a sufficiently advanced translation layer (which apparently doesn't exist yet). Apparently f2fs does well with it?
- simcop2387 6y agoNot terribly surprising, f2fs and similar filesystems are log-based systems. Rather than overwrite the old data they almost always try to write to the next new area. This ends up working really well for flash technology because writing to existing areas is expensive. You have to read in a 1-4MB area depending on the block size, make your changes to that, erase that area entirely, and then write the changed version. [Those sizes might be a little off but it's what I remember]. Some of that may be hidden by the disk's controller but it has to happen on every write to an area with existing data. SMR is similar in this respect because you have to read, change, and write large blocks together because of the way the tech works. So I'd expect anything that's directly optimized for low level flash memory to work similarly ok performance wise for it. The real problem comes when you can't work like that, in particular this happens when you're low on free space or if you're in a situation where relocating data isn't possible or known that it needs to happen. RAID setups are typically the worst case for this, since they'll effectively treat the entire disk as used and can't relocate data on it. ZFS is a bit more complicated with this but effectively ends up the same.
- deleted 6y ago[deleted]
- m4rtink 6y agoThere have been some experiment with modified XFS using SMR drives natively: https://www.snia.org/sites/default/files/SDC15_presentations/smr/HannesReinecke_Strategies_for_running_unmodified_FS_SMR.pdf https://www.snia.org/sites/default/files/SDC15_presentations... You put the journal and metadata on the continuous part and data on the shingled part, making sure you only ever add to what was written previously in a shingled segment by using copy-on-write. And sporadically you reclaim a segment. This should be much more efficient than a block layer translation layer that knows nothing about the filesystem.
- wegs 6y agoWell, no. SMR is not fine. What this debacle showed, very clearly, is that SMR collapses under some workloads. RAID rebuilds failed. Some took a week, but some just failed. Will my hard drive's workload ever resemble that of a NAS RAID rebuild? Or will there be another workload which breaks SMR drives? Key here is that workloads change, and weird issues like this one lead to compounding failures in emergencies. A system might have an SMR-friendly workload during it's normal operations, but during a cyberattack? When debugging an outage? It's impossible to predict what I'll be doing when the unexpected comes up. Above all else, I want my storage medium to be reliable and to not have issues like this. It's clear SMR drives aren't there yet. Yes, if there was a sufficiently advanced translation layer, or the right abstractions to the OS, SMR might be fine. But the present state-of-the-art of SMR technology is very obviously unsuitable for any application where you care about your data. I'll mention early SSDs were in a similar state many years ago, with wear leveling algorithms. But there was a difference in the level of transparency there.