Prevent admins from shooting themselves in the foot
The admin interface for managing domain storage should check when the updated values for "max files" and "max file size" would cause problems.
As mentioned by Axigen Support:
=====
If the value of the 'Max file size' parameter is set lower, then the larger containers will be used but they will behave as if they were completely full, meaning that no modification can be performed on the messages in those containers.
If the value of the 'Max files' parameter is set lower than the actual number of containers, then the containers exceeding the configured value will not be used at all and the messages stored in them will not be accessible.
Likewise, when setting "max files" and "max file size", the system should first check if the given values will fit in the server's available disk space.
Anonymous
shared this idea
-
Anonymous
commented
According to Axigen Support, referring to over-provisioning of "max files" and "max file size" in domain storage:
=====
Please know that in such a case Axigen could write onto the disk until it becomes full, if space is needed, and when this occurs it can potentially cause data corruption because the data from memory can no longer be flushed onto the disk. Therefore such a situation should be avoided.
=====