[DRBD-user] Re: Non persistant root drive ( booting from compactflash rom).

Brett Bolen hbbolen at yahoo.com
Wed Mar 2 17:27:16 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.

Lars Ellenberg wrote:
> / 2005-03-01 14:51:04 -0500
> \ Brett Bolen:
>>I noticed on a sidebar on the drbd article, that drbd uses
>>a directory in /var ( maybe /var/lib/drbd ) for 'meta-data'
>>which is used to determine which drive to sync from.
> that is drbd 0.6 and before.
> drbd 0.7 uses a block device for its meta data.

That sounds like good news.  But what block device --
/dev/drbd0 ( ala /dev/sda1)?

>>We have a system that boots from a compact flash  -- the
>>init ram drive is a file that is unzipped to make the root
>>file system.  This means that there is no persistant data
>>across reboots.
>>Does this pose a problem for drbd?

> if drbd (or other cluster software) had no persistent meta data,
> how could be determined which of the nodes is consistent and up-to-date ?

The /dev/drbd0 device is mapped onto /dev/sda1 ( or actually a pair of 
/dev/sda1's on seperate computers), which is persistent.

Is this sufficient for the meta-data requirement?

>>We are using this for a ha-nfs -- and use real disks for the nfs
> with drbd 0.7 you should be fine, still.

Thanks.  This is great stuff...


More information about the drbd-user mailing list