LINBIT / drbd-utils

DRBD userspace utilities (for 9.x, 8.4, 8.3)
GNU General Public License v2.0
78 stars 46 forks source link

device drbd01234 -> /dev/drbd1234 - shouldn't warn/error about '0' in device name? #28

Open jirib opened 1 year ago

jirib commented 1 year ago

DRBD does not error if one uses eg. device drbd01234 but it does "convert" it to drbd1234. It was discovered on SLES while using yast2-drbd.

grep -RH '' /etc/drbd.{conf,d/*.{conf,res}}
/etc/drbd.conf:# YaST2 created seperated configuration file
/etc/drbd.conf:include "/etc/drbd.d/global_common.conf";
/etc/drbd.conf:include "/etc/drbd.d/test01234.res";
/etc/drbd.d/global_common.conf:global {
/etc/drbd.d/global_common.conf:   usage-count   yes;
/etc/drbd.d/global_common.conf:   udev-always-use-vnr;
/etc/drbd.d/global_common.conf:   minor-count   5;
/etc/drbd.d/global_common.conf:   dialog-refresh        1;
/etc/drbd.d/global_common.conf:}
/etc/drbd.d/global_common.conf:common {
/etc/drbd.d/global_common.conf:   disk {
/etc/drbd.d/global_common.conf:   }
/etc/drbd.d/global_common.conf:   net {
/etc/drbd.d/global_common.conf:   }
/etc/drbd.d/global_common.conf:   startup {
/etc/drbd.d/global_common.conf:   }
/etc/drbd.d/global_common.conf:   options {
/etc/drbd.d/global_common.conf:      quorum     off;
/etc/drbd.d/global_common.conf:   }
/etc/drbd.d/global_common.conf:   handlers {
/etc/drbd.d/global_common.conf:   }
/etc/drbd.d/global_common.conf:}
/etc/drbd.d/test01234.res:resource test01234 {
/etc/drbd.d/test01234.res:   disk {
/etc/drbd.d/test01234.res:      on-io-error     pass_on;
/etc/drbd.d/test01234.res:   }
/etc/drbd.d/test01234.res:   net {
/etc/drbd.d/test01234.res:      protocol        C;
/etc/drbd.d/test01234.res:   }
/etc/drbd.d/test01234.res:   connection-mesh {
/etc/drbd.d/test01234.res:      hosts   jb154sapqe01 jb154sapqe02;
/etc/drbd.d/test01234.res:   }
/etc/drbd.d/test01234.res:   on jb154sapqe01 {
/etc/drbd.d/test01234.res:      address 192.168.0.57:7791;
/etc/drbd.d/test01234.res:      device  drbd01234;
/etc/drbd.d/test01234.res:      disk    /dev/disk/by-id/scsi-SQEMU_QEMU_HARDDISK_jb154sapqe01drbd01;
/etc/drbd.d/test01234.res:      meta-disk       internal;
/etc/drbd.d/test01234.res:      node-id 0;
/etc/drbd.d/test01234.res:   }
/etc/drbd.d/test01234.res:   on jb154sapqe02 {
/etc/drbd.d/test01234.res:      address 192.168.0.61:7791;
/etc/drbd.d/test01234.res:      device  drbd01234;
/etc/drbd.d/test01234.res:      disk    /dev/disk/by-id/scsi-SQEMU_QEMU_HARDDISK_jb154sapqe02drbd01;
/etc/drbd.d/test01234.res:      meta-disk       internal;
/etc/drbd.d/test01234.res:      node-id 1;
/etc/drbd.d/test01234.res:   }
/etc/drbd.d/test01234.res:}
udevadm info -n /dev/drbd1234
P: /devices/virtual/block/drbd1234
N: drbd1234
L: 0
S: drbd/by-disk/disk/by-id/scsi-SQEMU_QEMU_HARDDISK_jb154sapqe01drbd01
S: drbd/by-res/test01234/0
E: DEVPATH=/devices/virtual/block/drbd1234
E: DEVNAME=/dev/drbd1234
E: DEVTYPE=disk
E: MAJOR=147
E: MINOR=1234
E: SUBSYSTEM=block
E: USEC_INITIALIZED=102824765779
E: DEVICE=drbd01234
E: SYMLINK=drbd/by-res/test01234/0
E: SYMLINK_BY_RES=drbd/by-res/test01234/0
E: SYMLINK_BY_DISK=drbd/by-disk/disk/by-id/scsi-SQEMU_QEMU_HARDDISK_jb154sapqe01drbd01
E: DEVLINKS=/dev/drbd/by-disk/disk/by-id/scsi-SQEMU_QEMU_HARDDISK_jb154sapqe01drbd01 /dev/drbd/by-res/test01234/0
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd: