DRBD

wget  http://oss.linbit.com/drbd/8.4/drbd-8.4.4.tar.gz
export LC_ALL=C 
vi /etc/profile增加export LC_ALL=C并执行source /etc/profile
tar -zxf drbd-8.4.4.tar.gz && cd  drbd-8.4.4
 ./configure --prefix=/application/drbd8.4.4 --with-km --with-heartbeat --sysconfdir=/etc/
#--with-km  Enable kernel module
#--with-heartbeat  Enable Heartbeat integration
make KDIR=/usr/src/kernels/$(uname -r)/    #指定内核源码路径（若无yum install kernel-devel）
make install
modprobe drbd
lsmod | grep drbd
drbd                  372759  0 
libcrc32c               1246  1 drbd
echo "modprobe drbd" >>/etc/sysconfig/modules/drbd.modules
chmod 755 /etc/sysconfig/modules/drbd.modules

global {
# minor-count 64;
# dialog-refresh 5; # 5 seconds
# disable-ip-verification;
usage-count no;
}

common {
protocol C;
disk {
on-io-error   detach;
#size 454G;
no-disk-flushes;
no-md-flushes;
}

net {
sndbuf-size 512k;
# timeout       60;    #  6 seconds  (unit = 0.1 seconds)
# connect-int   10;    # 10 seconds  (unit = 1 second)
# ping-int      10;    # 10 seconds  (unit = 1 second)
# ping-timeout   5;    # 500 ms (unit = 0.1 seconds)
max-buffers     8000;
unplug-watermark   1024;
max-epoch-size  8000;
# ko-count 4;
# allow-two-primaries;
cram-hmac-alg "sha1";
shared-secret "hdhwXes23sYEhart8t";
after-sb-0pri disconnect;
after-sb-1pri disconnect;
after-sb-2pri disconnect;
rr-conflict disconnect;
# data-integrity-alg "md5";
# no-tcp-cork;
}

syncer {
rate 120M;
al-extents 517;
}

}

resource data {
on data-1-1 {
device     /dev/drbd0;
disk       /dev/sdb1;
address    192.168.1.91:7788;
meta-disk  /dev/sdb2[0];
}

on data-1-2 {
device     /dev/drbd0;
disk       /dev/sdb1;
address    192.168.1.92:7788;
meta-disk  /dev/sdb2[0];
}
}

 The resource-specific output from/proc/drbd contains various pieces ofinformation about the resource:
*cs(connection state). Status of the network connection. See the section called “Connection states” for details about the various connection states.
*ro(roles). Roles of the nodes. The role of the local node isdisplayed first, followed by the role of the partnernode shown after the slash. See the section called “Resource roles” for details about thepossible resource roles.
*ds(disk states). State of the hard disks. Prior to the slash thestate of the local node is displayed, after the slashthe state of the hard disk of the partner node isshown. See the section called “Disk states” for details about the variousdisk states.
*ns(network send). Volume of net data sent to the partner via thenetwork connection; in Kibyte.
*nr(network receive). Volume of net data received by the partner viathe network connection; in Kibyte.
*dw(disk write). Net data written on local hard disk; inKibyte.
*dr(disk read). Net data read from local hard disk; in Kibyte.
*al(activity log). Number of updates of the activity log area of the metadata.
*bm(bit map). Number of updates of the bitmap area of the metadata.
*lo(local count). Number of open requests to the local I/O sub-systemissued by DRBD.
*pe(pending). Number of requests sent to the partner, but thathave not yet been answered by the latter.
*ua(unacknowledged). Number of requests received by the partner via thenetwork connection, but that have not yet beenanswered.
*ap(application pending). Number of block I/O requests forwarded to DRBD, butnot yet answered by DRBD.
*ep(epochs). Number of epoch objects. Usually 1. Might increaseunder I/O load when using either thebarrier or the nonewriteordering methd. Since 8.2.7.
*wo(write order). Currently used write ordering method:b (barrier), f(flush),d(drain) or n(none). Since8.2.7.
*oos(out of sync). Amount of storage currently out of sync; inKibibytes. Since 8.2.6. 

