Oh I agree with your post, but I was responding to Valmond who used different criteria.
Oh I agree with your post, but I was responding to Valmond who used different criteria.
You can have all three of those, but you won’t get great performance. The Samsung QVO SATA drives are a great example. I wouldn’t use those for an OS drive but they’re fantastic for NAS or media use.
If everything went fine during production you’re probably right. But there have definitely been batches of hard disks with production flaws which caused all drives from that batch to fail in a similar way.
I think the kinks have been worked out. Samsung is on it’s fifth generation of foldables already and Motorola has made multiple as well that haven’t been released in the states. No idea about the custom ROMs though.
Be warned though, some x265 stuff out there, particularly at 1080p and lower, is a reencode of a x264 source file. So lower filesize, but also slightly lower quality. Scene regulations say only higher resolutions should be x265.
Object storage (the S3 API stuff) is the most logical answer here, it’s much simpler and thus more reliable than solutions like Gluster, and the abstraction actually matches your use case. Otherwise something like an NFS share from a central fileserver works too.
But I agree with the other comment that you’re trying to do kubernetes on hard mode and most likely with a worse result.