I found the solution by myself:
I was missing to run resize2fs /dev/drbd3 on primary node.
Now df shows the correct disk size.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Proj
I'm running a Debian cluster with corosync without LVM.
One of my resources run out of space and I had to replace the disk by a
bigger one.
Resource r3 on one whole disk.
What I did:
Put node2 in standby - crm node standby
Shutdown the server
Replaced the disk
After reboot stopped corosync - /etc
My two node email server cluster uses corosync 1.4.2.
One device (/dev/drbd3), which only holds the email data in a separated
disk, is running out of space.
To change the two disks for bigger ones I'm thinking to use the following
strategy:
1.Put node 2 in standby
2.Chan
