Directory Files
.. 31
File Size
Kconfig 2.5 kB
Makefile 348 B
drbd.mod.c 0 B
drbd_actlog.c 38 kB
drbd_bitmap.c 49 kB
drbd_buildtag.c 443 B
drbd_debugfs.c 28 kB
drbd_debugfs.h 1.6 kB
drbd_int.h 79 kB
drbd_interval.c 4.2 kB
drbd_interval.h 1.4 kB
drbd_main.c 111 kB
drbd_nl.c 148 kB
drbd_nla.c 1.5 kB
drbd_nla.h 332 B
drbd_polymorph_printk.h 5.2 kB
drbd_proc.c 10 kB
drbd_protocol.h 13 kB
drbd_receiver.c 181 kB
drbd_req.c 57 kB
drbd_req.h 11 kB
drbd_state.c 75 kB
drbd_state.h 6.5 kB
drbd_state_change.h 2.0 kB
drbd_strings.c 3.9 kB
drbd_strings.h 344 B
drbd_vli.h 11 kB
drbd_worker.c 66 kB

Linux v6.4-rc4 - drbd

# SPDX-License-Identifier: GPL-2.0-only
# DRBD device driver configuration

comment "DRBD disabled because PROC_FS or INET not selected"
	depends on PROC_FS='n' || INET='n'

	tristate "DRBD Distributed Replicated Block Device support"
	depends on PROC_FS && INET
	select LRU_CACHE
	select LIBCRC32C

	  NOTE: In order to authenticate connections you have to select
	  CRYPTO_HMAC and a hash function as well.

	  DRBD is a shared-nothing, synchronously replicated block device. It
	  is designed to serve as a building block for high availability
	  clusters and in this context, is a "drop-in" replacement for shared
	  storage. Simplistically, you could see it as a network RAID 1.

	  Each minor device has a role, 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, across the network, to the
	  node with the device in 'secondary' state.  The secondary device
	  simply writes the data to its lower level block device.

	  DRBD can also be used in dual-Primary mode (device writable on both
	  nodes), which means it can exhibit shared disk semantics in a
	  shared-nothing cluster.  Needless to say, on top of dual-Primary
	  DRBD utilizing a cluster file system is necessary to maintain for
	  cache coherency.

	  For automatic failover you need a cluster manager (e.g. heartbeat).
	  See also:,

	  If unsure, say N.

	bool "DRBD fault injection"
	depends on BLK_DEV_DRBD

	  Say Y here if you want to simulate IO errors, in order to test DRBD's

	  The actual simulation of IO errors is done by writing 3 values to

	  enable_faults: bitmask of...
	  1	meta data write
	  2               read
	  4	resync data write
	  8	            read
	  16	data write
	  32	data read
	  64	read ahead
	  128	kmalloc of bitmap
	  256	allocation of peer_requests
	  512	insert data corruption on receiving side

	  fault_devs: bitmask of minor numbers
	  fault_rate: frequency in percent

	  Example: Simulate data write errors on /dev/drbd0 with a probability of 5%.
		echo 16 > /sys/module/drbd/parameters/enable_faults
		echo 1 > /sys/module/drbd/parameters/fault_devs
		echo 5 > /sys/module/drbd/parameters/fault_rate

	  If unsure, say N.