You can call the stat mop in notify() of event GF_EVENT_CHILD_UP. GF_EVENT_CHILD_UP ensures that the child volumes have been called init(). you can refer the case of schedulers sending the stat call in notify() (unify+rr) if you need a variable across the call and its callback, you should put them in frame->local. thanks, avati 2008/1/18, Angel <clist@xxxxxx>: > > Hi, > > I have to record underlaying storage parameters total_disk_size, > disk_usage and free_disk. > > Can I call child-> stat mops in init or i must declare notify and record > params on CHILD_UP?? > > Last question calling chid-> stats mops... > I need to call and place my record_stats_cbk on the stack to read values > on return? is this the way? > > Regards, Angel > > > -- > ---------------------------- > Clister UAH > ---------------------------- > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > http://lists.nongnu.org/mailman/listinfo/gluster-devel > -- If I traveled to the end of the rainbow As Dame Fortune did intend, Murphy would be there to tell me The pot's at the other end.
