Are you making HDF5 calls that fail or is it PETSc routines calling HDF5 that fail?
Regardless it sounds like the easiest fix is to switch back to the previous HDF5 and wait for HDF5 to fix what sounds to be a bug. Barry > On Jun 11, 2020, at 1:05 AM, Danyang Su <danyang...@gmail.com> wrote: > > Hi All, > > Sorry to send the previous incomplete email accidentally. > > After updating to HDF5-1.12.0, I got some problem if some processors have no > data to write or not necessary to write. Since parallel writing is > collective, I cannot disable those processors from writing. For the old > version, there seems no such problem. So far, the problem only occurs on > Linux using GNU compiler. The same code has no problem using intel compiler > or latest gnu compiler on MacOS. > > I have already included h5sselect_none in the code for those processors > without data. But it does not take effect. The problem is documented in the > following link (How do you write data when one process doesn't have or need > to write data ?). > https://support.hdfgroup.org/HDF5/hdf5-quest.html#par-nodata > <https://support.hdfgroup.org/HDF5/hdf5-quest.html#par-nodata> > > Similar problem has also been reported on HDF Forum by others. > https://forum.hdfgroup.org/t/bug-on-hdf5-1-12-0-fortran-parallel/6864 > <https://forum.hdfgroup.org/t/bug-on-hdf5-1-12-0-fortran-parallel/6864> > > Any suggestion for that? > > Thanks, > > Danyang
