3 ms·
But we've had disk quotas before that mostly worked? If anything it seems an easier problem than processor time. I recall disk quotas on shared systems at uni
by AngusH 6y ago
But we've had disk quotas before that mostly worked?
If anything it seems an easier problem than processor time.
I recall disk quotas on shared systems at university back in 1998 and I'm sure they existed before that.
Two thresholds IIRC, one at which you get a warning, second at which you can't write any further and the disk write operation fails.
I don't think they deleted files, it was just you couldn't write more than [quota] bytes to your disk.
Is there something particular about cloud based systems that prevent this from working?
ie. is this a specific problem with distributed storage?
edit:tone
- robrtsql 6y agoS3 costs money to keep your files in, even if you're not touching them, so just preventing further uploads wouldn't do much to prevent your AWS bill from increasing.
- camjohnson26 6y agoIt would let you set an upper limit on the price you pay though. Better than accidentally misconfiguring a logging service and writing gigabytes of unneeded data.
- Spooky23 6y agoThe IaaS services are easy. Other services are more difficult. Something like BigQuery ML could generate massive bills pretty easily.
- user5994461 6y ago>>> But we've had disk quotas before that mostly worked? AWS has quotas on everything, including quotas on EBS storage per region. You will realize that after you spin up some instances with disks and it's failing because you've hit 10 TB of EBS storage. Have to raise a ticket to raise the limit.