On Wed, Mar 04, 2009 at 07:15:24PM -0500, Bradley Settlemyer wrote: > Hello > > I am trying to use PAV to run pvfs with the MX protocol. I've > updated pav so that servers start and ping correctly. But when I try > and run an mpi code, I'm getting client timeouts like the client > cannot contact the servers: > > Lots of this stuff: > > [E 19:11:02.573509] job_time_mgr_expire: job time out: cancelling bmi > operation, job_id: 3. > [E 19:11:02.583659] msgpair failed, will retry: Operation cancelled > (possibly due to timeout)
OK, so pvfs utilities are all hunky-dory? not just pvfs2-ping but pvfs2-cp and pvfs2-ls? On Jazz, I usually configure MPICH2 to communicate over TCP and have the PVFS system interface communicate over MX. This keeps the situation fairly simple, but of course you get awful MPI performance. Does MX still have the "ports" restriction that GM has? I wonder if MPI communication is getting in the way of PVFS communication... In short, I don't exactly know what's wrong myself. just tossing out some theories. ==rob -- Rob Latham Mathematics and Computer Science Division A215 0178 EA2D B059 8CDF Argonne National Lab, IL USA B29D F333 664A 4280 315B _______________________________________________ Pvfs2-users mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
