Hello list,
I recently upgraded my distribution-supplied OpenMPI packages (debian)
from 1.6.5 to 1.10.2 and the attached test is no longer guaranteed to
produce the expected output.
In plain English what the test is doing is:
1) open a file in parallel (all on the same local ext3/4 filesystem)
Thanks for the report.
the romio included in the v1.10 series is a bit old and did not include
the fix,
i made PR #1206 for that
http://www.open-mpi.org/community/lists/users/2016/05/29333.php
feel free to manually apply the patch available at
https://github.com/open-mpi/ompi-release/commi
just for my understanding, which bug in ompio are you referring? I am
only aware of a single (pretty minor) pending issue in the 2.x series
Thanks
Edgar
On 5/31/2016 1:28 AM, Gilles Gouaillardet wrote:
Thanks for the report.
the romio included in the v1.10 series is a bit old and did not
Hi Gilles,
Firstly thank you so much for your response.
I moved the line "source ~/OpenFOAM/OpenFOAM-v3.0+/etc/bashrc" (a line required
for a different program) to the bottom of the .bashrc file and the errors
previously encountered have disappeared.
I ran a test case for different program usi
Edgar,
this is the bug reported at
http://www.open-mpi.org/community/lists/users/2016/05/29333.php
now i am having some second thoughts about it ...
per the MPI_File_close man page :
"MPI_File_close first synchronizes file state, then closes the file
associated with fh.
MPI_File_clo
Gilles,
This is not an answer to your question, but:
MPI_File_write_at() is itself a blocking collective routine so your
example, would not work, would it?
Also, the standard has a few extra words (emphasis mine):
https://www.mpi-forum.org/docs/mpi-3.1/mpi31-report/node309.htm#Node309
"The u
