Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
>
> Message: 1
> Date: Sun, 1 Mar 2009 16:33:22 +0100
> From: "Rik v. A" <rikratva at gmail.com>
> Subject: [DRBD-user] One of two nodes in DRBD cluster has a strange
> problem
> To: drbd-user at lists.linbit.com
> Message-ID:
> <4278c7ed0903010733o747e1e87gb8be4e32ad491e6d at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
>
> I am having a weird problem with two DRBD machines. These machines are
> exactly the same in hardware and software and are both running Debian
> Etch and DRBD 8.0.14.
> These two machines run Heartbeat and the IETD iSCSI target (latest
> stable version) in active/passive setup. The primary node is "stor1",
> the secondary "stor2".
> They have a direct Gigabit connection between each other, dedicated for DRBD.
> The problem is that Xen VMs running from this iSCSI target crash on
> high disk load, because (presumably) the iSCSI sessions time out.
>
> This only occurs when:
>
> - The two machines ("stor1" and "stor2") are both online, so stor1 is
> the active node, syncing to stor2.
> - stor1 is offline, so stor2 is the active node (and there is no DRBD syncing).
>
> This does not occur when:
>
> - stor2 is offline, so stor1 is the active node (there is no DRBD
> syncing between the nodes).
>
> Sometimes, a few seconds before one of these crashes, this error
> appears in the syslog, only of stor1. Note that this does not happen
> every time:
> drbd0: [drbd0_worker/26335] sock_sendmsg time expired, ko = 3
> I am currently running just from stor1, and have had no crashes.
>
> >From this I conclude that the problem must lay somewhere in the stor2
> machine. I just can't find out where.
> Both machines are running from A-brand hardware RAID, so disks can't
> be the problem.
>
> The machines have both Intel Gigabit Ethernet ports and on-board
> nVidia Gigabit Ethernet ports.
> Letting DRBD sync over another (brand) network interface does not make
> any difference. I am running the latest Intel e1000 drivers for these
> interfaces,
> hence I do not think the network is the problem.
>
> Following is my drbd.conf, which is pretty default, but just in case.
> If any more information is needed, I'd be glad to supply it.
>
> Thanks,
> Rik
>
> ### /etc/drbd.conf ###
>
> global {
> usage-count yes;
> }
> common {
> }
>
> resource resource0 {
> protocol C;
> handlers {
> pri-on-incon-degr "echo o > /proc/sysrq-trigger ; halt -f";
> pri-lost-after-sb "echo o > /proc/sysrq-trigger ; halt -f";
> local-io-error "echo o > /proc/sysrq-trigger ; halt -f";
> outdate-peer "/usr/lib/heartbeat/drbd-peer-outdater -t 5";
> }
>
> startup {
> degr-wfc-timeout 120; # 2 minutes.
> }
>
> disk {
> on-io-error detach;
> }
>
> net {
> ko-count 4;
> after-sb-0pri disconnect;
> after-sb-1pri disconnect;
> after-sb-2pri disconnect;
> rr-conflict disconnect;
> }
>
> syncer {
> rate 90M;
> al-extents 257;
> }
>
> on stor1 {
> device /dev/drbd0;
> disk /dev/sda9;
> address 192.168.3.121:7788;
> meta-disk /dev/sda8 [0];
> }
>
> on stor2 {
> device /dev/drbd0;
> disk /dev/sda9;
> address 192.168.3.122:7788;
> meta-disk /dev/sda8 [0];
> }
> }
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 02 Mar 2009 09:02:15 +0100
> From: Michael Turner <michael_turner at web.de>
> Subject: [DRBD-user] Syncronisation
> To: drbd-user at lists.linbit.com
> Message-ID: <515744165 at web.de>
> Content-Type: text/plain; charset=iso-8859-15
>
> Hello,
> my next problem is that the syncronisation of the nodes just won't work.
> On PC1 I changed the resource to master with the command "drbdsetup /dev/drbd0 primary --overwrite-data-of-peer".
> After typing "cat /proc/drbd" i get the following output:
>
> version: 8.2.7 (api:88/proto:86-88)
> GIT-hash: 8a9ba53abe973301639beacc55eec569b43507e5 build by lmb at hermes, 2008-12-10 13:23:20
> 0: cs:WFConnection st:Primary/Unknown ds:UpToDate/DUnknown C r---
> ns:0 nr:0 dw:32620 dr:20 al:13 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:1003900
>
> I continued with formating the /dev/drbd0 device with ext3.
>
>
> When I try to start DRBD i receive this output:
>
> PC1:~ # /etc/init.d/drbd start
> Starting DRBD resources: [ ].
> ..........
> ***************************************************************
> DRBD's startup script waits for the peer node(s) to appear.
> - In case this node was already a degraded cluster before the
> reboot the timeout is 0 seconds. [degr-wfc-timeout]
> - If the peer was available before the reboot the timeout will
> expire after 0 seconds. [wfc-timeout]
> (These values are for resource 'drbd-resource-0'; 0 sec -> wait forever)
> To abort waiting enter 'yes' [ 34]
>
>
>
> What am I doing wrong?
> I tried different tutorials and different configurations, but I always receive the same errors...
>
>
> drbd.conf:
>
> resource drbd-resource-0 {
>
> protocol C;
>
> handlers {
> pri-on-incon-degr "halt -f";
> }
> disk {
> on-io-error detach;
> }
>
> #startup {
> # degr-wfc-timeout 120;
> #}
>
> #net {
> # timeout 60;
> # connect-int 10;
> # ping-int 10;
> # max-buffers 2048;
> # max-epoch-size 2048;
> #}
>
>
> syncer {
> rate 10M;
> # group 1;
> # al-extents 257
> }
>
> on PC1 {
> device /dev/drbd0;
> disk /dev/md1;
> address 10.0.0.210:7789;
> flexible-meta-disk internal;
> }
>
> on PC2 {
> device /dev/drbd0;
> disk /dev/md1;
> address 10.0.0.211:7789;
> meta-disk internal;
> }
Obvious question, perhaps, but have you run '/sbin/service drbd start'
on both machines? That message implies that DRBD is not running on PC2.
If you did, make sure that any firewall software is allowing connections
to TCP port 7789.