[DRBD-user] IO Error Logging

Andrew Eross eross at locatrix.com
Sun Oct 7 18:02:13 CEST 2012

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


Hi Felix, guys,

Thanks for all the help and advice ---

So, in the end, yep, guess what ... DRBD on XenServer 6 does not appear to
like Open vSwitch in my case.

If the Linbit guys are listening, might be worth noting that in the XS6
setup guide.

If anyone else experiences this problem...

Just run "xe-switch-network-backend bridge" on your nodes, which seamlessly
switches from open vswitch to linux bridging after a reboot... and poof all
of my freezing and problems have now gone away at the expense of the OVS
features that I wasn't using anyways.

Cheers,
Andrew

On Sun, Oct 7, 2012 at 12:46 PM, Andrew Eross <eross at locatrix.com> wrote:

> Hi Felix,
>
> I have a very simple default type config running here:
>
> global
> {
>     usage-count yes;
> }
> common
> {
>     protocol C;
>     net
>     {
>         after-sb-0pri discard-zero-changes;
>         after-sb-1pri consensus;
>         after-sb-2pri disconnect;
>     }
>     disk
>     {
>     }
>     handlers
>     {
>         split-brain "/usr/lib/drbd/notify-split-brain.sh";
>     }
> }
>
> resource drbd-sr1 {
> net {
> }
> syncer {
> }
> disk {
> on-io-error detach;
> }
>     on vh03.office.locatrix.net {
>         device /dev/drbd1;
>         disk /dev/VG_XenStorage-862f18be-6501-63bd-328d-e4a0843fac7b/drdb;
>         address 10.0.0.3:7789;
>         meta-disk internal;
>     }
>     on vh04.office.locatrix.net {
>         device /dev/drbd1;
>         disk /dev/VG_XenStorage-94ac59fb-2d82-df06-5560-76570dcfa307/drbd;
>         address 10.0.0.4:7789;
>         meta-disk internal;
>     }
> }
>
> ifconfig looks like this:
> [root at vh04 ~]# ifconfig
> eth0      Link encap:Ethernet  HWaddr 40:6C:8F:24:C0:6F
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:311004408 errors:0 dropped:0 overruns:0 frame:229
>            TX packets:628898462 errors:1 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:3336540977 (3.1 GiB)  TX bytes:1043299490 (994.9 MiB)
>           Interrupt:16
>
> eth1      Link encap:Ethernet  HWaddr 7C:C3:A1:87:F1:D9
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:327842282 errors:225 dropped:0 overruns:0 frame:225
>           TX packets:346387593 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:667488230 (636.5 MiB)  TX bytes:997801992 (951.5 MiB)
>
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:42549511 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:42549511 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:4111323287 (3.8 GiB)  TX bytes:4111323287 (3.8 GiB)
>
> vif18.0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           UP BROADCAST RUNNING NOARP PROMISC  MTU:1500  Metric:1
>           RX packets:11497 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:11489 errors:0 dropped:17 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:2100283 (2.0 MiB)  TX bytes:2682900 (2.5 MiB)
>
> vif19.0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           UP BROADCAST RUNNING NOARP PROMISC  MTU:1500  Metric:1
>           RX packets:10801 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:14222 errors:0 dropped:49 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:2537871 (2.4 MiB)  TX bytes:2558791 (2.4 MiB)
>
> xenbr0    Link encap:Ethernet  HWaddr 40:6C:8F:24:C0:6F
>           inet addr:10.0.0.4  Bcast:10.0.0.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>           RX packets:311004466 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:166306729 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:2092488469 (1.9 GiB)  TX bytes:2485661044 (2.3 GiB)
>
> xenbr1    Link encap:Ethernet  HWaddr 7C:C3:A1:87:F1:D9
>           inet addr:192.168.41.24  Bcast:192.168.41.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>           RX packets:63765301 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:31683504 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:1320179908 (1.2 GiB)  TX bytes:2335142508 (2.1 GiB)
>
> Hmmmm... in fact I think it does use OVS.
>
> I followed the Linbit directions on setting up DRBD with XenServer 6:
> http://www.linbit.com/fileadmin/tech-guides/xenserver-drbd.pdf
>
> Which means I added the DRBD interface as a XS management interface, which
> gets setup as a bridge by XS.
>
> I also see that Open vSwitch is now the default with XS6 as well, so yes
> it must be.
>
> I can change from open vswitch to normal linux bridging with
> "xe-switch-network-backend bridge" on XenServer, so what the heck let's see
> if that does some magic here.
>
>
>
> On Sun, Oct 7, 2012 at 12:28 PM, Felix Frank <ff at mpexnet.de> wrote:
>
>>
>> On 10/07/2012 05:13 PM, Andrew Eross wrote
>>
>>  Very strange! Any ideas, guys?
>>>
>>
>> Yeah. I haven't looked at your config, but if DRBD relies on an OVS port
>> for replication, that may be a Bad Idea.
>>
>> HTH,
>> Felix
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20121007/289e6034/attachment.htm>


More information about the drbd-user mailing list