Open drodarie opened 4 months ago
Please confirm, but during simulation the storage engine should be operating in "readonly" mode, so it would be safe to use HDF5_USE_FILE_LOCKING=FALSE
as a workaround.
This may however indicate a problem with your MPI installation. Since an MPI-Window based lock should be active to prevent these issues.
When running a simulation with Nest, using MPI, one of the cores fails to get access to the h5 file. Command used:
Stack trace:
At the moment, I do not have a simple way to replicate this issue, since it happens randomly.