Dear List,
We are configuring DRBD for the first time using the DRBD manual. We are planning to setup DRBD on our mail server running on RHEL 6.1 (64 bit), with the sole objective to replicate the mail store and mail queue from our data center to the DR site. Both the sites are connected with giga bit captive OF network. We have installed the following drbd rpm that was built from the source drbd-8.4.3.tar.gz :- drbd-heartbeat-8.4.3-2.el6.x86_64 drbd-xen-8.4.3-2.el6.x86_64 drbd-km-debuginfo-8.4.3-2.el6.x86_64 drbd-udev-8.4.3-2.el6.x86_64 drbd-8.4.3-2.el6.x86_64 drbd-pacemaker-8.4.3-2.el6.x86_64 drbd-debuginfo-8.4.3-2.el6.x86_64 drbd-utils-8.4.3-2.el6.x86_64 drbd-km-2.6.32_131.0.15.el6.x86_64-8.4.3-2.el6.x86_64 drbd-bash-completion-8.4.3-2.el6.x86_64 We plan to have our meta data on a separate partition. The partition was created with fdisk and is not having any file system created in it. The configuration files drbd.conf, global_common.conf and maildrbd.res are attached herewith for your kind reference. After configuration we were proceeding further as per the manual. While trying to enable the resources for the first time which are given as follows:- 1. Create device metadata . (drbdadm create-md r0) This step was executed successfully at both the nodes. 2. Attach to backing device. (drbdadm attach r0). This step is generating the following error :- [root@drbdtest2 ~]# drbdadm attach r0 1: Failure: (116) Lower device / meta device / index combination invalid. Command 'drbdsetup attach 1 /dev/sda2 /dev/sda2 flexible' terminated with exit code 10 [root@drbdtest2 ~]# This error is being generated at both the nodes. We tried to figure out the solution using google search but could not make much headway. Would request your help to resolve this issue. Regards, Goutam
# You can find an example in /usr/share/doc/drbd.../drbd.conf.example include "drbd.d/global_common.conf"; include "drbd.d/*.res";
global {
usage-count yes;
# minor-count dialog-refresh disable-ip-verification
}
common {
handlers {
# These are EXAMPLE handlers only.
# They may have severe implications,
# like hard resetting the node under certain circumstances.
# Be careful when chosing your poison.
# 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 {
# wfc-timeout degr-wfc-timeout outdated-wfc-timeout
wait-after-sb
}
options {
# cpu-mask on-no-data-accessible
}
disk {
# size max-bio-bvecs on-io-error fencing disk-barrier
disk-flushes
# disk-drain md-flushes resync-rate resync-after al-extents
# c-plan-ahead c-delay-target c-fill-target c-max-rate
# c-min-rate disk-timeout
}
net {
# protocol timeout max-epoch-size max-buffers unplug-watermark
# connect-int ping-int sndbuf-size rcvbuf-size ko-count
# allow-two-primaries cram-hmac-alg shared-secret after-sb-0pri
# after-sb-1pri after-sb-2pri always-asbp rr-conflict
# ping-timeout data-integrity-alg tcp-cork on-congestion
# congestion-fill congestion-extents csums-alg verify-alg
# use-rle
}
}
maildrbd.res
Description: Binary data
_______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
