Bug 215890 – version bump: sys-block/drdb

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Stefan Behte (RETIRED) 2008-04-02 14:14:11 UTC]

http://www.drbd.org/
Download from: http://oss.linbit.com/drbd/8.2/drbd-8.2.5.tar.gz


   DRBD is a block device which is designed to build high availability clusters.
   This is done by mirroring a whole block device via (a dedicated) network. You
   could see it as a network raid-1.
   
   DRBD takes over the data, writes it to the local disk and sends it to the other
   host. On the other host, it takes it to the disk there.
   
   The other components needed are a cluster membership service, which is supposed
   to be heartbeat, and some kind of application that works on top of a block
   device.
   
   Each device (DRBD provides more than one of these devices) has a state, which
   can be 'primary' or 'secondary'. On the node with the primary device the
   application is supposed to run and to access the device (/dev/drbdX; used to be
   /dev/nbX). Every write is sent to the local 'lower level block device' and to
   the node with the device in 'secondary' state. The secondary device simply
   writes the data to its lower level block device. Reads are always carried out
   locally.
   
   If the primary node fails, heartbeat is switching the secondary device into
   primary state and starts the application there. (If you are using it with a
   non-journaling FS this involves running fsck)
   
   If the failed node comes up again, it is a new secondary node and has to
   synchronise its content to the primary. This, of course, will happen whithout
   interruption of service in the background. 
   
   And, of course, we only will resynchronize those parts of the device that
   actually have been changed. DRBD has always done intelligent resynchronization
   when possible. Starting with the DBRD-0.7 series, you can define an "active
   set" of a certain size. This makes it possible to have a total resync time of
   1--3 min, regardless of device size (currently up to 4TB), even after a hard
   crash of an active node.

[Comment 1 Richard Scott 2008-04-04 10:57:28 UTC]

its already done:

# emerge -s drbd
Searching...
[ Results for search key : drbd ]
[ Applications found : 2 ]

*  sys-cluster/drbd
      Latest version available: 8.0.11
      Latest version installed: 8.0.11
      Size of files: 311 kB
      Homepage:      http://www.drbd.org
      Description:   mirror/replicate block-devices across a network-connection
      License:       GPL-2

*  sys-cluster/drbd-kernel
      Latest version available: 8.0.11
      Latest version installed: 8.0.11
      Size of files: 311 kB
      Homepage:      http://www.drbd.org
      Description:   mirror/replicate block-devices across a network-connection
      License:       GPL-2

[Comment 2 Stefan Behte (RETIRED) 2008-04-05 14:14:18 UTC]

I had also searched, and wondered why I did not find it: from my .bash_history I can see that I accidently searched for drDB instead of drBD, damn.
Closing.