Edgar Gabriel <gabr...@cs.uh.edu> writes: > not sure honestly. Basically, as suggested in this email chain earlier, > I had to disable the PVFS2_IreadContig and PVFS2_IwriteContig routines > in ad_pvfs2.c to make the tests pass. Otherwise the tests worked but > produced wrong data. I did not have however the time to figure what > actually goes wrong underneath the hood.
[I can't get into trac to comment on the issue (hangs on login), so I'm following up here.] In case it's not clear, the changes for 1.6 and 1.7 are different, and probably shouldn't be. The patch I took from 1.7 looked similar to what's in mpich, but hard-wired rather than autoconfiscated, whereas the patch for 1.6 on the tracker sets the entries to NULL instead. > Edgar > > On 3/25/2014 9:21 AM, Rob Latham wrote: >> >> >> On 03/25/2014 07:32 AM, Dave Love wrote: >>> Edgar Gabriel <gabr...@cs.uh.edu> writes: >>> >>>> I am still looking into the PVFS2 with ROMIO problem with the 1.6 >>>> series, where (as I mentioned yesterday) the problem I am having right >>>> now is that the data is wrong. Not sure what causes it, but since I have >>>> teach this afternoon again, it might be friday until I can digg into >>>> that. >>> >>> Was there any progress with this? Otherwise, what version of PVFS2 is >>> known to work with OMPI 1.6? Thanks. >> >> Edgar, should I pick this up for MPICH, or was this fix specific to >> OpenMPI ? >> >> ==rob >>
