我有两个节点“ A”(主要)和“ B”。每个节点有3个资源。在节点“ B”上,我替换磁盘,然后将每个资源添加为辅助资源。两种资源成功连接并同步,但是只有一种资源存在问题。当在节点“ B”上停止该资源时,节点“ A”显示
lv1 role:Primary
disk:UpToDate
b.host connection:Connecting
当我在节点“ B”上启动此资源时,节点“ A”显示:
lv1 role:Primary
disk:UpToDate
b.host connection:StandAlone
节点“ B”显示:
lv1 role:Secondary
disk:Inconsistent
a.host connection:Connecting
我会尝试一切,删除/添加资源,节点“ B”上的元数据,删除数据,重建RAID drbdadm connect lv1 --discard-my-data
等。
工作中断的资源之间的区别是This node was a crashed primary, and has not seen its peer since
+--< Current data generation UUID >-
| +--< Bitmap's base data generation UUID >-
| | +--< younger history UUID >-
| | | +-< older history >-
V V V V
E43824C7BC375B4A:626476078D91E933:CC1DC3FAD143EDCC:E4E71860FBA887C2:1:1:1:1:0:0:0:0:0:0:0:1
^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^
-< Data consistency flag >--+ | | | | | | | | | | |
-< Data was/is currently up-to-date >--+ | | | | | | | | | |
-< Node was/is currently primary >--+ | | | | | | | | |
-< This node was a crashed primary, and has not seen its peer since >--+ | | | | | | | |
-< The activity-log was applied, the disk can be attached >--+ | | | | | | |
-< The activity-log was disabled, peer is completely out of sync >--+ | | | | | |
-< This node was primary when it lost quorum >--+ | | | | |
-< Node was/is currently connected >--+ | | | |
-< The peer's disk was out-dated or inconsistent >--+ | | |
-< A fence policy other the dont-care was used >--+ | |
-< Node was in the progress of marking all blocks as out of sync >--+ |
-< At least once we saw this node with a backing device attached >--+
有什么想法我可以解决吗?
UPD::找到新的差异a kernel: drbd lv1/0 drbd1 b.host: The peer's disk size is too small! (999671944 < 1000196216 sectors)
答案 0 :(得分:0)
在我的情况下,在节点“ A”(主)上,我有LVM,在节点“ B”上,我有MDRAID。这种差异使我在524272个行业中的资源规模有所不同。我要如何保存我的数据。我在主模式下运行这两个资源,将数据从“ A”装入并复制到“ B”,然后将节点“ A”重建到MDRAID并同步资源。