DRBD UpToDate/DUnknown 故障恢复
来源:互联网 发布:剑与家园 知乎 编辑:程序博客网 时间:2024/06/11 14:46
配置drbd过程出现Primary/Unknown 故障,最后通过如下方式解决。
1, 节点状态查看
(1) 主节点状态
[root@app1 drbd.d]# cat /proc/drbd
version: 8.4.3 (api:1/proto:86-101)
GIT-hash: 89a294209144b68adb3ee85a73221f964d3ee515 build by gardner@, 2013-11-29 12:28:00
0: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r-----
ns:0 nr:0 dw:0 dr:672 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:604
[root@app1 drbd.d]#
(2) 从节点状态
[root@app2 ~]# cat /proc/drbd
version: 8.4.3 (api:1/proto:86-101)
GIT-hash: 89a294209144b68adb3ee85a73221f964d3ee515 build by gardner@, 2013-11-29 12:28:00
0: cs:StandAlone ro:Secondary/Unknown ds:UpToDate/DUnknown r-----
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:548
[root@app2 ~]#
2. 这里确认以主节点的数据为准,重新同步到从节点
(1) 停止app2 drbd服务
[root@app2 ~]# service drbd stop
Stopping all DRBD resources: .
[root@app2 ~]#
(2) 重新初始化元数据
[root@app2 ~]# drbdadm create-md data #create-md后面的是drbd资源的名称
You want me to create a v08 style flexible-size internal meta data block.
There appears to be a v08 flexible-size internal meta data block
already in place on /dev/sdb1 at byte offset 5364318208
Do you really want to overwrite the existing v08 meta-data?
[need to type 'yes' to confirm] yes
Writing meta data...
md_offset 5364318208
al_offset 5364285440
bm_offset 5364121600
Found ext3 filesystem
5238400 kB data area apparently used
5238400 kB left usable by current configuration
Even though it looks like this would place the new meta data intounused space, you still need to confirm, as this is only a guess.
Do you want to proceed?[need to type 'yes' to confirm] yes
initializing activity log
NOT initializing bitmap
lk_bdev_save(/var/lib/drbd/drbd-minor-0.lkbd) failed: No such file or directory
New drbd meta data block successfully created.
lk_bdev_save(/var/lib/drbd/drbd-minor-0.lkbd) failed: No such file or directory
(3) 启动drbd服务
[root@app2 ~]# service drbd start
Starting DRBD resources: [
create res: data
prepare disk: data
adjust disk: data
adjust net: data
]
..........
***************************************************************
DRBD's startup script waits for the peer node(s) to appear.
- In case this node was already a degraded cluster before the
reboot the timeout is 0 seconds. [degr-wfc-timeout]
- If the peer was available before the reboot the timeout will
expire after 0 seconds. [wfc-timeout]
(These values are for resource 'data'; 0 sec -> wait forever)
To abort waiting enter 'yes' [ 15]:yes
.
[root@app2 ~]# cat /proc/drbd
version: 8.4.3 (api:1/proto:86-101)
GIT-hash: 89a294209144b68adb3ee85a73221f964d3ee515 build by gardner@, 2013-11-29 12:28:00
0: cs:Connected ro:Secondary/Primary ds:UpToDate/UpToDate C r-----
ns:0 nr:5238400 dw:5238400 dr:0 al:0 bm:320 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0
[root@app2 ~]#
3. app1主节点下
(1) 主节点状态正常了
[root@app1 ~]# cat /proc/drbd
version: 8.4.3 (api:1/proto:86-101)
GIT-hash: 89a294209144b68adb3ee85a73221f964d3ee515 build by gardner@, 2013-11-29 12:28:00
0: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r-----
ns:0 nr:0 dw:0 dr:672 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:604
(2) 重启drbd之后,数据重新同步到从节点
[root@app1 ~]# service drbd reload
Reloading DRBD configuration: .
[root@app1 ~]# cat /proc/drbd
version: 8.4.3 (api:1/proto:86-101)
GIT-hash: 89a294209144b68adb3ee85a73221f964d3ee515 build by gardner@, 2013-11-29 12:28:00
0: cs:SyncSource ro:Primary/Secondary ds:UpToDate/Inconsistent C r---n-
ns:176816 nr:0 dw:0 dr:180896 al:0 bm:10 lo:4 pe:2 ua:8 ap:0 ep:1 wo:d oos:5063296
[>....................] sync'ed: 3.4% (4944/5112)M
finish: 0:00:57 speed: 87,552 (87,552) K/sec
[root@app1 ~]# cat /proc/drbd
version: 8.4.3 (api:1/proto:86-101)
GIT-hash: 89a294209144b68adb3ee85a73221f964d3ee515 build by gardner@, 2013-11-29 12:28:00
0: cs:SyncSource ro:Primary/Secondary ds:UpToDate/Inconsistent C r---n-
ns:3541004 nr:0 dw:0 dr:3545760 al:0 bm:215 lo:2 pe:4 ua:6 ap:0 ep:1 wo:d oos:1700480
[============>.......] sync'ed: 67.6% (1660/5112)M
finish: 0:00:23 speed: 71,780 (69,368) K/sec
[root@app1 ~]# cat /proc/drbd
version: 8.4.3 (api:1/proto:86-101)
GIT-hash: 89a294209144b68adb3ee85a73221f964d3ee515 build by gardner@, 2013-11-29 12:28:00
0: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
ns:5238400 nr:0 dw:0 dr:5239072 al:0 bm:320 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0
再看一下节点状态就同步了!这样就解决了脑裂情况。且保证数据都还在。
学习DRBD+Heartbeat+NFS高可用的可以点击此链接:http://blog.csdn.net/kjsayn/article/details/52871835
- DRBD UpToDate/DUnknown 故障恢复
- DRBD故障分类和恢复办法
- DRBD安装配置、工作原理及故障恢复
- drbd脑裂恢复
- DRBD Unknown故障处理过程
- drbd脑裂恢复实例
- Linux 故障恢复技巧
- 故障恢复控制台
- DC故障恢复记录
- 实例故障恢复
- AIX磁盘故障恢复
- oracle 块故障恢复
- undofile故障恢复
- 数据库故障恢复技术
- ZooKeeper 故障恢复
- ASM恢复故障组
- 磁盘故障与恢复
- drbd
- CEO的苦恼:内部提拔还是“空降”?
- Trinity简介(1)--用于无参考基因组的转录组de novo组装
- Ubuntu 12.04下NFS安装配置图解
- HDU 5726 - GCD
- SourceForge上发布dedup util
- DRBD UpToDate/DUnknown 故障恢复
- Error:Execution failed for task ':app:mergeDebugResources'. > Error: java.lang.RuntimeException: Som
- 乱用函数导致sql变慢
- LCS-51NOD-1092 回文字符串
- Ubuntu 16.04 CUDA 8 cuDNN 5.1安装
- PAT (Basic Level) Practise (中文)1015. 德才论(3种方法)
- Jade/pug-HTML模板引擎
- paint 的介绍
- 《机器学习实战》读后备忘