我有两个节点"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等等。
+--< 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)
发布于 2019-01-22 09:17:10
在我的例子中,在节点"A“(主)上,我有LVM,在节点"B”上,我有MDRAID。这一差异使我在524个272个行业的资源规模上存在差异。我为保存数据所做的一切。我以主模式运行这两个资源,将数据从"A“加载到"B",然后将节点"A”重新构建到MDRAID和同步资源。
https://stackoverflow.com/questions/54295762
复制相似问题