Misconfiguration with DRBD on Proxmox 3.0?

[TUM]

Hi all,

at the moment I’m configure the DRBD disks as described here -> http://pve.proxmox.com/wiki/DRBD#Add_the_LVM_group_to_the_Proxmox_VE_storage_list_via_web_interface
The configuration file on node1 and node2 looks exactlly the same:

/etc/drbd.d/r0.res
resource r0 {
protocol C;
startup {
wfc-timeout 0;
degr-wfc-timeout 60;
become-primary-on both;
}
net {
cram-hmac-alg sha1;
shared-secret "my-secret";
allow-two-primaries;
after-sb-0pri discard-zero-changes;
after-sb-1pri discard-secondary;
after-sb-2pri disconnect;
#data-integrity-alg crc32c;
}
on node1 {
device /dev/drbd0;
disk /dev/sdb1;
address 192.168.0.1:7788;
meta-disk internal;
}
on node2 {
device /dev/drbd0;
disk /dev/sdb1;
address 192.168.0.2:7788;
meta-disk internal;
}
}

If I try to start DRBD on those node I’m receiving:

root@node1:~# /etc/init.d/drbd start

drbd.d/r0.res:18: conflicting use of device-minor 'device-minor:node1:0' ...
drbd.d/os.res:24: device-minor 'device-minor:node1:0' first used here.
Starting DRBD resources:drbd.d/r0.res:18: conflicting use of device-minor 'device-minor:node1:0' ...
drbd.d/os.res:24: device-minor 'device-minor:node1:0' first used here.
root@node1:~# configuration file /etc/drbd.d/r0.res

root@node2:~# /etc/init.d/drbd start
drbd.d/r0.res:18: conflicting use of device-minor 'device-minor:node1:0' ...
drbd.d/os.res:24: device-minor 'device-minor:node1:0' first used here.
Starting DRBD resources:drbd.d/r0.res:18: conflicting use of device-minor 'device-minor:node1:0' ...
drbd.d/os.res:24: device-minor 'device-minor:node1:0' first used here.

Thanks for any help.
Regards
Markus

 

[TUM]

Anybody who is able the help me on this issue, please?

Regards
Markus

 

[macday]

Hello,

please post to folowing configs

pveversion -v
cat /etc/network/interfaces
parted -l (do apt-get install parted first)

regards
marco

 

[TUM]

Hello Marco,
thanks for your answer and help on this.

Here is the configuration of node1:

pve-manager: 3.0-20 (pve-manager/3.0/0428106c)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-15
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-6
vncterm: 1.1-3
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-12
ksm-control-daemon: 1.1-1

auto lo
iface lo inet loopback

iface eth0 inet manual
iface eth1 inet manual
iface eth2 inet manual
iface eth3 inet manual
iface eth4 inet manual
iface eth5 inet manual

#BONDING
auto bond0
iface bond0 inet manual
slaves eth4 eth5
bond_miimon 100
bond_mode balance-rr
bond-mode active-backup
bond-miimon 100
bond-downdelay 200
bond-updelay 200

#BONDING
auto bond1
iface bond1 inet static
address 192.168.0.1
netmask 255.255.255.0
slaves eth0 eth1 eth2 eth3
bond_miimon 100
bond_mode 802.3ad

#Bonding
auto vmbr0
iface vmbr0 inet static
address 10.162.192.1
netmask 255.255.252.0
gateway 10.162.195.254
network 10.162.192.0
bridge_ports bond0
bridge_stp off
bridge_fd 0

Model: LSI MR9260-16i (scsi)
Disk /dev/sdb: 6000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 1049kB 6000GB 6000GB primary lvm


Model: QNAP iSCSI Storage (scsi)
Disk /dev/sdc: 2199GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 17.4kB 134MB 134MB Microsoft reserved partition msftres
2 135MB 2199GB 2199GB ntfs Basic data partition


Model: QNAP iSCSI Storage (scsi)
Disk /dev/sdd: 1074MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
1 1049kB 1074MB 1073MB primary


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/pve-swap: 31.1GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number Start End Size File system Flags
1 0.00B 31.1GB 31.1GB linux-swap(v1)


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/pve-data: 138GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number Start End Size File system Flags
1 0.00B 138GB 138GB ext3


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/pve-root: 62.3GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number Start End Size File system Flags
1 0.00B 62.3GB 62.3GB ext3


root@node1:~#

Regards
Markus

 

[TUM]

doubled post *deleted content*

 

[udo]

Hello Marco,
thanks for your answer and help on this.

Here is the configuration of node1:

Hi,
is the device (sdb1) allready in use from lvm? Do you have filterd the device in lvm.conf?
What is the output of

pvs

Udo

 

[macday]

bond_mode balance-rr
bond-mode active-backup

two bond modes in one section ? which one is right ? does the ping work between the drbd-interfaces ?

 

[TUM]

@Udo
my output of pvs doesn't show that sdb1 is already in use...

root@node1:~# pvs
PV VG Fmt Attr PSize PFree
/dev/sda2 pve lvm2 a-- 231.87g 16.00g

@macday
ok, the ping between those drbd-interfaces is not working

root@node1:~# ping 102.168.0.2
PING 102.168.0.2 (102.168.0.2) 56(84) bytes of data.
From 188.1.37.89 icmp_seq=3 Destination Host Unreachable

Is there a mistake in the interfaces configuration? How should it look like?


Regards
Markus

 

[macday]

here is one of mine....

auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
address 10.11.12.30
netmask 255.255.252.0
gateway 10.11.12.254
bridge_ports eth6
bridge_stp off
bridge_fd 0
bridge_maxwait 0
bridge_maxage 0
bridge_ageing 0

auto bond1
iface bond1 inet static
slaves eth4 eth5
bond_miimon 100
bond_mode active-backup
address 10.0.0.30
netmask 255.255.255.0
post-up ifconfig bond1 mtu 9000

 

[TUM]

I've tried the difference the you got in your interfaces configuration, but the result is the same

root@node1:~# /etc/init.d/drbd start
drbd.d/r0.res:18: conflicting use of device-minor 'device-minor:node1:0' ...
drbd.d/os.res:24: device-minor 'device-minor:node1:0' first used here.
Starting DRBD resources:drbd.d/r0.res:18: conflicting use of device-minor 'device-minor:node1:0' ...
drbd.d/os.res:24: device-minor 'device-minor:node1:0' first used here.
root@node1:~#

Regards
Markus