[DRBD-user] Minor not found

Andreas Unterkircher unki at netshadow.at
Sat Jun 12 10:23:55 CEST 2004


Hello list!

I searched trough the archives, but didn't find any similar things...

I have a setup with two cluster nodes (debian SID) and 3 drbd devices on the
nodes. They run a plain 2.4.26 kernel with drbd 0.6.12.

Nodes are named debian1 & debian2 - also connected through a crossover cable
(drbddebian1 & drbddebian2).

Sometimes, when i reboot the secondary node and it comes up again, i got
following message when drbd is starting in the bootup sequence:

    "ERROR: Minor for /dev/nb2 'drbd2' not found in /proc/drbd"

... and drbd2 goes into unconfigured state or sometimes didn't appear in
/proc/drbd....
... drbd0 & drbd1 are always ok and never had problems!

After an manual "/etc/init.d/drbd restart" all went fine...

All minors i think are at there right place (on both hosts):

root at debian1:/dev# ls -l nb*
brw-rw----    1 root     disk      43,   0 May 15 13:39 nb0
brw-rw----    1 root     disk      43,   1 May 15 13:39 nb1
brw-rw----    1 root     disk      43,   2 May 15 13:39 nb2
brw-rw----    1 root     disk      43,   3 May 15 13:39 nb3
brw-rw----    1 root     disk      43,   4 May 15 13:39 nb4
brw-rw----    1 root     disk      43,   5 May 15 13:39 nb5
brw-rw----    1 root     disk      43,   6 May 15 13:39 nb6
brw-rw----    1 root     disk      43,   7 May 15 13:39 nb7

Here the drbd.conf

# global {
    # minor_count=5
# }

# DRBD /var/www
resource drbd0 {
  protocol = C
  fsckcmd  = fsck -p -y
  disk {
    do-panic
    disk-size = 29294496
  }
  net {
    # sync-rate         # _deprecated_ synonym for sync-max
    # sync-nice  = -18  # if synchronization is high priority for you
                        # -max has to be larger than -min, obviously
    sync-min    = 8M
    sync-max    = 10M    # maximal average syncer bandwidth
    tl-size     = 5000  # transfer log size, ensures strict write ordering
    timeout     = 60    # unit: 0.1 seconds
    connect-int = 10    # unit: seconds
    ping-int    = 10    # unit: seconds
    ko-count    = 4     # if some block send times out this many times,
                        # the peer is considered dead, even if it still
                        # answeres ping requests
  }
  on debian1 {
    device  = /dev/nb0
    disk    = /dev/hda8
    address = drbddebian1
    port    = 7788
  }
  on debian2 {
    device  = /dev/nb0
    disk    = /dev/hda8
    address = drbddebian2
    port    = 7788
  }
}

# DRBD /var/lib/mysql
resource drbd1 {
  protocol = C
  fsckcmd  = fsck -p -y
  disk {
    do-panic
    disk-size = 19535008
  }
  net {
    # sync-rate         # _deprecated_ synonym for sync-max
    # sync-nice  = -18  # if synchronization is high priority for you
                        # -max has to be larger than -min, obviously
    sync-min    = 8M
    sync-max    = 10M    # maximal average syncer bandwidth
    tl-size     = 5000  # transfer log size, ensures strict write ordering
    timeout     = 60    # unit: 0.1 seconds
    connect-int = 10    # unit: seconds
    ping-int    = 10    # unit: seconds
    ko-count    = 4     # if some block send times out this many times,
                        # the peer is considered dead, even if it still
                        # answeres ping requests
  }
  on debian1 {
    device  = /dev/nb1
    disk    = /dev/hda9
    address = drbddebian1
    port    = 7789
  }
  on debian2 {
    device  = /dev/nb1
    disk    = /dev/hda9
    address = drbddebian2
    port    = 7789
  }
}

# DRBD /home
resource drbd2 {
  protocol = C
  fsckcmd  = fsck -p -y
  disk {
    do-panic
    disk-size = 4883728
  }

  net {
    # sync-rate         # _deprecated_ synonym for sync-max
    # sync-nice  = -18  # if synchronization is high priority for you
                        # -max has to be larger than -min, obviously
    sync-min    = 8M
    sync-max    = 10M    # maximal average syncer bandwidth
    tl-size     = 5000  # transfer log size, ensures strict write ordering
    timeout     = 60    # unit: 0.1 seconds
    connect-int = 10    # unit: seconds
    ping-int    = 10    # unit: seconds
    ko-count    = 4     # if some block send times out this many times,
                        # the peer is considered dead, even if it still
                        # answeres ping requests
  }
  on debian1 {
    device  = /dev/nb2
    disk    = /dev/hda10
    address = drbddebian1
    port    = 7790
  }
  on debian2 {
    device  = /dev/nb2
    disk    = /dev/hda10
    address = drbddebian2
    port    = 7790
  }
}

I also tried such things like deleting the content of /var/lib/drbd/* and so
one...
Anyone has an idea, what can cause this bootup failure?

Andreas




More information about the drbd-user mailing list