I wonder how difficult it would be to build an S3 like interface on top of this so you can get a coarse pay-for-what-you-use, avoid downtime, but also have a much larger capacity than the max of 10TB for one drive.
You might be able to build this on top of minio. Start with, say, 4 1GB linodes (smallest), with 8 volumes each (the max) of the smallest volume size of 10GB, and a somewhat low 1:3 parity in minio (redundancy is mostly handled by linode replication). That would be 320GB * $0.10 + 4 * $5 = $52/mo to start with. After some utilization threshold, incrementally resize all drives to grow dynamically, the parity drives would fill in while a drive is offline & resizing. The parity is also enough to resize the linodes one at a time too if you need to up their compute capacity. This system could grow up to 320 TB raw / 240TB accessible.
The last I poked around at this idea when linode block storage was introduced, this "should" work with minio, but I got the impression they didn't really consider this kind of use case.
If you run it at a higher level of abstraction than linode volumes with parity and can tolerate up to 8 drives / 1 server going down at once (like this setup on minio should get you), that would take you a long ways towards adding one or two 9's.
High availability is just one S3 feature though. Other important features are paying for what you use, and effectively unlimited storage growth (you will probably revisit this before you hit $32k/mo the 320TB would cost). Even if this didn't add reliability, those other features still have utility above the raw Block Storage Volumes provided by linode here.
You might be able to build this on top of minio. Start with, say, 4 1GB linodes (smallest), with 8 volumes each (the max) of the smallest volume size of 10GB, and a somewhat low 1:3 parity in minio (redundancy is mostly handled by linode replication). That would be 320GB * $0.10 + 4 * $5 = $52/mo to start with. After some utilization threshold, incrementally resize all drives to grow dynamically, the parity drives would fill in while a drive is offline & resizing. The parity is also enough to resize the linodes one at a time too if you need to up their compute capacity. This system could grow up to 320 TB raw / 240TB accessible.
The last I poked around at this idea when linode block storage was introduced, this "should" work with minio, but I got the impression they didn't really consider this kind of use case.