[DRBD-user] Behaviour of drbd-secondary

Helmut Wollmersdorfer helmut.wollmersdorfer at gmx.at
Wed Mar 23 13:50:40 CET 2005

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

Philipp Reisner wrote:

> Please hold you feets still until DRBD-0.8 is released. In DRBD-0.8 we
> will support primary/primary, and with on of OCFS2, openGFS or GFS
> you will be able to build such a setup.

Do I understand correctly, that plain FSs like EXT3 or XFS could not be 
used, because of missing appropriate lock-mechanisms? And mounting 
read-only of EXT3/XFS on the DRBD-Secondary will also not be possible?

Just thinking loud, where such features can be useful in my 
current/planned configuration:

- daily.cron with logrotate pushes CPU-usage to 60% which can grow and 
get a serious bottleneck. Placing it on the secondary makes no sense, 
because apache-logrotate does an apache-restart, which needs to be on 
the primary. But running log-analyzer on the secondary can make sense - 
read only would be enough.

- running a mirror of very large dictd-dictionaries, which consume large 
amounts of HDD-space and memory. Running it with the public 
web-interface on the primary, and running a web-robot querying dictd 
heavily on the secondary can make sense. Read only would be enough. But 
I am not sure, which configuration would have wich performance:
1) dict on GFS used by both nodes
2) dict on EXT3/XFS queried over IP:Port by both nodes
3) splitting the dicts logically, queried criss-cross by both nodes over 

Last question:
Can you expect a ready-to-test date for 0.8?

Helmut Wollmersdorfer

More information about the drbd-user mailing list