On Wed, Oct 10, 2012 at 5:42 AM, Velayutham, Prakash <[email protected]> wrote: > Just wanted to add this. I repeated my test again and get the exact same > results again. Here is /proc/drbd of the primary (bmimysqlt3) and secondary > (bmimysqlt4) before the secondary's disk is cut off (disabling the fiber > switch port that the secondary is connected to) > > [root@bmimysqlt3 ~]# cat /proc/drbd > version: 8.4.2 (api:1/proto:86-101) > GIT-hash: 7ad5f850d711223713d6dcadc3dd48860321070c build by > [email protected], 2012-10-02 00:02:32 > 0: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r----- > ns:184 nr:0 dw:160 dr:14317 al:6 bm:6 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0 > > [root@bmimysqlt4 ~]# cat /proc/drbd > version: 8.4.2 (api:1/proto:86-101) > GIT-hash: 7ad5f850d711223713d6dcadc3dd48860321070c build by > [email protected], 2012-10-02 00:02:32 > 0: cs:Connected ro:Secondary/Primary ds:UpToDate/UpToDate C r----- > ns:0 nr:184 dw:184 dr:0 al:0 bm:6 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0 > > Here is /proc/drbd of primary and secondary about 5 minutes after the disk is > cut off. > > [root@bmimysqlt3 ~]# cat /proc/drbd > version: 8.4.2 (api:1/proto:86-101) > GIT-hash: 7ad5f850d711223713d6dcadc3dd48860321070c build by > [email protected], 2012-10-02 00:02:32 > 0: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r----- > ns:184 nr:0 dw:160 dr:14317 al:6 bm:6 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0 > > [root@bmimysqlt4 ~]# cat /proc/drbd > version: 8.4.2 (api:1/proto:86-101) > GIT-hash: 7ad5f850d711223713d6dcadc3dd48860321070c build by > [email protected], 2012-10-02 00:02:32 > 0: cs:Connected ro:Secondary/Primary ds:UpToDate/UpToDate C r----- > ns:0 nr:184 dw:184 dr:0 al:0 bm:6 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0 > > As you can see, there is absolutely nothing there to suggest that the > secondary even noticed the io-error.
At the risk of asking a silly question, how much I/O (on the Primary) went on after you cut the fiber connection on your Secondary? Was there any? In terms of which logs would be useful, a dump of your kernel logs (kern.log or dmesg), grepped for "drbd0" and pastebinned, would probably help. Cheers, Florian -- Need help with High Availability? http://www.hastexo.com/now _______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
