Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi Mark,
Please, tell me more about this.
I have been struggling with my e1000e NIC, and the cluster isn't synching
at all. It goes until 2.8% (out of 16Tb) and the connection simply drops
off. That is why I want to use another NIC, which use a chipset other that
this e1000e.
I have already updated the driver to 1.9.5, and it's exactly what you said:
"random nic resets". I thought it was (1) the cables, (2) the switch ports
and finally (3) the switch itself. I have changed all these hardware, and
still can't sync.
Tell more about this issue with the Intel e1000e, please!
Thanks,
Marcelo
On Mon, Mar 12, 2012 at 10:41 AM, Mark Deneen <mdeneen at gmail.com> wrote:
> Also, please check your e1000e driver version and update to the latest
> stable version (out of tree). With the in-tree revision, we suffered
> from random nic resets under certain conditions, which really gave
> DRBD headaches.
>
> -M
>
> On Fri, Mar 9, 2012 at 11:37 AM, Marcelo Pereira <marcelops at gmail.com>
> wrote:
> > Hello guys,
> >
> > I have been facing a problem with a server who can't sync at all due to
> > network issues. The NIC (two Intel e1000e) is showing several errors and
> is
> > being dropped off. Sometimes at the primary node, sometimes at the
> > secondary. It will not sync.
> >
> > I have an unused NIC on both servers, and I would like to use them
> instead.
> > What should I do to move the configuration from one set of IP's to
> another??
> >
> > So, that is my current /etc/drbd.conf:
> >
> > global { usage-count no; }
> > resource pdc0 {
> > protocol C;
> > startup { wfc-timeout 0; degr-wfc-timeout 120; }
> > disk { on-io-error detach; } # ACK!
> > net { cram-hmac-alg "sha1"; shared-secret "xxxxxxx"; }
> > syncer { rate 10M; verify-alg sha1; }
> > on node0 {
> > device /dev/drbd0;
> > disk /dev/sdb;
> > address 192.168.69.1:7788;
> > meta-disk internal;
> > }
> > on node1 {
> > device /dev/drbd0;
> > disk /dev/sdc;
> > address 192.168.69.2:7788;
> > meta-disk internal;
> > }
> > }
> >
> > And that is what it should be after:
> >
> > global { usage-count no; }
> > resource pdc0 {
> > protocol C;
> > startup { wfc-timeout 0; degr-wfc-timeout 120; }
> > disk { on-io-error detach; } # ACK!
> > net { cram-hmac-alg "sha1"; shared-secret "xxxxxxx"; }
> > syncer { rate 10M; verify-alg sha1; }
> > on node0 {
> > device /dev/drbd0;
> > disk /dev/sdb;
> > address 10.0.0.1:7788;
> > meta-disk internal;
> > }
> > on node1 {
> > device /dev/drbd0;
> > disk /dev/sdc;
> > address 10.0.0.2:7788;
> > meta-disk internal;
> > }
> > }
> >
> > Is it enough to just change the /etc/drbd.conf on both servers? What is
> the
> > exact procedure? I'm using DRBD v8.2.6.
> >
> > Thanks,
> > Marcelo
> >
> > _______________________________________________
> > drbd-user mailing list
> > drbd-user at lists.linbit.com
> > http://lists.linbit.com/mailman/listinfo/drbd-user
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20120312/0f3c15ad/attachment.htm>