For the standard function call sequence you'll want to look at server_initialize_subsystems() in src/server/pvfs2-server.c. This is part of what occurs during server start. I do see BMI_set_info() is called with the TCP options called regardless of BMI module type, I'm not sure offhand why that is.
In addition to the initialization in the above function a server tries to contact other servers in order to fill their precreate pools (see precreate_pool_launch_refiller() in the same file). I'm not sure if this is what's causing the testcontext you're seeing or not. Does that help? Michael On Thu, Aug 11, 2011 at 7:17 AM, Михаил Гильмендинов <[email protected]>wrote: > Hi! > > I've implement bmi method and I have a problem with pvfs2-server. > No send or recv operations were posted, but server calls testcontext: > > [mix@torus0 sbin]$ ./pvfs2-server ./pvfs2.conf -d > [S 08/11/2011 14:06:06] PVFS2 Server on node torus0 version 2.8.4-orangefs > starting... > [E 08/11/2011 14:06:06] BMI_initialize: j=0, ladr = m2://0, proto=m2: > bmi_m2 > [Node 0 at 0.0] m2_method_addr_lookup 547: id m2://0 > activate_method 2155: method_addr_lookup returns 0x91719e8 > [Node 0 at 0.1] m2_init 131: logfile creation failed > [Node 0 at 0.14] m2_init 135: Initialization. Warning: 10 nodes max. > init_rma 128: initialized. my node is 0, mem usage 15.625763 Mbytes > activate_method 2167: method_initialize returns 0 > BMI_initialize 306: activate method returns 0 > [Node 0 at 0.17959] m2_set_nfo 180: option 11 > [Node 0 at 0.17973] m2_set_nfo 180: option 12 > [Node 0 at 0.21876] m2_open_context 715: context id = 0 > [Node 0 at 0.21990] m2_testcontext 513: context id = 0, incount = 5 > [Node 0 at 0.22080] m2_test 400: id = 0 > [Node 0 at 0.22118] m2_test 451: id == 0 or errcode == BMI_ECANCELL > [Node 0 at 0.22156] m2_test 400: id = 107374182400 > [Node 0 at 0.22264] m2_method_addr_lookup 547: id m2://0 > Segmentation faut > > its look like server does these bmi calls: > > BMI_initialize("bmi_m2", "m2://0", BMI_INIT_SERVER ) > > BMI_set_info(..., BMI_TCP_BUFFER_SEND_SIZE = 11) > BMI_set_info(..., BMI_TCP_BUFFER_RECEIVE_SIZE = 12) > > BMI_testcontext(incount = 5, ....) > first id ==0, but second not null and no operation was posted. > > server log is empty. > > PVFS was configured with --without-bmi-tcp and options passed to > bmi_set_info looks strange. > I thought that it can be local problems on torus0(server log file is empty > and m2_init could not create logfile) but there still strange call stack. > > storage space creates successfuly. > > What is standard function call sequence for pvfs2-server? > > > С уважением, Гильмендинов Михаил > > _______________________________________________ > 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
