Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
> > >so this is not a bug in drbd, but web100 alters the timing "somehow" >> >that it takes several seconds to get one single data block through. >> >> Is that really the case (see below)? Do you have any guess about the >> "somehow"? The timing of what exactly? I gather that there are two >> separate lines of communication for each resource, the ping and the >> data stream and what's below is only the ping. The data stream is >> being ignored. >> >> Here's an excerpt from tcpdump taken from the acting primary >> (kennedy2), which lacks the web100 kernel, just after drbd has been >> brought up on the web100-based peer (kennedy1). There are two >> resources, one using port 7790 and the other using port 7791. > >and what am I supposed to do with that? > Nothing. :-) The problem turned out to be a second bug in the web100 code. It was fixed in 2.5.10 of web100. -- Maurice Volaski, mvolaski at aecom.yu.edu Computing Support, Rose F. Kennedy Center Albert Einstein College of Medicine of Yeshiva University