Ray Loy reported this with cobalt-subrun but could also happen in a normal mpirun environment.

Jobs started with cobalt-subrun all have the same jobid and user and possibly the same start/end time to the second resolution. This will cause one darshan log to be written but other mpiruns will have errors in the standard error complaining that the darshan log could not be written.