SolidWallOfCode commented on issue #4711: URL: https://github.com/apache/trafficserver/issues/4711#issuecomment-870123150
There are two issues that could be going wrong here, none of which come up if a raw partition is used. * When the cache reads "3500G" it interprets that as "3500 * 2^30" which is 3.75 * 10^12 which makes it possible there is really not that much space on the disk. * ATS will create a file of the appropriate size, but many operating systems will not actually allocate the space until required. This means disk space can run out due to too many accesses as the cache size grows, but ATS thinks it's already reserved the space. See [here](https://docs.trafficserver.apache.org/en/9.0.x/developer-guide/cache-architecture/architecture.en.html#storage-layout) - the content is at the end of the storage. We could try tweaking ATS to write the last byte for the storage file, which should force the file to exist. This could lead to very long start up times the first time ATS is started with that storage config. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
