Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Good afternoon, I took a look through the mailing list but my issue didn't seem to jump out at me, so I'll ask it. Right now I have DRBD8 tied in with Heartbeat v1. Running on a Ubuntu 7.04 install, kernel 2.6.22-14-server. I am running a MySQL database on the DRBD partition. When I power down the secondary machine to simulate a complete hardware failure. The /proc/drbd file on the Primary shows: cs:WFConnection st:Primary/Unknown ds:UpToDate/DUnknown C r--- I expected to see that, but after a few minutes my mounted partition suddenly stopped responding. I could cd into it, but couldn't do anything else. Is this suppose to happen, and if it is how can I stop it from happening? Since having my database freeze up if any of the DRBD nodes go out is not really helpful. Here is my drbd.conf file: *resource r0 { protocol C; startup { wfc-timeout 0; ## degr-wfc-timeout 120; ## 2 minutes. } disk { on-io-error detach; } net { # timeout 60; # connect-int 10; # ping-int 10; # max-buffers 2048; # max-epoch-size 2048; } syncer { rate 100M; } on Primary { device /dev/drbd0; disk /dev/sdb2; address 192.168.2.2:7789; meta-disk internal; } on Secondary { device /dev/drbd0; disk /dev/sda4; address 192.168.2.3:7789; meta-disk internal; } }* -- Joseph Crosby Network Administrator Scotia Weather Service Inc. netadmin at scotiaweather.com ----------- A byte walks into a bar and orders a pint. Bartender asks him "What's wrong?" Byte says "Parity error." Bartender nods and says "Yeah, I thought you looked a bit off."