Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Ok, lets try this again... downloaded 08pre4 and built and installed it... here's my config [root at amber etc]# uname -r 2.6.17-1.2157_FC5 [root at amber etc]# /etc/init.d/drbd status drbd driver loaded OK; device status: version: 8.0pre4 (api:83/proto:82) SVN Revision: 2316 build by root at amber.pickerill.net, 2006-08-05 14:21:43 0: cs:Unconfigured [root at amber etc]# cat /proc/drbd version: 8.0pre4 (api:83/proto:82) SVN Revision: 2316 build by root at amber.pickerill.net, 2006-08-05 14:21:43 0: cs:Unconfigured [root at amber etc]# drbdadm dump common { syncer { rate 10M; } } resource drbd0 { protocol C; on amber.pickerill.net { device /dev/drbd0; disk /dev/sda1; address 192.168.1.4:7788; meta-disk /dev/sda2 [0]; } on avalon.pickerill.net { device /dev/drbd0; disk /dev/sda1; address 192.168.1.6:7788; meta-disk /dev/sda2 [0]; } net { after-sb-0pri disconnect; after-sb-1pri disconnect; after-sb-2pri disconnect; } disk { on-io-error detach; } syncer { rate 10M; al-extents 257; } startup { degr-wfc-timeout 120; } handlers { pri-on-incon-degr "halt -f"; pri-lost-after-sb "halt -f"; } } Now here's what happens... [root at amber etc]# drbdadm create-md all Valid meta-data already in place, recreate new? [need to type 'yes' to confirm] yes Creating meta data... initialising activity log initialising bitmap (131036 KB) 99%New drbd meta data block sucessfully created. [root at amber etc]# drbdadm up all ioctl(,SET_DISK_CONFIG,) failed: Invalid argument No valid meta-data signature found. Use 'drbdadm create-md res' to initialize meta-data area. Command 'drbdsetup /dev/drbd0 disk /dev/sda1 /dev/sda2 0 --on-io-error=detach' terminated with exit code 20 What am I missing or doing wrong? -dp-