Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
You created the metadata on this device first? I remember having to do that first I think. What does /etc/mtab and /proc/mounts say? If /dev/hdb1 is OK to nuke have you tried writing zeros to it first to 'clean' it before creating the drbd device on it (and then subsequently pvcreate'ing the resulting drbdx). Jim ----- Original Message ----- From: Tim Stoop <tim.stoop at gmail.com> To: james vanns <james.vanns at framestore-cfc.com> Sent: 03 January 2007 14:59:45 o'clock GMT Europe/London Subject: Re: [DRBD-user] DRBD8 on LVM2 + Xen Hi James, On 1/3/07 , James Vanns < james.vanns at framestore-cfc.com > wrote: Yes it all works fine. I have a very similar setup. DRBD 8.0pre6 (or rc1) in primary/primary mode LVM2 (with RH Cluster extensions) Xen That looks about the same, indeed! What is the output of /proc/drbd on both machines? Looks like they don't have a cstate of connected... Which is correct, since I don't have the second machine online, since I'm not getting drbd to run on the first machine :) In the meantime, I've upgraded the debian source package to rc1 (really crude, but I'm getting the latest version at least). So the output from /proc/drbd is: tim at drbd1:~$ cat /proc/drbd version: 8.0rc1 (api:86/proto:85) SVN Revision: 2644 build by root at drbd1, 2007-01-03 14:52:57 0: cs:Unconfigured When I do a /etc/init.d/drbd start, I'm now getting: Starting DRBD resources: WARN: You are using the 'drbd-peer-outdater' as outdate-peer program. If you use that mechanism the dopd heartbeat plugin program needs to be able to call drbdsetup and drbdmeta with root privileges. You need to fix this with these commands: chgrp haclient /sbin/drbdsetup chmod o-x /sbin/drbdsetup chmod u+s /sbin/drbdsetup WARN: You are using the 'drbd-peer-outdater' as outdate-peer program. If you use that mechanism the dopd heartbeat plugin program needs to be able to call drbdsetup and drbdmeta with root privileges. You need to fix this with these commands: chgrp haclient /sbin/drbdmeta chmod o-x /sbin/drbdmeta chmod u+s /sbin/drbdmeta [ d0 Failure: (114) Lower device is already mounted. cmd /sbin/drbdsetup /dev/drbd0 disk /dev/hdb1 /dev/hdb1 flexible --set-defaults --create-device --on-io-error=detach failed! tim at drbd1:~$ Which is in my eyes far more descriptive, but still doesn't tell me what to do :( I'm very sure /dev/hdb1 isn't mounted. Check this: tim at drbd1:~$ mount /dev/sda1 on / type ext3 (rw,errors=remount-ro) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) procbususb on /proc/bus/usb type usbfs (rw) udev on /dev type tmpfs (rw,mode=0755) Any help is greatly appreciated! -- Gegroet, Tim -- -- James Vanns Systems Programmer Framestore CFC Ltd.