[DRBD-user] some doubt using drbd 7.2

Martin Bene martin.bene at icomedias.com
Wed Aug 18 07:53:19 CEST 2004

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


Hi German,

> 1- What is the best way for to integrate it with
> heartbeat since the datadisk changed by drbdisk ? 
>  I remember that datadisk do the work for switch
> primary / secondary and mount and umount partition. On
> 7.2 ( if i not mistake ) only swith , but not mount /
> umount partition . Let me know a good way for to do
> it.

Example from my haressources file:

test-neu1       10.192.64.63 \
                drbddisk::drbd1
Filesystem::/dev/drbd1::/var/dbase::jfs::noatime \
                postgresql pg_autovacuum
MailTo::support at icomedias.com::test-neu-db

So mount/unmount is handled by using the  "Filesystem" ressource script
provided with heartbeat.

> 2- If one of my two nodes fail (disk corruption , hw
> problems , etc) and i need to change a new one for
> recovery the redundance, How can i do for to
> recontruct DrBd ? ( forcing syncs , etc ) .

If you're using internal metadata, drbd should realize that the disk is
new and resync by itself. If you want to explicitely resync a device you
can use "drbdadm invalidate <ressource>" on the side with bad data.

> 4- How can i monitoring that DRBD is working well
> without testing switchover ?

You'll definitely want to try failovers before putting a system in
production. you can monitor current status of drbd by checking the
information from cat /proc/drbd.

Bye, Martin




More information about the drbd-user mailing list