Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi,
Once I used the drbd device on top of my lvm device then things are
working fine.
Thanks,
Nikhil
From: drbd-user-bounces at linbit.com [mailto:drbd-user-bounces at linbit.com]
On Behalf Of Nikhil Kulkarni
Sent: Wednesday, July 30, 2008 9:39 PM
To: drbd-user at linbit.com
Subject: [DRBD-user] Failure: (114) Lower device is already claimed.
Hi,
I'm trying to debug this problem and so far am unsuccessful. I sincerely
hope someone on this list can provide some solution. I also googled
around but most of the solutions that seemed to work for other people
did not work for me.
I have the following setup:
DRBD
LVM
Multipath
Physical disks
As soon as I run drbdadm attach resource I get the following error:
/dev/drbd1: Failure: (114) Lower device is already claimed. This usually
means it is mounted.
========================================================================
=
Here is my drbd.conf:
[root at fileserver1 ~]# more /etc/drbd.conf
# SAMPLE : /usr/share/doc/drbd/drbd.conf
#
global {
usage-count yes;
}
common {
protocol C;
}
resource mysql {
handlers {
outdate-peer "/usr/lib64/heartbeat/drbd-peer-outdater";
}
startup {
wfc-timeout 0;
degr-wfc-timeout 120; # 2 minutes.
}
disk {
on-io-error detach;
fencing resource-only;
}
net {
timeout 60;
connect-int 10;
ping-int 10;
max-buffers 4096;
max-epoch-size 4096;
}
syncer {
rate 500M;
al-extents 257;
verify-alg crc32c;
}
on fileserver1 {
device /dev/drbd1;
disk /dev/mapper/mpath0p3;
address 10.100.40.11:7789;
meta-disk /dev/mapper/mpath0p1[0];
}
on fileserver2 {
device /dev/drbd1;
disk /dev/mapper/mpath2p3;
address 10.100.40.13:7789;
meta-disk /dev/mapper/mpath2p1[0];
}
}
resource sqlite {
handlers {
outdate-peer "/usr/lib64/heartbeat/drbd-peer-outdater";
}
startup {
wfc-timeout 0;
degr-wfc-timeout 120; # 2 minutes.
}
disk {
on-io-error detach;
fencing resource-only;
}
net {
timeout 60;
connect-int 10;
ping-int 10;
max-buffers 4096;
max-epoch-size 4096;
}
syncer {
rate 500M;
al-extents 257;
verify-alg crc32c;
}
on fileserver1 {
device /dev/drbd2;
disk /dev/mapper/mpath0p4;
address 10.100.40.11:7790;
meta-disk /dev/mapper/mpath0p2[0];
}
on fileserver2 {
device /dev/drbd2;
disk /dev/mapper/mpath2p4;
address 10.100.40.13:7790;
meta-disk /dev/mapper/mpath2p2[0];
}
}
dmsetup table gives me this:
[root at fileserver1 ~]# dmsetup table
mpath0: 0 23437498368 multipath 1 queue_if_no_path 0 1 1 round-robin 0 2
1 8:32 100 8:48 100
mysql_volgrp-mysql: 0 392577024 linear 253:3 384
mpath0p4: 0 6363281250 linear 253:0 472656251
mpath0p3: 0 392578125 linear 253:0 80078126
mpath0p2: 0 41015625 linear 253:0 39062501
mpath0p1: 0 39062467 linear 253:0 34
sqlite_volgrp-sqlite: 0 6363275264 linear 253:4 384
[root at fileserver1 ~]# find /sys/block/ -path "*/holder/s*" -o -path
"*/slaves/*" -ls
28238 0 lrwxrwxrwx 1 root root 0 Jul 30 20:25
/sys/block/dm-2/sla -0 -> ../../../block/dm-0
28243 0 lrwxrwxrwx 1 root root 0 Jul 30 20:25
/sys/block/dm-1/sla -0 -> ../../../block/dm-0
28244 0 lrwxrwxrwx 1 root root 0 Jul 30 20:25
/sys/block/dm-6/sla -4 -> ../../../block/dm-4
28245 0 lrwxrwxrwx 1 root root 0 Jul 30 20:25
/sys/block/dm-5/sla -3 -> ../../../block/dm-3
28246 0 lrwxrwxrwx 1 root root 0 Jul 30 20:25
/sys/block/dm-4/sla -0 -> ../../../block/dm-0
28247 0 lrwxrwxrwx 1 root root 0 Jul 30 20:25
/sys/block/dm-3/sla -0 -> ../../../block/dm-0
28248 0 lrwxrwxrwx 1 root root 0 Jul 30 20:25
/sys/block/dm-0/sla d -> ../../../block/sdd
28249 0 lrwxrwxrwx 1 root root 0 Jul 30 20:25
/sys/block/dm-0/sla c -> ../../../block/sdc
Can someone please tell me which device has access to the block device
and how I can fix it?
Any help is greatly appreciated.
Thanks,
Nikhil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20080804/1744d087/attachment.htm>