Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
> > > If I start again: > > > > > > Starting DRBD resources: [vol21][vol22]Child process does not > > > terminate! Exiting. > > > > > > and so on : one more volume is completed every time I launch the > > > script. Looking at the source code, I believe the timeout has to do > > > with the SLEEPS_LONG / SLEEPS_VERY_LONG values that probably aren't > > > enough in my case (but i'm not sure if I'm hitting the "long" or "very > > > long" timeout). Can these be made into module parameters, or at least > > > #define's ? > > > > > > Eventually, after enough launches, all volumes are corrected > > > initialized, except... > > > > Yes, I have changed SLEEPS_LONG from 60 to 120 Seconds with the > > drbd-0.7.6 release. > > this might not really solve this issue, since the "child process" (the one > which does not terminate) stays until the corresponding device is in sync. > Couldn't drbd check whether the child syncs and went on with the other > devices? In fact, drbd might first check, which devices are in the highest > sync group (e.g. group=1) and start the corresponding child processes for > parallel sync. The others might be schedduled accordingly for sync. Just my > thoughts. Is there any necessarity for waiting? I consider "Exiting" as a > bug in a HA context. I stumbeled on the same recently. > Renaud and I were refering to "drbdsetup /dev/drbdX disk ..." while you are refering to "drbdstup /dev/drbdX wait_sync" probabely... -Phil -- : Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 : : LINBIT Information Technologies GmbH Fax +43-1-8178292-82 : : Schönbrunnerstr 244, 1120 Vienna, Austria http://www.linbit.com :