|
Centos 7: DRBD: Configuring a resource: Parsing errors
Been bashing my head against this issue for two weeks. Reaching out for help. I am trying to implement CLVM with Pacemaker/Corosync, and am stuck in the process of creating the resource needed to replicate data on an LVM. I have tried to follow examples from the Pacemaker manual and the DRBD website, and am getting parsing errors. What follows is the error, along with two attempts at creating the resource.
This is the error on the production servers
conflicting use of disk 'disk:rhapsody-prd-01:/dev/mapper/vg01-rhapsody' ...
drbd.d/datastore.res:16: disk 'disk:rhapsody-prd-01:/dev/mapper/vg01-rhapsody' first used here.
drbd.d/datastore.res:16: conflicting use of disk 'disk:rhapsody-prd-01:/dev/mapper/vg01-rhapsody' ...
drbd.d/datastore.res:16: disk 'disk:rhapsody-prd-01:/dev/mapper/vg01-rhapsody' first used here.
The following are two different resource configurations:
--- Config 1 (based on the Pacemaker manual) ---
resource wwwdata {
protocol C;
meta-disk internal;
device /dev/drbd1;
syncer {
verify-alg sha1;
}
on rhapsody-prd-01 {
disk /dev/vg01/rhapsody/drbd-demo;
address <node1IP>:7789;
on rhapsody-prd-02 {
disk /dev/vg01/rhapsody/drbd-demo;
address <node2IP>:7789;
}
}
--- Config 1 ---
--- Config 2 (Based on the DRBD Usage Guide) ----
resource datastore {
volume 0 {
device /dev/drbd1;
disk /dev/mapper/vg01-rhapsody;
meta-disk internal;
}
volume 1 {
device /dev/drbd2;
disk /dev/mapper/vg01-rhapsody;
meta-disk internal;
}
on rhapsody-prd-01 {
address <node1 IP>:7789;
}
on rhapsody-prd-02 {
address <node2 IP>:7789;
}
}
--- Config 2 ---
NOTE: Both of the above configurations have proper formatting (tabs, indent,etc). Unfortunately, once it gets posted, all the text gets aligned left
Both yield the same result, the error shown above. I tried a third different way, and got a different error. I have tried this on the production server that is being prepared for a live deployment, and on VMs that I am running on VirtualBox. I get different results. The Pacemaker documentation itself says that there are multiple ways to create a data replication resource, so I have tried to create one based on examples that I have seen in other websites. No luck. My suspicion is that the config file needs to adhere to a strict syntax, similar to python, and am not able to pin down what the rules are (tabbed categories, curly brace placement, etc).
Anyone have any suggestions for how to create a DRBD resource that can create data redundancy for CLVM? Wanted to reach out for help as I seem to be getting a similar error for multiple attempts. Thanks in advance.
Last edited by Bluestreak; 09-21-2015 at 07:01 PM.
Reason: Typo and removed acronym
|
