Commit 64189e31 authored by Philipp Reisner's avatar Philipp Reisner

DRBD: final

Kconfig integration, Makefile and major.h
Signed-off-by: default avatarPhilipp Reisner <philipp.reisner@linbit.com>
Signed-off-by: default avatarLars Ellenberg <lars.ellenberg@linbit.com>
parent 11e154b8
...@@ -271,6 +271,8 @@ config BLK_DEV_CRYPTOLOOP ...@@ -271,6 +271,8 @@ config BLK_DEV_CRYPTOLOOP
instead, which can be configured to be on-disk compatible with the instead, which can be configured to be on-disk compatible with the
cryptoloop device. cryptoloop device.
source "drivers/block/drbd/Kconfig"
config BLK_DEV_NBD config BLK_DEV_NBD
tristate "Network block device support" tristate "Network block device support"
depends on NET depends on NET
......
...@@ -35,5 +35,6 @@ obj-$(CONFIG_BLK_DEV_UB) += ub.o ...@@ -35,5 +35,6 @@ obj-$(CONFIG_BLK_DEV_UB) += ub.o
obj-$(CONFIG_BLK_DEV_HD) += hd.o obj-$(CONFIG_BLK_DEV_HD) += hd.o
obj-$(CONFIG_XEN_BLKDEV_FRONTEND) += xen-blkfront.o obj-$(CONFIG_XEN_BLKDEV_FRONTEND) += xen-blkfront.o
obj-$(CONFIG_BLK_DEV_DRBD) += drbd/
swim_mod-objs := swim.o swim_asm.o swim_mod-objs := swim.o swim_asm.o
#
# DRBD device driver configuration
#
config BLK_DEV_DRBD
tristate "DRBD Distributed Replicated Block Device support"
select INET
select PROC_FS
select CONNECTOR
select CRYPTO
select CRYPTO_HMAC
---help---
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.
Each minor device 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). Every write is sent to the
local 'lower level block device' and via network to the node with the
device in 'secondary' state.
The secondary device simply writes the data to its lower level block
device. Currently no read-balancing via the network is done.
DRBD can also be used with "shared-disk semantics" (primary-primary),
even though it is a "shared-nothing cluster". You'd need to use a
cluster file system on top of that for cache coherency.
DRBD management is done through user-space tools.
For automatic failover you need a cluster manager (e.g. heartbeat).
See also: http://www.drbd.org/, http://www.linux-ha.org
If unsure, say N.
#CFLAGS_drbd_sizeof_sanity_check.o = -Wpadded # -Werror
drbd-objs := drbd_buildtag.o drbd_bitmap.o drbd_proc.o \
drbd_worker.o drbd_receiver.o drbd_req.o drbd_actlog.o \
lru_cache.o drbd_main.o drbd_strings.o drbd_nl.o
obj-$(CONFIG_BLK_DEV_DRBD) += drbd.o
...@@ -145,6 +145,7 @@ ...@@ -145,6 +145,7 @@
#define UNIX98_PTY_MAJOR_COUNT 8 #define UNIX98_PTY_MAJOR_COUNT 8
#define UNIX98_PTY_SLAVE_MAJOR (UNIX98_PTY_MASTER_MAJOR+UNIX98_PTY_MAJOR_COUNT) #define UNIX98_PTY_SLAVE_MAJOR (UNIX98_PTY_MASTER_MAJOR+UNIX98_PTY_MAJOR_COUNT)
#define DRBD_MAJOR 147
#define RTF_MAJOR 150 #define RTF_MAJOR 150
#define RAW_MAJOR 162 #define RAW_MAJOR 162
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment