Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi all, I'm using drbd 8.0.4 from a Debian Package from Lenny (testing), and I think drbd has some problems handling long names for backend devices. I'm using a LVM volume "/dev/storage/drbd-backups-from-jeroen" for my resource "backups-jeroen" and drbd seems to get confused by the long device name: > $ drbdadm up backups-jeroen > Failure: (104) Can not open backing device. > Command 'drbdsetup /dev/drbd1 disk > /dev/storage/drbd-backups-from-jeroen > /dev/storage/drbd-backups-from-jeroen internal --set-defaults > --create-device --on-io-error=detach' terminated with exit code 10 And: > $ ls -la /dev/storage/drbd-backups-from-jeroen > lrwxrwxrwx 1 root root 47 2008-01-06 14:31 > /dev/storage/drbd-backups-from-jeroen -> > /dev/mapper/storage-drbd--backups--from--jeroen Now check the output of dmesg: > $ dmesg > drbd: initialised. Version: 8.0.4 (api:86/proto:86) > drbd: SVN Revision: 2947 build by root at guust, 2008-01-06 14:20:15 > drbd: registered as block device major 147 > drbd: minor_table @ 0xc23c60c0 > drbd1: > open("/dev/storage/drbd-backups-from-jeroe/dev/storage/drbd-backups-from-jeroe����") > failed with -2 The last line is the one worrying me: it seems like drbd has some difficulties with managing it's memory? Would there exist a worst case scenario where one would end up using a wrong device as backend? I'd like to hear your thoughts! Cheers, Bas