Dangers of rotating tar files too often In our Stage environment, we have a 'Share Nothing' Author configuration with a diskspace of 200GB for the Author. The diskspace fills up too quickly; every day workspace/crx.default directory grows by 30GB and tarJournal by 12G. When tar optimisation runs overnight, it optimizes the tar files but doesn't delete them if the maximumAge is not set in the repository.xml. By default optimized files are not deleted unless they are a month old. The problem is since these optimized files are not deleted, when optimisation runs the following night, it starts by processing the oldest file under the 3 locations: workspace/crx.default, tarJournal, version. It takes the same amount of time to optimize these files, although they had already been optimised the night before. Since they're already optimised, the append=-1 shows there is nothing to append to the new output data files created during optimisation. The optimisation process really should start from the where it left off, rather from the ol
