[DRBD-user] DRBD rw access at both nodes

["Kotrappa(?????)"]

Hi List,

Is it possible to configure DRBD with active-active setup
with rw access at both the nodes???

I have trick-setup like below:

hostname:

kusha                                           lawa

primary -------------------------------------> secondary
/dev/nb0                                    /dev/nb0
/dev/hdb8                                   /dev/hda8


secondary <------------------------------primary
/dev/nb1                                /dev/nb1
/dev/hdb8                               /dev/hda8


By this setup read-write access is configured at both nodes.
please find attached drdb.conf file

drbd driver source modified at ~/drbd/drbd_fs.c: drbd_ioctl_set_disk()
commented lines from 97-105: for (i=0;i<minor_count;i++) loop

drbd script modified at /etc/init.d/drbd : line 1203, commented # check_disk

I am using drbd 0.6.12 version.

this setup is not working for rw access at both nodes, I get
SyncingAll : for /dev/nb1 trying to send blocks from lawa to kusha
and eventually sock_sendmsg time out and decrementing ko counter.

thanks,
Kotresh


-------------- drbd.conf --------------------------------
#
resource drbd0 {
  inittimeout=60
  protocol=B
  #fsckcmd=fsck.ext3 -p -y
  fsckcmd=date
  disk {
    disk-size = 256M
  }
  net {
    # sndbuf-size = 512k
    # skip-sync

    # sync-rate         # _deprecated_ synonym for sync-max
    # sync-nice  = -18  # if synchronization is high priority for you
    # sync-min   = 4M   # syncer tries hard to not drop below this rate
    # sync-max   = 100M # if you don't care about network saturation
                        # -max has to be larger than -min, obviously
    sync-min    = 500k
    sync-max    = 100M    # 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
  }

#primary
  on kusha {
    device  = /dev/nb0
    disk    = /dev/hdb8
    address = 10.10.10.1
    port    = 7788
  }
#secondary
  on lawa {
    device  = /dev/nb0
    disk    = /dev/hda8
    address = 10.10.10.2
    port    = 7788
  }
}
#
resource drbd1 {
  inittimeout=60
  protocol=B
  #fsckcmd=fsck.ext3 -p -y
  fsckcmd=date
  disk {
    disk-size = 256M
  }

net {
    # sndbuf-size = 512k
    # skip-sync

    # sync-rate         # _deprecated_ synonym for sync-max
    # sync-nice  = -18  # if synchronization is high priority for you
    # sync-min   = 4M   # syncer tries hard to not drop below this rate
    # sync-max   = 100M # if you don't care about network saturation
                        # -max has to be larger than -min, obviously
    sync-min    = 500k
    sync-max    = 100M    # 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
  }
#primary
  on lawa {
    device  = /dev/nb1
    disk    = /dev/hda8
    address = 10.10.10.2
    port    = 7789
  }
#secondary
  on kusha {
    device  = /dev/nb1
    disk    = /dev/hdb8
    address = 10.10.10.1 
    port    = 7789
  }
}

--------------------------------------------------------------------------------------------