3 ms·
You don't need a single Log structure -- the shingle stripes are on the order of 128 MB of or so. Any CoW filesystem can relatively easily adapt to this kind o
by loeg 7y ago
You don't need a single Log structure -- the shingle stripes are on the order of 128 MB of or so. Any CoW filesystem can relatively easily adapt to this kind of system; in-place filesystems are basically boned on SMR. The CoW filesystem aren't going to be fast on SMR, mind you, just not quite as awful.
- seized 7y agoExcept filesystems like ZFS are having issues on these SMR Reds during resilvers (rebuilds) because SMR slows down so much.
- Dylan16807 7y ago"Can relatively easily adapt" is not the same as "has already been adapted". It still performs awfully without the work put in to make the hardware and software cooperate, but doing that work is not nearly as big of a burden.
- loeg 7y agoToast0's great-grandparent comment (and my grandparent comment) are talking about Host-managed SMR, not "transparent" drive-managed SMR like these fraudulent WD Reds. Yes, nothing except extremely low load or extremely linear (i.e., security video / tape-style backup) workflows works well with drive-managed SMR.
- ngcc_hk 7y agostorage drive recycle after certain period and hence it is good for the first write but after that as those (and then as which support it) would need to assume low load environment. May be ok, just if we can tell we can test.
- londons_explore 7y agoI believe these SMR drives don't allow direct access to "write a block here". They try to write your writes to a staging area first, and them move them later. The SATA/SCSI spec, together with operating systems, block device interfaces, and filesystems, would all need to be updated to have more parameters to correctly handle SMR drives properly. Since hard drives are going out of fashion and architectural changes like that will take 5+ years to be widely deployed, it's never going to happen.
- loeg 7y agoHost-managed SMR came first. When it wasn't being adopted because it sucks, drive-managed SMR like the crap WD is selling as Reds came about. SCSI and SATA and operating systems already have support for host-managed SMR — the name used in this context is "ZONE" and those changes happened around 5+ years ago. https://zonedstorage.io/introduction/smr/#scsi-standard-zbc https://zonedstorage.io/introduction/smr/#scsi-standard-zbc
- Dylan16807 7y ago> They try to write your writes to a staging area first, and them move them later. If a zone is empty, and you try to write sequentially to it, I would sure hope the firmware isn't so hopelessly dumb as to redirect that data to a staging area. This does require that they don't disable TRIM support, I guess. I'd really like to see some detailed analysis of how these drives perform.
- loeg 7y agoYou'd need a filesystem that was pretty careful to write a very large chunk extremely sequeuntially. That's easiest with Host-aware SMR (to have some idea the size of the zones) or a linear LogFS.
- Dylan16807 7y agoYes, I agree entirely. But the point I'm making is that "host-aware" should be good enough for this type of use. Even though it's still drive-managed, the internal logic in the drive should pass through certain write patterns without interference. And you can make the host aware through feeding in a few parameters; it doesn't necessarily have to interrogate the drive. In other words, I'm disagreeing with the idea that this big laundry list of things would need to be updated. The filesystem should be sufficient if these drives act in a way that's at all reasonable.
- loeg 7y agoAh, maybe. It’s not a big step from aware to managed, though. The zoned api is actually quite simple: what are the zones?, open zone, finish zone. The filesystem that’s tolerant of these characteristics is the hard part.