Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
The configurations SHOULD match to simplify maintenance, but server A will completely ignore server B settings, and server B will completely ignore server A settings. Your config is being read by the servers as:
Host A:
resource r0 {
on ME {
device /dev/drbd0;
disk /dev/vg01/share;
address 2.2.2.150:7788;
meta-disk internal;
}
}
and Host B is like this:
resource r0 {
on ME {
device /dev/drbd0;
disk /dev/vg02/share;
address 2.2.2.151:7788;
meta-disk internal;
}
}
Which is (I believe) what you wanted.
Dan
From: drbd-user-bounces at lists.linbit.com [mailto:drbd-user-bounces at lists.linbit.com] On Behalf Of ??
Sent: Friday, May 18, 2012 3:20 AM
To: drbd-user
Subject: [DRBD-user] drbd wrong lower device doubt
Hi All, I have some doubts about drbd. I have configure two servers as Host A and Host B. Host A drbd configuration is like this:
resource r0 {
on A {
device /dev/drbd0;
disk /dev/vg01/share;
address 2.2.2.150:7788;
meta-disk internal;
}
on B {
device /dev/drbd0;
disk /dev/vg01/share;
address 2.2.2.151:7788;
meta-disk internal;
}
}
and Host B is like this:
resource r0 {
on A {
device /dev/drbd0;
disk /dev/vg02/share;
address 2.2.2.150:7788;
meta-disk internal;
}
on B {
device /dev/drbd0;
disk /dev/vg02/share;
address 2.2.2.151:7788;
meta-disk internal;
}
}
You can notice that Host A and Host B configuration file is not same. Actually Host A lower device is /dev/vg01/share and Host B lower device is /dev/vg02/share. The specified destination lower device is wrong in each server. Network setting is right . I set Host A disk state to UpToDate and Host B disk state inconsistent. I find that Host A is syncing to Host B. Why it can work regularly when I configure wrong lower device.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20120518/fbd189a5/attachment.htm>