Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Stefan Lesicnik wrote: > Hi Guys! > > I am getting a strange error on both boxes running drbd. > > > 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 claimed. This usually means > it is mounted. > > cmd /sbin/drbdsetup /dev/drbd0 disk /dev/sdb1 /dev/sdb1 internal > --set-defaults --create-device --on-io-error=detach failed! > > > This defiantly used to work, so im not sure what has gone wrong. > >>From what i've been able to determine, if LVM, MD or the system accesses > the drive, drbd cant use it then. Although im pretty sure this is not > the case. > > Im not using MD. I am using LVM and have tried the following > > filter = [ "a|/dev/drbd|", "r|.*|" ] > and > filter = [ "r|/dev/sdb1|" ] > > So im not convinced LVM has grabbed this device. > > I did update my standard ubuntu tools with the tools from the 8.0.6 > package. I dont know if this has anything to do with it. > > I am using the 8.0.6 kernel module. > > filename: > /lib/modules/2.6.20-16-lowlatency/kernel/drivers/block/drbd.ko > alias: block-major-147-* > license: GPL > description: drbd - Distributed Replicated Block Device v8.0.6 > author: Philipp Reisner <phil at linbit.com>, Lars Ellenberg > <lars at linbit.com> > srcversion: DC72784B6B126E56C64089F > depends: cn > vermagic: 2.6.20-16-lowlatency SMP preempt mod_unload > > > Anyone got any ideas around this! > > Thanks :) > Some more information. heh. Actually I cant say that its not MD. root at candyflip:~# dmsetup info Name: datavg-test State: ACTIVE Tables present: LIVE Open count: 0 Event number: 0 Major, minor: 254, 0 Number of targets: 1 UUID: LVM-3nyGH33GVieJvm0bmnLFEJMLjxhFlqgLQRxNTC94CNox6lK0TW0l67htJEg6RWF7 So it looks like dmsetup does setup the datavg-test LV. sigh. Although why. From my LVM by running vgscan -vvvv #cache/lvmcache.c:867 Wiping internal VG cache #toollib.c:501 Finding all volume groups #filters/filter-regex.c:185 /dev/ram0: Skipping (regex) #filters/filter-sysfs.c:251 /dev/loop0: Skipping (sysfs) #filters/filter-regex.c:185 /dev/sda: Skipping (regex) #device/dev-io.c:395 /dev/drbd0: open failed: Wrong medium type #filters/filter.c:95 /dev/drbd0: Skipping: open failed #filters/filter-regex.c:185 /dev/datavg/test: Skipping (regex) #filters/filter-regex.c:185 /dev/ram1: Skipping (regex) #filters/filter-regex.c:185 /dev/sda1: Skipping (regex) #filters/filter-regex.c:185 /dev/ram2: Skipping (regex) #filters/filter-regex.c:185 /dev/sda2: Skipping (regex) #filters/filter-regex.c:185 /dev/ram3: Skipping (regex) #filters/filter-regex.c:185 /dev/ram4: Skipping (regex) #filters/filter-regex.c:185 /dev/ram5: Skipping (regex) #filters/filter-regex.c:185 /dev/sda5: Skipping (regex) #filters/filter-regex.c:185 /dev/ram6: Skipping (regex) #filters/filter-regex.c:185 /dev/ram7: Skipping (regex) #filters/filter-regex.c:185 /dev/ram8: Skipping (regex) #filters/filter-regex.c:185 /dev/ram9: Skipping (regex) #filters/filter-regex.c:185 /dev/ram10: Skipping (regex) #filters/filter-regex.c:185 /dev/ram11: Skipping (regex) #filters/filter-regex.c:185 /dev/ram12: Skipping (regex) #filters/filter-regex.c:185 /dev/ram13: Skipping (regex) #filters/filter-regex.c:185 /dev/ram14: Skipping (regex) #filters/filter-regex.c:185 /dev/ram15: Skipping (regex) #filters/filter-regex.c:185 /dev/sdb: Skipping (regex) #filters/filter-regex.c:185 /dev/sdb1: Skipping (regex) #toollib.c:503 No volume groups found it also shows this #device/dev-cache.c:222 /dev/mapper/datavg-test: Aliased to /dev/datavg/test in device cache and /dev/datavg/test is skipped according to regex. So why is it adding it to dmsetup. sigh :) its ubuntu 7.04 if it makes a diff. thanks guys.