The job was terminated because there was insufficient disk space available. Please reduce the write frequency for results.
The instance storage ran out of space. You can prevent this behavior by reducing the number of time steps that are stored by increasing the write interval in the simulation control settings.
The analysis was failed because there was insufficient disk space available on the computing instance.
What could be the possible reason?
This error occurred when a simulation with a large mesh is conducted and the write frequency for the results is high.
What can I do now?
- Reduce the write frequency of the results:
The used storage space is directly correlated to the write frequency of the results. For a CFD simulation or a transient solid mechanics analysis multiple iterations or time steps are written to the hard disc. The frequency of the writing is controlled via the Write control definition setting of the simulation control. Increasing the write interval will reduce the disk usage.
- Equation solver specific changes:
If you are conducting a solid mechanics analysis and are using a direct solver like MUMPS or PETSC, reducing the number of cores used for the computation will also reduce the disk usage footprint of the analysis while running because of the way how those equation solvers are parallelized. Alternatively you could switch the linear solver to MultFront or GCPC.
- Reduce the computed result fields:
If you are conducting a solid mechanics analysis and none of the above worked, the final option would be to reduce the amount of result fields that are computed for the analysis. For this, remove all unnecessary solution fields from the result control setting.