Hi Avery, Yup.. Your fix is correct, but let's wait for Sam's comments.. Why exactly is result.bytes different from s_op->u.small_io.result_bytes? I wonder how this did not get triggered in the normal scenarios (perhaps it needed a sparse data file or something?) Thanks, Murali
On Mon, 22 May 2006, Avery Ching wrote: > I kept getting segmentation faults with the read case in the small I/O > state machine. I think there's a problem with the parameter passed in > to job_trove_bstream_read_list() around line 194 of small-io.sm. > > instead of: > &result.bytes, > > I think it should be: > &s_op->u.small_io.result_bytes, > > > Avery > > _______________________________________________ > Pvfs2-developers mailing list > [email protected] > http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers > > _______________________________________________ Pvfs2-developers mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
