4 ms·
" In SMR, unlike conventional recording, tracks are written in an overlapping manner. ... once the tracks are overlapped, they cannot be written independently.
by h2odragon 7y ago
" In SMR, unlike conventional recording, tracks are written in an overlapping manner. ... once the tracks are overlapped, they cannot be written independently. there are disadvantages for device-side localized management. ... Managing the complexity on the host side is almost a requirement"
also links: https://www.zonedstorage.io/ https://www.zonedstorage.io/ for further information.
Sounds good to me; exposure of the actual mechanisms instead of outdated abstractions makes sense. I'd even argue for open access to motor controllers and raw signal buffers but apparently I'm insane.
- josefbacik 7y agoHost managed also means messing with the file system, and the patch set for btrfs is not small. Plus you have to disable a bunch of features (like preallocation since you can’t move the write pointer backwards) which is going to surprise people in unfun ways. These drives are useless for general purpose. If you are going to use them as expensive tape then by all means, but otherwise I have serious doubts about their usefulnes. Edit: I’m talking specifically about the SMR side. The general zoned stuff is interesting, but when you start putting restrictions on how you can write to certain zones you wind up with a lot of weirdness that application developers are going to be surprised by.
- rzzzt 7y agoDrive-managed SMR looks OK to me for general use, although I don't have hands-on experience with it. They also have a non-shingled region that can accept random I/O at higher speeds, and the drive deals with moving data to a linear-only region once it fills up, or at garbage collection time. It's very much like the QLC drives where a portion is treated as SLC/MLC.
- josefbacik 7y agoAgreed, drive managed is far better from a usability standpoint.
- loeg 7y agoIt's like the QLC drives with SLC/MLC cache (e.g., Intel 660p) except the performance cliff is far, far worse (and obviously the "fast" mode is far worse as well).
- deleted 7y ago[deleted]
- amelius 7y ago> If you are going to use them as expensive tape then by all means, but otherwise I have serious doubts about their usefulness. Only writing is more complicated. Reading is still simple and fast; and random access reading is fast, unlike tape.
- the8472 7y agoSome of the fallocate modes don't make much sense on CoW filesystems anyway. ZoL doesn't support preallocation either, you have to use FALLOC_FL_PUNCH_HOLE. Lack of DIO might be a bigger issue. Then again it's often used by write-heavy workloads which probably don't want to use SMR drives anyway.
- nine_k 7y agoExpensive but very fast tape with easy random rewind, but still largely sequential write access, is something that spark / hadoop could readily use.
- DoctorOetker 7y agoI totally agree, how on earth could being given optional access to lower level functionality ever be considered a negative?
- pjc50 7y agoIt makes it much easier to accidentally break something, and much harder to swap out the implementation for a better but different one?