[DRBD-user] drbd based logical volume not getting marked active on boot

Felix Frank ff at mpexnet.de
Mon Jan 28 14:48:41 CET 2013

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


On 01/13/2013 10:14 PM, Andy Dills wrote:
> I'm trying to setup a gfs2 filesystem on a drbd 'c' volume (to facilitate 
> migration of openvz containers). 
> Everything is working great with the exception of reboots. On reboot, the 
> filesystem wasn't getting marked as active, and the only way I could get 
> the filesystem to mount on boot is to add this to rc.local:

Wait, wait, wait, wait, wait...wait. ;-)

This is a cluster file system? On DRBD? Are we talking dual-primary? Is
pacemaker not controlling this? How does the node fencing work if not?

> /sbin/lvchange -aly data/openvz
> /bin/mount -t gfs2 -o noatime,nodiratime /dev/data/openvz /containers/
> I feel like there is probably a better way to handle this. 

Pacemaker should be maintaining both drbd and gfs, I believe.


More information about the drbd-user mailing list