#1283: Missing data in HDF5 files ---------------------+------------------------------------------------------ Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Cactus | Version: Resolution: | Keywords: ---------------------+------------------------------------------------------
Comment (by knarf):
which means that you can recover a simulation from a "corrupted"
restart, and not have the data from that restart.
Shouldn't Cactus abort with a non-zero exit code in such a case (e.g. disk full)? Shouldn't then simfactory _not_ restart in that case, unless explicitly told, in which case the user would be able to decide depending on what happened where to restart from?