4 ms·
It's also interesting that nobody implements CKD on storage devices. This complexity runs on a massive POWER AIX box in IBM's storage systems, or in a similar
by kev009 7y ago
It's also interesting that nobody implements CKD on storage devices. This complexity runs on a massive POWER AIX box in IBM's storage systems, or in a similar commodity powerhouse running UNIX or an RTOS in similar arrays of the past couple decades.
You have a comparatively weak CPU (think ARM Cortex M series) on an SSD and drive companies have been notoriously bad at firmware development.
Frankly, I don't trust Samsung to implement a file system. I prefer to not even use their enterprise flash based on past trauma, but those are usually harder fails than the subtle fuckups they can pull off in an opaque FS.
- ClumsyPilot 7y agoYou already are using a translation layer in the SSD, most SSDs have wear levelling, error correction, compression, etc. What your OS things it's writing to disk is very different to what ends up stored in the flash chips. I think your are fighting yesterday's war.
- kev009 7y agoFighting opaque and unsupportable complexity will always be the current war in technology.
- theamk 7y agoThat is exactly the reason I am using ZFS for important data -- one should not really trust the storage devices to be fully reliable. Is is a real pity that so few filesystems systems have integrated data checksumming -- I'd love to use something other than ZFS for this.
- Beltiras 7y agoSSDs are not the only storage device that lies about these things. Just about the only one that doesn't is tape, and I'm not even sure about those.