Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Is this the correct way to add additional resources to the same host?
startup {
wfc-timeout 0; ## Infinite!
degr-wfc-timeout 60; ## 2 minutes.
}
disk {
on-io-error detach;
}
net {
# timeout 60;
# connect-int 10;
# ping-int 10;
# max-buffers 2048;
# max-epoch-size 2048;
}
syncer {
rate 120M;
al-extents 257;
}
on dolphins.transolutions.net {
device /dev/drbd0;
disk /dev/VolGroup01/test;
address 192.168.5.2:7789;
meta-disk internal;
}
on patriots.transolutions.net {
device /dev/drbd0;
disk /dev/VolGroup01/test;
address 192.168.5.6:7789;
meta-disk internal;
}
}
resource livetime {
protocol C;
startup {
wfc-timeout 0; ## Infinite!
degr-wfc-timeout 60; ## 2 minutes.
}
disk {
on-io-error detach;
}
net {
# timeout 60;
# connect-int 10;
# ping-int 10;
# max-buffers 2048;
# max-epoch-size 2048;
}
syncer {
rate 60M;
al-extents 257; }
on dolphins.transolutions.net {
device /dev/drbd1;
disk /dev/VolGroup02/livetime-u01;
address 192.168.5.2:7790;
meta-disk internal;
}
on patriots.transolutions.net {
device /dev/drbd1;
disk /dev/VolGroup02/livetime-u01;
address 192.168.5.6:7790;
meta-disk internal;
}
}
resource zimbra {
protocol C;
startup {
wfc-timeout 0; ## Infinite!
degr-wfc-timeout 60; ## 2 minutes.
}
disk {
on-io-error detach;
}
net {
# timeout 60;
# connect-int 10;
# ping-int 10;
# max-buffers 2048;
# max-epoch-size 2048;
}
syncer {
rate 60M;
al-extents 257;
}
on dolphins.transolutions.net {
device /dev/drbd2;
disk /dev/VolGroup02/zimbra-u01;
address 192.168.5.2:7791;
meta-disk /dev/VolGroup01/drbd-metadata[0];
}
on patriots.transolutions.net {
device /dev/drbd2;
disk /dev/VolGroup02/zimbra-u01;
address 192.168.5.6:7791;
meta-disk /dev/VolGroup01/drbd-metadata[0];
}
}