Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Dear all,
yesterday I had to turn off for an hour all our servers (replacement of
emergency power generator and simulation of failure).
After reboot the main server "lost" all 3 internet interfaces. For that
reason DRBD failed to start. After some time I figured out, that aliases
for NICs were not loaded (no idea why, but they disappeared from
/etc/modprobe.conf). Again reboot network was there but still no DRBD.
The output of "service drbd status" is not complete:
"service drbd status"
drbd driver loaded OK; device status:
version: 8.0.16 (api:86/proto:86)
GIT-hash: d30881451c988619e243d6294a899139eed1183d build by
mockbuild at v20z-x86-64.home.local, 2009-08-22 13:26:57
m:res cs st ds p mounted fstype
However "/proc/drbd" seems OK
version: 8.0.16 (api:86/proto:86)
GIT-hash: d30881451c988619e243d6294a899139eed1183d build by
mockbuild at v20z-x86-64.home.local, 2009-08-22 13:26:57
0: cs:Connected st:Secondary/Secondary ds:UpToDate/UpToDate C r---
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
resync: used:0/61 hits:0 misses:0 starving:0 dirty:0 changed:0
act_log: used:0/127 hits:0 misses:0 starving:0 dirty:0 changed:0
I've found out that block file /dev/drbd0 was missing after reboot.
I've tried to add the /dev/drbd0 manually with
"mknod -m 0660 /dev/drbd0 b 147 0" and restart of drbd
but it didn't change the situation.
The same results form "service drbd status"
After reboot again no /dev/drbd0.
As last resort I've tried to regenerate whole DRBD from secondary node.
service drbd stop
rm -f /dev/drbd0
drbdadm create-md r0
service drbd start
Still no /dev/drbd0 and no output from "service drbd status" (only the
"cat /prc/drbd" shows now that the drive is synchronizing).
I would be very grateful for any help
kris