[DRBD-user] DRDB Failover Not Right - Not Replicating Share

chalmc80 chrissychalm at hotmail.co.uk
Mon Dec 26 21:13:28 CET 2011

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


Hi, 

Please help me! 

I have my DRBD setup with two nodes, using software raid for storage as
/dev/md0.

I have followed these instructions
http://www.howtoforge.com/openfiler-2.99-active-passive-with-corosync-pacemaker-and-drbd.
Same LVM being /dev/data/filer. I then made a share called VMs and attached
it in ESXi with some files copied to it for testing.

The problem is that when I fail over my primary node, the new share that I
created didn't move. The /data/filer is made but not the share below it.
Whats going wrong? What am I missing? 

I have tried:
- Invalidating the secondary node and letting everything copy across
- Running vgscan after changing the filter in /etc/lvm/lvm.conf (as
instructed)

When I then bring my primary back online the share is still there with the
files so hasn't been deleted or anything.

I have searched online and also on here but can't find anything. 

Really appreciate it if you could help me :-(

-- 
View this message in context: http://old.nabble.com/DRDB-Failover-Not-Right---Not-Replicating-Share-tp33039171p33039171.html
Sent from the DRBD - User mailing list archive at Nabble.com.




More information about the drbd-user mailing list