Please forgive me for the confusing reply I sent before. My crappy email
cliente isn´t adding the char > on the original message so Ill do it by hand
:-(
Hi,
I would just try to remove the last 2 lines in the "net" column of DRBD
Config. I had the same behavior with the option "ping-timeou
Hi Matthias.
Tank you for the quick reply.
I would just try to remove the last 2 lines in the "net" column of DRBD
Config. I had the same behavior with the option "ping-timeout" in the "net"
column.
Starting DRBD via init-script worked but not managed via pacemaker.
Just try it!
I am still
Hi,
I would just try to remove the last 2 lines in the "net" column of DRBD Config.
I had the same behavior with the option "ping-timeout" in the "net" column.
Starting DRBD via init-script worked but not managed via pacemaker.
Just try it!
I am still investigating the reason for that.
Additiona
Hi.
I configured one cluster using one resouce of DRBD and it works fine,
althoug I had to downgrade the kernel to the version 2.6.37.6 to get it
stable.
Now I´m configuring another cluster but two DRBD resources are required.
They were created and if I use the system init script to start them
