[DRBD-user] 8.4 unable to use device mapper dev files?

[Brian Chrisman]

Under 8.4.0, this configuration gives me "Cannot determine minor
device number of" ...

Under 8.3.11 it appears to be working fine.

The device file looks fine:

[root at scale-192-168-98-109 ~]# ls -l /dev/dm-0
brw-rw---- 1 root disk 253, 0 Sep  9 21:40 /dev/dm-0
[root at scale-192-168-98-109 ~]#

Here's my .res
resource ramdevn1a2b {
  device    /dev/drbd7;
  meta-disk internal;
  on scale-192-168-98-109 {
    disk      /dev/dm-0;
    address   192.168.98.109:7795;
  }
  on scale-192-168-98-110 {
    disk      /dev/dm-1;
    address   192.168.98.110:7795;
  }
}
resource ramdevn1c2d {
  device    /dev/drbd8;
  meta-disk internal;
  on scale-192-168-98-109 {
    disk      /dev/dm-2;
    address   192.168.98.109:7796;
  }
  on scale-192-168-98-110 {
    disk      /dev/dm-3;
    address   192.168.98.110:7796;
  }
}
resource ramdevn1b3a {
  device    /dev/drbd9;
  meta-disk internal;
  on scale-192-168-98-109 {
    disk      /dev/dm-1;
    address   192.168.98.109:7797;
  }
  on scale-192-168-98-111 {
    disk      /dev/dm-0;
    address   192.168.98.111:7797;
  }
}
resource ramdevn1d3c {
  device    /dev/drbd10;
  meta-disk internal;
  on scale-192-168-98-109 {
    disk      /dev/dm-3;
    address   192.168.98.109:7798;
  }
  on scale-192-168-98-111 {
    disk      /dev/dm-2;
    address   192.168.98.111:7798;
  }
}
resource ramdevn2a3b {
  device    /dev/drbd11;
  meta-disk internal;
  on scale-192-168-98-110 {
    disk      /dev/dm-0;
    address   192.168.98.110:7799;
  }
  on scale-192-168-98-111 {
    disk      /dev/dm-1;
    address   192.168.98.111:7799;
  }
}
resource ramdevn2c3d {
  device    /dev/drbd12;
  meta-disk internal;
  on scale-192-168-98-110 {
    disk      /dev/dm-2;
    address   192.168.98.110:7800;
  }
  on scale-192-168-98-111 {
    disk      /dev/dm-3;
    address   192.168.98.111:7800;
  }
}




And conf... (note, this is only playing-around...)
global {
	usage-count no;
	# minor-count dialog-refresh disable-ip-verification
}

common {
	protocol C;

	handlers {
		pri-on-incon-degr "/usr/lib/drbd/notify-pri-on-incon-degr.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger
; reboot -f";
		pri-lost-after-sb "/usr/lib/drbd/notify-pri-lost-after-sb.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger
; reboot -f";
		local-io-error "/usr/lib/drbd/notify-io-error.sh;
/usr/lib/drbd/notify-emergency-shutdown.sh; echo o >
/proc/sysrq-trigger ; halt -f";
		# fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
		# split-brain "/usr/lib/drbd/notify-split-brain.sh root";
		# out-of-sync "/usr/lib/drbd/notify-out-of-sync.sh root";
		# before-resync-target "/usr/lib/drbd/snapshot-resync-target-lvm.sh
-p 15 -- -c 16k";
		# after-resync-target /usr/lib/drbd/unsnapshot-resync-target-lvm.sh;
	}

	startup {
        become-primary-on both;
		# wfc-timeout degr-wfc-timeout outdated-wfc-timeout wait-after-sb
	}

	disk {
		# on-io-error fencing use-bmbv no-disk-barrier no-disk-flushes
		# no-disk-drain no-md-flushes max-bio-bvecs
        no-disk-flushes;
        no-disk-drain;
        no-md-flushes;
	}

	net {
        allow-two-primaries;
#        allow-two-primaries yes; # this doesn't work
		# sndbuf-size rcvbuf-size timeout connect-int ping-int ping-timeout
max-buffers
		# max-epoch-size ko-count allow-two-primaries cram-hmac-alg shared-secret
		# after-sb-0pri after-sb-1pri after-sb-2pri data-integrity-alg no-tcp-cork
	}

	syncer {
		# rate after al-extents use-rle cpu-mask verify-alg csums-alg
	}
}