Hi, Thanks for catching this. I agree that IOR_offset_t (long long int) should be used, not the 32-bit int in the source. I'll make that change.
Thanks, -- Bill. On Monday 05 March 2007 00:08, yujian wrote: > Hello Bill, > > Recently, when we ran IOR (version 2.9.0) in the MPIIO mode to test the > performance of Lustre, we encountered the following error: > > ** error ** > ERROR in aiori-MPIIO.c (line 303): cannot access explicit, noncollective. > MPI Invalid argument > ** exiting ** > > After looking into the IOR codes, we found that the offset parameter > passed to MPI_File_read_at() api was negative, and this was due to the > incorrect data type of tmpOffset variable in WriteOrRead() function in > IOR.c. It's declared as "int", and we think it should be "IOR_offset_t". > Could you please take a look at this issue? > > BTW: this issue also exists in other 2.9-series IORs. > > Thanks. _______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
