Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I'm sure there is something obvious I am neglecting, but I can't figure
this out:
[root at rhdmz01 ~]# rpm -qa |grep drbd
kmod-drbd82-smp-8.2.6-2.2.6.9_67.0.22.EL
drbd82-8.2.5-1.el4.centos
I have a box running DRBD without a second node - I just brought the
second box online this morning. I'm able to connect them, run them
pri/pri, however I'm unable to attach the disk of the new node.
[root at rhdmz01 ~]# drbdadm attach home_ftp
Failure: (119) No valid meta-data signature found.
==> Use 'drbdadm create-md res' to initialize meta-data area. <==
Command 'drbdsetup /dev/drbd1 disk /dev/VolGroup00/home_ftp
/dev/VolGroup00/home_ftp internal --set-defaults --create-device'
terminated with exit code 10
I didn't think I had to do that, but I tried it anyway... Now when I do
an attach I get this in the logs:
drbd2: disk( Diskless -> Attaching )
drbd2: No usable activity log found.
drbd2: max_segment_size ( = BIO size ) = 32768
drbd2: drbd_bm_resize called with capacity == 1048472
drbd2: resync bitmap: bits=131059 words=4096
drbd2: size = 512 MB (524236 KB)
drbd2: reading of bitmap took 5 jiffies
drbd2: recounting of set bits took additional 0 jiffies
drbd2: 512 MB (131059 bits) marked out-of-sync by on disk bit-map.
drbd2: disk( Attaching -> Negotiating )
drbd2: Writing meta data super block now.
drbd2: Barriers not supported on meta data device - disabling
drbd2: Becoming sync target due to disk states.
drbd2: conn( Connected -> WFBitMapT )
drbd2: conn( WFBitMapT -> WFSyncUUID )
drbd2: helper command: /sbin/drbdadm before-resync-target
drbd2: before-resync-target handler returned 3, dropping connection.
drbd2: peer( Primary -> Unknown ) conn( WFSyncUUID -> Disconnecting )
disk( Negotiating -> Inconsistent )
Any ideas what I'm missing here?
DAvid