A resource may have one of the following connectionstates: 
*StandAlone. No network configuration available. The resourcehas not yet been connected, or has beenadministratively disconnected (using drbdadm disconnect), or has dropped its connectiondue to failed authentication or split brain.   独立的：网络配置不可用；资源还没有被连接或是被管理断开（使用 drbdadm disconnect 命令），或是由于出现认证失败或是脑裂的情况
*Disconnecting. Temporary state during disconnection. The nextstate is StandAlone. 断开：断开只是临时状态，下一个状态是StandAlone独立的
*Unconnected. Temporary state, prior to a connection attempt.Possible next states: WFConnection andWFReportParams. 悬空：是尝试连接前的临时状态，可能下一个状态为WFconnection和WFReportParams
*Timeout. Temporary state following a timeout in thecommunication with the peer. Next state:Unconnected. 超时：与对等节点连接超时，也是临时状态，下一个状态为Unconected悬空
*BrokenPipe. Temporary state after the connection to the peerwas lost. Next state: Unconnected. 与对等节点连接丢失，也是临时状态，下一个状态为Unconected悬空
*NetworkFailure. Temporary state after the connection to thepartner was lost. Next state: Unconnected. 与对等节点推动连接后的临时状态，下一个状态为Unconected悬空
*ProtocolError. Temporary state after the connection to thepartner was lost. Next state: Unconnected. 与对等节点推动连接后的临时状态，下一个状态为Unconected悬空
*TearDown. Temporary state. The peer is closing theconnection. Next state: Unconnected. 拆解：临时状态，对等节点关闭，下一个状态为Unconected悬空
*WFConnection. This node is waiting until the peer node becomesvisible on the network. 等待和对等节点建立网络连接
*WFReportParams. TCP connection has been established, this nodewaits for the first network packet from thepeer. 已经建立TCP连接，本节点等待从对等节点传来的第一个网络包
*Connected. A DRBD connection has been established, datamirroring is now active. This is the normalstate. 连接：DRBD已经建立连接，数据镜像现在可用，节点处于正常状态
*StartingSyncS. Full synchronization, initiated by theadministrator, is just starting. The next possiblestates are: SyncSource or PausedSyncS. 完全同步，有管理员发起的刚刚开始同步，未来可能的状态为SyncSource或PausedSyncS
*StartingSyncT. Full synchronization, initiated by theadministrator, is just starting. Next state:WFSyncUUID. 完全同步，有管理员发起的刚刚开始同步，下一状态为WFSyncUUID
*WFBitMapS. Partial synchronization is just starting. Nextpossible states: SyncSource or PausedSyncS. 部分同步刚刚开始，下一步可能的状态为SyncSource或PausedSyncS
*WFBitMapT. Partial synchronization is just starting. Nextpossible state: WFSyncUUID. 部分同步刚刚开始，下一步可能的状态为WFSyncUUID
*WFSyncUUID. Synchronization is about to begin. Next possiblestates: SyncTarget or PausedSyncT. 同步即将开始，下一步可能的状态为SyncTarget或PausedSyncT
*SyncSource. Synchronization is currently running, with thelocal node being the source ofsynchronization. 以本节点为同步源的同步正在进行
*SyncTarget. Synchronization is currently running, with thelocal node being the target ofsynchronization. 以本节点为同步目标的同步正在进行
*PausedSyncS. The local node is the source of an ongoingsynchronization, but synchronization is currentlypaused. This may be due to a dependency on thecompletion of another synchronization process, ordue to synchronization having been manuallyinterrupted by drbdadm pause-sync. 以本地节点是一个持续同步的源，但是目前同步已经暂停，可能是因为另外一个同步正在进行或是使用命令(drbdadm pause-sync)暂停了同步
*PausedSyncT. The local node is the target of an ongoingsynchronization, but synchronization is currentlypaused. 以本地节点为持续同步的目标，但是目前同步已经暂停，这可以是因为另外一个同步正在进行或是使用命令(drbdadm pause-sync)暂停了同步This may be due to a dependency on thecompletion of another synchronization process, ordue to synchronization having been manuallyinterrupted by drbdadm pause-sync. 
*VerifyS. On-line device verification is currently running,with the local node being the source ofverification. 以本地节点为验证源的线上设备验证正在执行
*VerifyT. On-line device verification is currently running,with the local node being the target ofverification. 以本地节点为验证目标的线上设备验证正在执行

本地和对等节点的硬盘有可能为下列状态之一：
Diskless     无盘：本地没有块设备分配给DRBD使用，这表示没有可用的设备，或者使用drbdadm命令手工分离或是底层的I/O错误导致自动分离
Attaching：    读取无数据时候的瞬间状态
Failed         失败：本地块设备报告I/O错误的下一个状态，其下一个状态为Diskless无盘
Negotiating：    在已经连接的DRBD设置进行Attach读取无数据前的瞬间状态
Inconsistent：    数据是不一致的，在两个节点上（初始的完全同步前）这种状态出现后立即创建一个新的资源。此外，在同步期间（同步目标）在一个节点上出现这种状态
Outdated：    数据资源是一致的，但是已经过时
DUnknown：    当对等节点网络连接不可用时出现这种状态
Consistent：    一个没有连接的节点数据一致，当建立连接时，它决定数据是UpToDate或是Outdated
UpToDate：    一致的最新的数据状态，这个状态为正常状态