dracut

package: dracut

title: dracut(8)

summary: low\-level tool for generating an initramfs/initrd image

text:
# dracut(8)

## NAME
dracut - low-level tool for generating an initramfs/initrd image

## SYNOPSIS
dracut [OPTION...] [<image> [<kernel version>]]

## DESCRIPTION
Create an initramfs <image> for the kernel with the version <kernel version>. If <kernel version> is omitted, then the version of the actual running kernel is used. If <image> is omitted or empty, the default location will be determined by the local configuration or Linux distribution policy.

dracut creates an initial image used by the kernel for preloading the block device modules (such as IDE, SCSI or RAID) which are needed to access the root filesystem, mounting the root filesystem and booting into the real system.

At boot time, the kernel unpacks that archive into RAM disk, mounts and uses it as initial root file system. All finding of the root device happens in this early userspace.

Initramfs images are also called "initrd".

For a complete list of kernel command line options see man:dracut.cmdline[7].

If you are dropped to an emergency shell, while booting your initramfs, the file /run/initramfs/rdsosreport.txt is created, which can be saved to a (to be mounted by hand) partition (usually /boot) or a USB stick. Additional debugging info can be produced by adding rd.debug to the kernel command line. /run/initramfs/rdsosreport.txt contains all logs and the output of some tools. It should be attached to any report about dracut problems.

Dracut is expected to run as the root user to have unrestricted access to the root filesystem during initramfs generation. Running dracut as any user other than root supports only a limited set of functionalities. As an example, to facilitate secure sulogin in the emergency console with the host password requires read access to /etc/shadow on the host, which is usually only allowed for the root user.

## USAGE
To create a initramfs image, the most simple command is:

```
# dracut
```

This will generate a general purpose initramfs image, with all possible functionality resulting of the combination of the installed dracut modules and system tools. The image contains the kernel modules of the currently active kernel with version <kernel-version>. The default location of the image is determined by the local configuration or Linux distribution policy.

If the initramfs image already exists, dracut will display an error message, and to overwrite the existing image, you have to use the --force option.

```
# dracut --force
```

If you want to specify another filename for the resulting image you would issue a command like:

```
# dracut foobar.img
```

To generate an image for a specific kernel version, the command would be:

```
# dracut foobar.img 2.6.40-1.rc5.f20
```

A shortcut to generate the image at the default location for a specific kernel version is:

```
# dracut --kver 2.6.40-1.rc5.f20
```

If you want to create lighter, smaller initramfs images, you may want to specify the --hostonly or -H option. Using this option, the resulting image will contain only those dracut modules, kernel modules and filesystems, which are needed to boot this specific machine. This has the drawback, that you can’t put the disk on another controller or machine, and that you can’t switch to another root filesystem, without recreating the initramfs image. It is recommended to keep a copy of a general purpose image (and corresponding kernel) as a fallback to rescue your system.

## INSPECTING THE CONTENTS
To see the contents of the image created by dracut, you can use the lsinitrd tool.

```
# lsinitrd | less
```

To display the contents of a file in the initramfs also use the lsinitrd tool:

```
# lsinitrd -f /etc/ld.so.conf
include ld.so.conf.d/*.conf
```

## ADDING DRACUT MODULES
Some dracut modules are turned off by default and have to be activated manually. You can do this by adding the dracut modules to the configuration file /etc/dracut.conf or /etc/dracut.conf.d/myconf.conf. See man:dracut.conf[5] You can also add dracut modules on the command line by using the -a or --add option:

```
# dracut --add module initramfs-module.img
```

To see a list of available dracut modules, use the --list-modules option:

```
# dracut --list-modules
```

Tip Omitted modules will override added modules. --force-add can be used

to add a module in host-only mode if it is specified as omitted (usually via a distribution configuration file).

## OMITTING DRACUT MODULES
Sometimes you don’t want a dracut module to be included for reasons of speed, size or functionality. To do this, either specify the omit_dracutmodules variable in the dracut.conf or /etc/dracut.conf.d/myconf.conf configuration file (see man:dracut.conf[5]) or use the -o or --omit option on the command line:

```
# dracut -o "multipath lvm" no-multipath-lvm.img
```

## ADDING KERNEL MODULES
If you need a special kernel module in the initramfs, which is not automatically picked up by dracut, you have the use the --add-drivers option on the command line or the drivers variable in the /etc/dracut.conf or /etc/dracut.conf.d/myconf.conf configuration file (see man:dracut.conf[5]):

```
# dracut --add-drivers mymod initramfs-with-mymod.img
```

## BOOT PARAMETERS
An initramfs generated without the "hostonly" mode, does not contain any system configuration files (except for some special exceptions), so the configuration has to be done on the kernel command line. With this flexibility, you can easily boot from a changed root partition, without the need to recompile the initramfs image. So, you could completely change your root partition (move it inside a md raid with encryption and LVM on top), as long as you specify the correct filesystem LABEL or UUID on the kernel command line for your root device, dracut will find it and boot from it.

Files from the host root filesystem under the /etc, /var, or /run directories should only be copied over to the generated initramfs in "hostonly" mode, as these host directories are meant to be customized by users for each host. Only host files from the /usr directory in the host root filesystem are meant to be included in the generated initramfs in both "hostonly" and "non-hostonly" mode. As an example /etc/fstab and /etc/cryptab files should be only consulted when dracut is run in "hostonly" mode.

The only exception to this rule is the /etc/dracut.conf file and /etc/dracut.conf.d/ directory that is considered both in "hostonly" and "non-hostonly" modes.

Some command line arguments (e.g. --include) can override the default "hostonly"/"non-hostonly" modes.

Generic initrd’s are larger, but should be able to automatically boot any bootable configuration with appropriate boot flags (root device, network configuration information, etc.)

The kernel command line can also be provided by the dhcp server with the root-path option. See NETWORK BOOT.

For a full reference of all kernel command line parameters, see man:dracut.cmdline[7].

To get a quick start for the suitable kernel command line on your system, use the --print-cmdline option:

```
# dracut --print-cmdline

 root=UUID=8b8b6f91-95c7-4da2-831b-171e12179081 rootflags=rw,relatime,discard,data=ordered rootfstype=ext4
```

### Specifying the root Device
This is the only option dracut really needs to boot from your root partition. Because your root partition can live in various environments, there are a lot of formats for the root= option. The most basic one is root=<path to device node>:

```
root=/dev/sda2
```

Because device node names can change, dependent on the drive ordering, you are encouraged to use the filesystem identifier (UUID) or filesystem label (LABEL) to specify your root partition:

```
root=UUID=19e9dda3-5a38-484d-a9b0-fa6b067d0331
```

or

```
root=LABEL=myrootpartitionlabel
```

To see all UUIDs or LABELs on your system, do:

```
# ls -l /dev/disk/by-uuid
```

or

```
# ls -l /dev/disk/by-label
```

If your root partition is on the network see NETWORK BOOT.

### Keyboard Settings
If you have to input passwords for encrypted disk volumes, you might want to set the keyboard layout and specify a display font.

A typical german kernel command line would contain:

```
rd.vconsole.font=eurlatgr rd.vconsole.keymap=de-latin1-nodeadkeys rd.locale.LANG=de_DE.UTF-8
```

Setting these options can override the setting stored on your system, if you use a modern init system, like systemd.

### Blacklisting Kernel Modules
Sometimes it is required to prevent the automatic kernel module loading of a specific kernel module. To do this, just add rd.driver.blacklist=<kernel module name>, with <kernel module name> not containing the .ko suffix, to the kernel command line. For example:

```
rd.driver.blacklist=mptsas rd.driver.blacklist=nouveau
```

The option can be specified multiple times on the kernel command line.

### Speeding up the Boot Process
If you want to speed up the boot process, you can specify as much information for dracut on the kernel command as possible. For example, you can tell dracut, that you root partition is not on a LVM volume or not on a raid partition, or that it lives inside a specific crypto LUKS encrypted volume. By default, dracut searches everywhere. A typical dracut kernel command line for a plain primary or logical partition would contain:

```
rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0
```

This turns off every automatic assembly of LVM, MD raids, DM raids and crypto LUKS.

Of course, you could also omit the dracut modules in the initramfs creation process, but then you would lose the possibility to turn it on on demand.

## INJECTING CUSTOM FILES
To add your own files to the initramfs image, you have several possibilities.

The --include option let you specify a source path and a target path. For example

```
# dracut --include cmdline-preset /etc/cmdline.d/50-mycmdline.conf initramfs-cmdline-pre.img
```

will create an initramfs image, where the file cmdline-preset will be copied inside the initramfs to /etc/cmdline.d/50-mycmdline.conf.

```
# mkdir -p rd.overlay/etc/cmdline.d
# mkdir -p rd.overlay/etc/conf.d
# echo "ip=dhcp" >> rd.overlay/etc/cmdline.d/50-mycmdline.conf
# echo export FOO=testtest >> rd.overlay/etc/conf.d/testvar.conf
# echo export BAR=testtest >> rd.overlay/etc/conf.d/testvar.conf
# tree rd.overlay/
rd.overlay/
`-- etc

    |-- cmdline.d

    |   `-- 50-mycmdline.conf

    `-- conf.d

        `-- testvar.conf
# dracut --include rd.overlay / initramfs-rd.overlay.img
```

This will put the contents of the rd.overlay directory into the root of the initramfs image.

The --install option let you specify several files, which will get installed in the initramfs image at the same location, as they are present on initramfs creation time.

```
# dracut --install 'strace fsck.ext4 ssh' initramfs-dbg.img
```

This will create an initramfs with the strace, fsck.ext4 and ssh executables, together with the libraries needed to start those. The --install option can be specified multiple times.

## NETWORK BOOT
If your root partition is on a network drive, you have to have the network dracut modules installed to create a network aware initramfs image.

If you specify ip=dhcp on the kernel command line, then dracut asks a dhcp server about the ip address for the machine. The dhcp server can also serve an additional root-path, which will set the root device for dracut. With this mechanism, you have static configuration on your client machine and a centralized boot configuration on your TFTP/DHCP server. If you can’t pass a kernel command line, then you can inject /etc/cmdline.d/50-mycmdline.conf, with a method described in INJECTING CUSTOM FILES.

### Reducing the Image Size
To reduce the size of the initramfs, you should create it with by omitting all dracut modules, which you know, you don’t need to boot the machine.

You can also specify the exact dracut and kernel modules to produce a very tiny initramfs image.

For example for a NFS image, you would do:

```
# dracut -m "nfs network base" initramfs-nfs-only.img
```

Then you would boot from this image with your target machine and reduce the size once more by creating it on the target machine with the --host-only option:

```
# dracut -m "nfs network base" --host-only initramfs-nfs-host-only.img
```

This will reduce the size of the initramfs image significantly.

## TROUBLESHOOTING
If the boot process does not succeed, you have several options to debug the situation.

## IDENTIFYING YOUR PROBLEM AREA
1.Remove 'splash' and 'quiet' from the kernel command line

2.Add 'rd.shell' to the kernel command line. This will present a shell should dracut be unable to locate your root device

3.Add 'rd.shell rd.debug log_buf_len=1M' to the kernel command line so that dracut shell commands are printed as they are executed

4.The file /run/initramfs/rdsosreport.txt is generated, which contains all the logs and the output of all significant tools, which are mentioned later.

If you want to save that output, simply mount /boot by hand or insert an USB stick and mount that. Then you can store the output for later inspection.

## INFORMATION TO INCLUDE IN YOUR REPORT

### All bug reports
In all cases, the following should be mentioned and attached to your bug report:

•The exact kernel command-line used. Typically from the bootloader configuration file (e.g. /boot/grub2/grub.cfg) or from /proc/cmdline.

•A copy of your disk partition information from /etc/fstab, which might be obtained booting an old working initramfs or a rescue medium.

•Turn on dracut debugging (see the debugging dracut section), and attach the file /run/initramfs/rdsosreport.txt.

•If you use a dracut configuration file, please include /etc/dracut.conf and all files in /etc/dracut.conf.d/*.conf

### Network root device related problems
This section details information to include when experiencing problems on a system whose root device is located on a network attached volume (e.g. iSCSI, NFS or NBD). As well as the information from All bug reports, include the following information:

•Please include the output of

```
# /sbin/ifup <interfacename>
# ip addr show
```

## DEBUGGING DRACUT

### Configure a serial console
Successfully debugging dracut will require some form of console logging during the system boot. This section documents configuring a serial console connection to record boot messages.

1.First, enable serial console output for both the kernel and the bootloader.

2.Open the file /boot/grub2/grub.cfg for editing. Below the line 'timeout=5', add the following:

```
serial --unit=0 --speed=9600
terminal --timeout=5 serial console
```

3.Also in /boot/grub2/grub.cfg, add the following boot arguments to the 'kernel' line:

```
console=tty0 console=ttyS0,9600
```

4.When finished, the /boot/grub2/grub.cfg file should look similar to the example below.

```
default=0
timeout=5
serial --unit=0 --speed=9600
terminal --timeout=5 serial console
title Fedora (2.6.29.5-191.fc11.x86_64)

  root (hd0,0)

  kernel /vmlinuz-2.6.29.5-191.fc11.x86_64 ro root=/dev/mapper/vg_uc1-lv_root console=tty0 console=ttyS0,9600

  initrd /dracut-2.6.29.5-191.fc11.x86_64.img
```

5.More detailed information on how to configure the kernel for console output can be found at <http://www.faqs.org/docs/Linux-HOWTO/Remote-Serial-Console-HOWTO.html#CONFIGURE-KERNEL>.

6.Redirecting non-interactive output

Note You can redirect all non-interactive output to /dev/kmsg and the kernel

will put it out on the console when it reaches the kernel buffer by doing

```
# exec >/dev/kmsg 2>&1 </dev/console
```

### Using the dracut shell
dracut offers a shell for interactive debugging in the event dracut fails to locate your root filesystem. To enable the shell:

1.Add the boot parameter 'rd.shell' to your bootloader configuration file (e.g. /boot/grub2/grub.cfg)

2.Remove the boot arguments 'splash' and 'quiet' A sample /boot/grub2/grub.cfg bootloader configuration file is listed below.

```
default=0
timeout=5
serial --unit=0 --speed=9600
terminal --timeout=5 serial console
title Fedora (2.6.29.5-191.fc11.x86_64)

  root (hd0,0)

  kernel /vmlinuz-2.6.29.5-191.fc11.x86_64 ro root=/dev/mapper/vg_uc1-lv_root console=tty0 rd.shell

  initrd /dracut-2.6.29.5-191.fc11.x86_64.img
```

3.If system boot fails, you will be dropped into a shell as seen in the example below.

```
No root device found
Dropping to debug shell.
#
```

4.Use this shell prompt to gather the information requested above (see All bug reports).

### Accessing the root volume from the dracut shell
From the dracut debug shell, you can manually perform the task of locating and preparing your root volume for boot. The required steps will depend on how your root volume is configured. Common scenarios include:

•A block device (e.g. /dev/sda7)

•A LVM logical volume (e.g. /dev/VolGroup00/LogVol00)

•An encrypted device (e.g. /dev/mapper/luks-4d5972ea-901c-4584-bd75-1da802417d83)

•A network attached device (e.g. netroot=iscsi:@192.168.0.4::3260::iqn.2009-02.org.example:for.all)

The exact method for locating and preparing will vary. However, to continue with a successful boot, the objective is to locate your root volume and create a symlink /dev/root which points to the file system. For example, the following example demonstrates accessing and booting a root volume that is an encrypted LVM Logical volume.

1.Inspect your partitions using parted

```
# parted /dev/sda -s p
Model: ATA HTS541060G9AT00 (scsi)
Disk /dev/sda: 60.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number  Start   End     Size    Type      File system  Flags
1      32.3kB  10.8GB  107MB   primary   ext4         boot
2      10.8GB  55.6GB  44.7GB  logical                lvm
```

2.You recall that your root volume was a LVM logical volume. Scan and activate any logical volumes.

```
# lvm vgscan
# lvm vgchange -ay
```

3.You should see any logical volumes now using the command blkid:

```
# blkid
/dev/sda1: UUID="3de247f3-5de4-4a44-afc5-1fe179750cf7" TYPE="ext4"
/dev/sda2: UUID="Ek4dQw-cOtq-5MJu-OGRF-xz5k-O2l8-wdDj0I" TYPE="LVM2_member"
/dev/mapper/linux-root: UUID="def0269e-424b-4752-acf3-1077bf96ad2c" TYPE="crypto_LUKS"
/dev/mapper/linux-home: UUID="c69127c1-f153-4ea2-b58e-4cbfa9257c5e" TYPE="ext4"
/dev/mapper/linux-swap: UUID="47b4d329-975c-4c08-b218-f9c9bf3635f1" TYPE="swap"
```

4.From the output above, you recall that your root volume exists on an encrypted block device. Following the guidance disk encryption guidance from the Installation Guide, you unlock your encrypted root volume.

```
# UUID=$(cryptsetup luksUUID /dev/mapper/linux-root)
# cryptsetup luksOpen /dev/mapper/linux-root luks-$UUID
Enter passphrase for /dev/mapper/linux-root:
Key slot 0 unlocked.
```

5.Next, make a symbolic link to the unlocked root volume

```
# ln -s /dev/mapper/luks-$UUID /dev/root
```

6.With the root volume available, you may continue booting the system by exiting the dracut shell

```
# exit
```

### Additional dracut boot parameters
For more debugging options, see man:dracut.cmdline[7].

### Debugging dracut on shutdown
To debug the shutdown sequence on systemd systems, you can rd.break on pre-shutdown or shutdown.

To do this from an already booted system:

```
# mkdir -p /run/initramfs/etc/cmdline.d
# echo "rd.debug rd.break=pre-shutdown rd.break=shutdown" > /run/initramfs/etc/cmdline.d/debug.conf
# touch /run/initramfs/.need_shutdown
```

This will give you a dracut shell after the system pivot’ed back in the initramfs.

## OPTIONS
--kver <kernel version>

Set the kernel version. This enables to specify the kernel version, without specifying the location of the initramfs image. For example:

```
# dracut --kver 3.5.0-0.rc7.git1.2.fc18.x86_64
```

-f, --force

Overwrite existing initramfs file.

<output file> --rebuild

Append the current arguments to those with which the input initramfs image was built. This option helps in incrementally building the initramfs for testing. If optional <output file> is not provided, the input initramfs provided to rebuild will be used as output file.

-a, --add <list of dracut modules>

Add a space-separated list of dracut modules to the default set of modules. If a module appears in both add and omit lists, it will be omitted. This parameter can be specified multiple times.

Note If the list has multiple arguments, then you have to put these in quotes. For

example:

```
# dracut --add "module1 module2"  ...
```

--force-add <list of dracut modules>

A space-separated list of dracut modules appended to the default set of modules when host-only (-H) mode is specified. Unlike --add, --force-add will override omittied (-o) modules; it is thus useful to ensure that a module is added even if it is specified as omitted in configuration files. This parameter can be specified multiple times.

Note If the list has multiple arguments, then you have to put these in quotes. For

example:

```
# dracut --force-add "module1 module2"  ...
```

-o, --omit <list of dracut modules>

Omit a space-separated list of dracut modules. This parameter can be specified multiple times. Warning: Avoid manually omitting dracut modules, as you may inadvertently remove essential ones that dracut can’t detect or warn you about. Using this option is not recommended and is at your own risk.

Note If the list has multiple arguments, then you have to put these in quotes. For

example:

```
# dracut --omit "module1 module2"  ...
```

-m, --modules <list of dracut modules>

Specify a space-separated list of dracut modules to call when building the initramfs. Modules are located in /usr/lib/dracut/modules.d. This parameter can be specified multiple times. This option forces dracut to only include the specified dracut modules. In most cases the "--add" option is what you want to use. This option is not recommended to use (use at your own risk).

Note If the list has multiple arguments, then you have to put these in quotes. For

example:

```
# dracut --modules "module1 module2"  ...
```

-d, --drivers <list of kernel modules>

Specify a space-separated list of kernel modules to exclusively include in the initramfs. The kernel modules have to be specified without the ".ko" suffix. This parameter can be specified multiple times. This option forces dracut to only include the specified kernel modules. In most cases the "--add-drivers" option is what you want to use. This option is not recommended to use (use at your own risk).

Note If the list has multiple arguments, then you have to put these in quotes. For

example:

```
# dracut --drivers "kmodule1 kmodule2"  ...
```

--add-drivers <list of kernel modules>

Specify a space-separated list of kernel modules to add to the initramfs. The kernel modules have to be specified without the ".ko" suffix. This parameter can be specified multiple times.

Note If the list has multiple arguments, then you have to put these in quotes. For

example:

```
# dracut --add-drivers "kmodule1 kmodule2"  ...
```

--force-drivers <list of kernel modules>

See add-drivers above. But in this case it is ensured that the drivers are tried to be loaded early via modprobe.

Note If the list has multiple arguments, then you have to put these in quotes. For

example:

```
# dracut --force-drivers "kmodule1 kmodule2"  ...
```

--omit-drivers <list of kernel modules>

Specify a space-separated list of kernel modules not to add to the initramfs. The kernel modules have to be specified without the ".ko" suffix. This parameter can be specified multiple times.

Note If the list has multiple arguments, then you have to put these in quotes. For

example:

```
# dracut --omit-drivers "kmodule1 kmodule2"  ...
```

--filesystems <list of filesystems>

Specify a space-separated list of kernel filesystem modules to exclusively include in the generic initramfs. This parameter can be specified multiple times.

Note If the list has multiple arguments, then you have to put these in quotes. For

example:

```
# dracut --filesystems "filesystem1 filesystem2"  ...
```

-k, --kmoddir <kernel directory>

Specify the directory, where to look for kernel modules.

--fwdir <dir>[:<dir>...]++

Specify additional directories, where to look for firmwares. This parameter can be specified multiple times.

--libdirs <list of directories>

Specify a space-separated list of directories to look for libraries to include in the generic initramfs. This parameter can be specified multiple times.

Note If the list has multiple arguments, then you have to put these in quotes. For

example:

```
# dracut --libdirs "dir1 dir2"  ...
```

--kernel-cmdline <parameters>

Specify default kernel command line parameters. Despite its name, this command only sets initrd parameters.

--kernel-only

Only install kernel drivers and firmware files.

--no-kernel

Do not install kernel drivers and firmware files.

--early-microcode

Combine early microcode with ramdisk.

--no-early-microcode

Do not combine early microcode with ramdisk.

--print-cmdline

Print part of the kernel command line required to boot for the current disk layout. This option does not return all kernel command line options that dracut might add to the initrd.

--mdadmconf

Include local /etc/mdadm.conf file.

--nomdadmconf

Do not include local /etc/mdadm.conf file.

--lvmconf

Include local /etc/lvm/lvm.conf file.

--nolvmconf

Do not include local /etc/lvm/lvm.conf file.

--fscks <list of fsck tools>

Add a space-separated list of fsck tools, in addition to dracut.conf's specification; the installation is opportunistic (non-existing tools are ignored).

Note If the list has multiple arguments, then you have to put these in quotes. For

example:

```
# dracut --fscks "fsck.foo barfsck"  ...
```

--nofscks

Inhibit installation of any fsck tools.

--strip

Strip binaries in the initramfs (default).

--aggressive-strip

Strip more than just debug symbol and sections, for a smaller initramfs build. The --strip option must also be specified.

--nostrip

Do not strip binaries in the initramfs.

--hardlink

Hardlink files in the initramfs (default).

--nohardlink

Do not hardlink files in the initramfs.

--prefix <dir>

Prefix initramfs files with the specified directory.

--noprefix

Do not prefix initramfs files (default).

-h, --help

Display help text and exit.

--debug

Output debug information of the build process.

-v, --verbose

Increase verbosity level (default is warnings(3)). Could be specified multiple times.

--version

Display version and exit.

-q, --quiet

Decrease verbosity level (default is warnings(3)). Could be specified multiple times.

-c, --conf <dracut configuration file>

Specify configuration file to use. Default: /etc/dracut.conf

--confdir <configuration directory>

Specify configuration directory to use. Default: /etc/dracut.conf.d

--add-confdir <configuration directory>

Add an extra configuration directory to use *.conf files from. If the directory is not existed, will look for subdirectory under confdir. Default: empty

--tmpdir <temporary directory>

Specify temporary directory to use. Default: /var/tmp

-r, --sysroot <sysroot directory>

Specify the sysroot directory to collect files from. This is useful to create the initramfs image from a cross-compiled sysroot directory. For the extra helper variables, see ENVIRONMENT below. Default: empty

--sshkey <sshkey file>

SSH key file used with ssh-client module.

--logfile <logfile>

Logfile to use; overrides any setting from the configuration files. Default: /var/log/dracut.log

-l, --local

Activates the local mode. dracut will use modules from the current working directory instead of the system-wide installed modules in /usr/lib/dracut/modules.d. This is useful when running dracut from a git checkout.

-H, --hostonly

Host-only mode: Install files from the host root filesystem, including from directories that are customized by system administrators and users such as /etc and generate host-specific configuration (default). Resilience to minor hardware changes of the generated initramfs is controlled by hostonly-mode .

Warning If chrooted to another root other than the real root device, use "--fstab" and

provide a valid /etc/fstab.

-N, --no-hostonly

Disable host-only mode.

--hostonly-mode <mode>

Specify the host-only mode to use. <mode> could be one of "sloppy" or "strict". In "sloppy" host-only mode, extra drivers and modules will be installed, so minor hardware change won’t make the image unbootable (e.g. changed keyboard), and the image is still portable among similar hosts. With "strict" mode enabled, anything not necessary for booting the local host in its current state will not be included, and modules may do some extra job to save more space. Minor change of hardware or environment could make the image unbootable. Default: sloppy

--hostonly-cmdline

Allow dracut modules to generate and store host-specific initrd arguments. These arguments will be stored in the etc/cmdline.d directory inside the generated initrd. The kernel cmdline arguments (specified by e.g. bootloader or UKI) take priority over initrd arguments generated by dracut modules. For example the rootfs-block dracut module could store the root= initrd cmdline argument in the etc/cmdline.d directory, which would set the root device if it is not already specified in /proc/cmdline.

--no-hostonly-cmdline

Do not store kernel command line arguments needed in the initramfs. Ensures that dracut modules are not allowed to generate and store host-specific initrd arguments in the etc/cmdline.d directory inside the generated initrd.

--no-hostonly-default-device

Do not generate implicit host devices like root, swap, fstab, etc. Use "--mount" or "--add-device" to explicitly add devices as needed.

--hostonly-i18n

Install only needed keyboard and font files according to the host configuration (default).

--no-hostonly-i18n

Install all keyboard and font files available.

--hostonly-nics <list of nics>

Only enable listed NICs in the initramfs. The list can be empty, so other modules can install only the necessary network drivers.

--persistent-policy <policy>

Use <policy> to address disks and partitions. <policy> can be any directory name found in /dev/disk (e.g. "by-uuid", "by-label"), or "mapper" to use /dev/mapper device names (default).

--fstab

Use /etc/fstab instead of /proc/self/mountinfo.

--add-fstab <filename>

Add entries of <filename> to the initramfs /etc/fstab.

--mount "<device> <mountpoint> <filesystem type> [<filesystem options> [<dump frequency> [<fsck order>]]]"

Mount <device> on <mountpoint> with <filesystem type> in the initramfs. <filesystem options>, <dump options> and <fsck order> can be specified, see fstab manpage for the details. The default <filesystem options> is "defaults". The default <dump frequency> is "0". The default <fsck order> is "2".

--mount "<mountpoint>"

Like above, but <device>, <filesystem type> and <filesystem options> are determined by looking at the current mounts.

--add-device <device>

Bring up <device> in initramfs, <device> should be the device name. This can be useful in host-only mode for resume support when your swap is on LVM or an encrypted partition. [NB --device can be used for compatibility with earlier releases]

-i, --include <SOURCE> <TARGET>

Include the files in the SOURCE directory into the TARGET directory in the final initramfs. If SOURCE is a file, it will be installed to TARGET in the final initramfs. This parameter can be specified multiple times.

-I, --install <file list>

Install the space separated list of files into the initramfs.

Note If the list has multiple arguments, then you have to put these in quotes. For

example:

```
# dracut --install "/bin/foo /sbin/bar"  ...
```

--remove <file/dir list>

Remove a space-separated list of files and directories from the initramfs. These file/dir are shell wildcard patterns (see glob(7)).

--install-optional <file list>

Install the space separated list of files into the initramfs, if they exist.

--gzip

Compress the generated initramfs using gzip.

Warning Make sure your kernel has gzip decompression support compiled in, otherwise you

will not be able to boot. Equivalent to "--compress=gzip -9".

--bzip2

Compress the generated initramfs using bzip2.

Warning Make sure your kernel has bzip2 decompression support compiled in, otherwise you

will not be able to boot. Equivalent to "--compress=bzip2 -9".

--lzma

Compress the generated initramfs using lzma.

Warning Make sure your kernel has lzma decompression support compiled in, otherwise you

will not be able to boot. Equivalent to "--compress=lzma -9 -T0".

--xz

Compress the generated initramfs using xz.

Warning Make sure your kernel has xz decompression support compiled in, otherwise you

will not be able to boot. Equivalent to "--compress=xz --check=crc32 --lzma2=dict=1MiB -T0".

--lzo

Compress the generated initramfs using lzop.

Warning Make sure your kernel has lzo decompression support compiled in, otherwise you

will not be able to boot. Equivalent to "--compress=lzop -9".

--lz4

Compress the generated initramfs using lz4.

Warning Make sure your kernel has lz4 decompression support compiled in, otherwise you

will not be able to boot. Equivalent to "--compress=lz4 -l -9".

--zstd

Compress the generated initramfs using Zstandard.

Warning Make sure your kernel has zstd decompression support compiled in, otherwise you

will not be able to boot. Equivalent to "--compress=zstd -15 -q -T0".

--compress <compressor>

Compress the generated initramfs using the passed compression program. If you pass it just the name of a compression program, it will call that program with known-working arguments. If you pass a quoted string with arguments, it will be called with exactly those arguments. Depending on what you pass, this may result in an initramfs that the kernel cannot decompress. The default value can also be set via the INITRD_COMPRESS environment variable.

--squash-compressor <compressor>

Compress the squashfs image using the passed compressor and compressor specific options for mksquashfs. You can refer to mksquashfs manual for supported compressors and compressor specific options. If squash module is not called when building the initramfs, this option will not take effect.

--no-compress

Do not compress the generated initramfs. This will override any other compression options.

--reproducible

Create reproducible images.

--no-reproducible

Do not create reproducible images.

--list-modules

List all available dracut modules.

-M, --show-modules

Print included module’s name to standard output during build.

--keep

Keep the initramfs temporary directory for debugging purposes.

--printconfig

Print the computed configuration and exit.

--printsize

Print out the module install size.

--profile

Output profile information of the build process.

--ro-mnt

Mount / and /usr read-only by default.

-L, --stdlog <level>

[0-6] Specify logging level (to standard error).

```
          0 - suppress any messages

          1 - only fatal errors

          2 - all errors

          3 - warnings

          4 - info

          5 - debug info (here starts lots of output)

          6 - trace info (and even more)
```

--regenerate-all

Regenerate all initramfs images at the default location with the kernel versions found on the system. Additional parameters are passed through.

-p, --parallel

Try to execute tasks in parallel. Currently only supported with --regenerate-all (build initramfs images for all kernel versions simultaneously).

--noimageifnotneeded

Do not create an image in host-only mode, if no kernel driver is needed and no /etc/cmdline/*.conf will be generated into the initramfs.

--loginstall <directory>

Log all files installed from the host to <directory>.

--uefi

Instead of creating an initramfs image, dracut will create an UEFI executable, which can be executed by an UEFI BIOS. The default output filename is <EFI>/EFI/Linux/linux-$kernel$-<MACHINE_ID>-<BUILD_ID>.efi. <EFI> might be /efi, /boot or /boot/efi depending on where the ESP partition is mounted. The <BUILD_ID> is taken from BUILD_ID in /usr/lib/os-release or if it exists /etc/os-release and is left out, if BUILD_ID is non-existent or empty.

--ukify

Enables using ukify to create UKI (default).

--no-uefi

Disables UEFI mode.

--no-ukify

Disables using ukify to create UKI even if ukify is installed.

--no-machineid

Affects the default output filename of --uefi and will discard the <MACHINE_ID> part.

--uefi-stub <file>

Specifies the UEFI stub loader, which will load the attached kernel, initramfs and kernel command line and boots the kernel. The default is $prefix/lib/systemd/boot/efi/linux<EFI-MACHINE-TYPE-NAME>.efi.stub.

--uefi-splash-image <file>

Specifies the UEFI stub loader’s splash image. Requires bitmap (.bmp) image format.

--kernel-image <file>

Specifies the kernel image, which to include in the UEFI executable. The default is /lib/modules/<KERNEL-VERSION>/vmlinuz or /boot/vmlinuz-<KERNEL-VERSION>.

--sbat <parameters>

Specifies the SBAT parameters, which to include in the UEFI executable. By default the default SBAT string added is "sbat,1,SBAT Version,sbat,1, ." <https://github.com/rhboot/shim/blob/main/SBAT.md" " >

--enhanced-cpio

Attempt to use the dracut-cpio binary, which optimizes archive creation for copy-on-write filesystems by using the man:copy_file_range[2] syscall via Rust’s io::copy(). When specified, initramfs archives are also padded to ensure optimal data alignment for extent sharing. To retain reflink data deduplication benefits, this should be used alongside the --no-compress and --nostrip parameters, with initramfs source files, --tmpdir staging area and destination all on the same copy-on-write capable filesystem.

## ENVIRONMENT
Environment variables override settings in configuration files, and command-line options override both.

INITRD_COMPRESS

sets the default compression program. See --compress.

DRACUT_LDCONFIG

sets the ldconfig program path and options. Optional. Used for --sysroot. Default: ldconfig

PKG_CONFIG

sets the pkg-config program path and options. Optional. Most useful together with --sysroot. Default: pkg-config

DRACUT_TESTBIN

sets the initially tested binary for detecting library paths. Optional. Used for --sysroot. In the cross-compiled sysroot, the default value (/bin/sh) is unusable, as it is an absolute symlink and points outside the sysroot directory. Default: /bin/sh

DRACUT_INSTALL

overrides path and options for executing dracut-install internally. Optional. Can be used to debug dracut-install while running the main dracut script. Default: dracut-install

Example: DRACUT_INSTALL="valgrind dracut-install"

DRACUT_COMPRESS_BZIP2, DRACUT_COMPRESS_LBZIP2, DRACUT_COMPRESS_LZMA, DRACUT_COMPRESS_XZ, DRACUT_COMPRESS_GZIP, DRACUT_COMPRESS_PIGZ, DRACUT_COMPRESS_LZOP, DRACUT_COMPRESS_ZSTD, DRACUT_COMPRESS_LZ4, DRACUT_COMPRESS_CAT

overrides for compression utilities to support using them from non-standard paths. Default values are the default compression utility names to be found in PATH.

DRACUT_ARCH

overrides the value of uname -m. Used for --sysroot. Default: empty (the value of uname -m on the host system)

DRACUT_EXTRA_ARGS

A string of additional dracut command-line arguments. The value is word-split and prepended to the argument list before option parsing, so explicit flags supplied directly on the command line will override the values set here. Arguments that contain spaces must be shell-quoted within the value:

```
DRACUT_EXTRA_ARGS='--add "module1 module2"' dracut
```

SYSTEMD_VERSION

overrides systemd version. Used for --sysroot.

SYSTEMCTL

overrides the systemctl binary. Used for --sysroot.

NM_VERSION

overrides the NetworkManager version. Used for --sysroot.

DRACUT_INSTALL_PATH

overrides PATH environment for dracut-install to look for binaries relative to --sysroot. In a cross-compiled environment (e.g. Yocto), PATH points to natively built binaries that are not in the host’s /bin, /usr/bin, etc. dracut-install still needs plain /bin and /usr/bin that are relative to the cross-compiled sysroot. Default: PATH

DRACUT_INSTALL_LOG_TARGET

overrides DRACUT_LOG_TARGET for dracut-install. It allows running dracut-install* to run with different log target that dracut** runs with. Default: DRACUT_LOG_TARGET

DRACUT_INSTALL_LOG_LEVEL

overrides DRACUT_LOG_LEVEL for dracut-install. It allows running dracut-install* to run with different log level that dracut** runs with. Default: DRACUT_LOG_LEVEL

## FILES
/var/log/dracut.log

logfile of initramfs image creation

/tmp/dracut.log

logfile of initramfs image creation, if /var/log/dracut.log is not writable

/etc/dracut.conf

see dracut.conf5

/etc/dracut.conf.d/*.conf

see dracut.conf5

/usr/lib/dracut/dracut.conf.d/*.conf

see dracut.conf5

### Configuration in the initramfs
/etc/conf.d/

Any files found in /etc/conf.d/ will be sourced in the initramfs to set initial values. Command line options will override these values set in the configuration files.

/etc/cmdline

Can contain additional command line options. Deprecated, better use /etc/cmdline.d/*.conf.

/etc/cmdline.d/*.conf

Can contain additional command line options. It is recommended to use an ordering schema for these conf files in the range of 50-59. Dracut generated conf files are placed in the 10-49 and 60-99 ordering range.

## AVAILABILITY
The dracut command is part of the dracut package and is available from <https://github.com/dracut-ng/dracut-ng> "" <"https://github.com/dracut-ng/dracut-ng">

## AUTHORS
Harald Hoyer

Victor Lowther

Amadeusz Żołnowski

Hannes Reinecke

Daniel Molkentin

Will Woods

Philippe Seewer

Warren Togami

## SEE ALSO
man:dracut.cmdline[7] man:dracut.conf[5] man:lsinitrd[1]


dracut-cmdline.service

title: dracut-cmdline.service(8)

text:
# dracut-cmdline.service(8)

## NAME
dracut-cmdline.service - runs the dracut hooks to parse the kernel command line

## SYNOPSIS
dracut-cmdline.service

## DESCRIPTION
This service runs all the dracut hooks to parse the kernel command line in the initramfs.

## AUTHORS
Harald Hoyer

## SEE ALSO
dracut.bootup(7) dracut(8)

branch: sisyphus


dracut-initqueue.service

title: dracut-initqueue.service(8)

text:
# dracut-initqueue.service(8)

## NAME
dracut-initqueue.service - runs the dracut main loop to find the real root

## SYNOPSIS
dracut-initqueue.service

## DESCRIPTION
This service runs all the main loop of dracut in the initramfs to find the real root.

## AUTHORS
Harald Hoyer

## SEE ALSO
dracut.bootup(7) dracut(8)


dracut-mount.service

title: dracut-mount.service(8)

text:
# dracut-mount.service(8)

## NAME
dracut-mount.service - runs the dracut hooks after /sysroot is mounted

## SYNOPSIS
dracut-mount.service

## DESCRIPTION
This service runs all dracut hooks after the real root is mounted on /sysroot.

## AUTHORS
Harald Hoyer

## SEE ALSO
dracut.bootup(7) dracut(8)


dracut-pre-mount.service

title: dracut-pre-mount.service(8)

text:
# dracut-pre-mount.service(8)

## NAME
dracut-pre-mount.service - runs the dracut hooks before /sysroot is mounted

## SYNOPSIS
dracut-pre-mount.service

## DESCRIPTION
This service runs all dracut hooks before the real root is mounted on /sysroot.

## AUTHORS
Harald Hoyer

## SEE ALSO
dracut.bootup(7) dracut(8)


dracut-pre-pivot.service

title: dracut-pre-pivot.service(8)

text:
# dracut-pre-pivot.service(8)

## NAME
dracut-pre-pivot.service - runs the dracut hooks before switching root

## SYNOPSIS
dracut-pre-pivot.service

## DESCRIPTION
This service runs all dracut hooks before the system switched to the real root.

## AUTHORS
Harald Hoyer

## SEE ALSO
dracut.bootup(7) dracut(8)


dracut-pre-trigger.service

title: dracut-pre-trigger.service(8)

text:
# dracut-pre-trigger.service(8)

## NAME
dracut-pre-trigger.service - runs the dracut hooks before udevd is triggered

## SYNOPSIS
dracut-pre-trigger.service

## DESCRIPTION
This service runs all dracut hooks before udevd is triggered in the initramfs.

## AUTHORS
Harald Hoyer

## SEE ALSO
dracut.bootup(7) dracut(8)


dracut-pre-udev.service

title: dracut-pre-udev.service(8)

text:
# dracut-pre-udev.service(8)

## NAME
dracut-pre-udev.service - runs the dracut hooks before udevd is started

## SYNOPSIS
dracut-pre-udev.service

## DESCRIPTION
This service runs all dracut hooks before udevd is started in the initramfs.

## AUTHORS
Harald Hoyer

## SEE ALSO
dracut.bootup(7) dracut(8)


dracut-shutdown.service

title: dracut-shutdown.service(8)

summary: unpack the initramfs to /run/initramfs

text:
# dracut-shutdown.service(8)

## NAME
dracut-shutdown.service - unpack the initramfs to /run/initramfs

## SYNOPSIS
dracut-shutdown.service

## DESCRIPTION
This service unpacks the initramfs image to /run/initramfs. systemd pivots into /run/initramfs at shutdown, so the root filesystem can be safely unmounted.

The following steps are executed during a shutdown:

•The system starts to shut down

•``$prefix/lib/systemd/system/sysinit.target.wants/dracut-shutdown.service`` gets its ``ExecStop`` target triggered.

•``dracut-shutdown.service`` executes ``/usr/lib/dracut/dracut-initramfs-restore`` which unpacks the initramfs to ``/run/initramfs``

•systemd kills all processes

•systemd tries to unmount everything and mounts the remaining read-only

•systemd checks if there is a ``/run/initramfs/shutdown`` executable

•if yes, it does a pivot_root to ``/run/initramfs`` and executes ``./shutdown``. The old root is then mounted on ``/oldroot``. ``/usr/lib/dracut/modules.d/[0-9][0-9]shutdown/shutdown.sh`` is the shutdown executable.

•shutdown will try to unmount every ``/oldroot`` mount and calls the various shutdown hooks from the dracut modules

This ensures, that all devices are disassembled and unmounted cleanly.

To debug the shutdown process, you can get a shell in the shutdown procedure by injecting "rd.break=pre-shutdown rd.shell" or "rd.break=shutdown rd.shell".

```
# mkdir -p /run/initramfs/etc/cmdline.d
# echo "rd.break=pre-shutdown rd.shell" > /run/initramfs/etc/cmdline.d/50-debug.conf
# touch /run/initramfs/.need_shutdown
```

In case the unpack of the initramfs fails, dracut-shutdown-onfailure.service executes to make sure switch root doesn’t happen, since it would result in switching to an incomplete initramfs.

## AUTHORS
Harald Hoyer

## SEE ALSO
dracut(8)


dracut-catimages

package: dracut-tools

title: dracut-catimages(8)

text:
# dracut-catimages(8)

## NAME
dracut-catimages - creates initial ramdisk image by concatenating images

## SYNOPSIS
dracut-catimages [OPTION...] <initramfs base image> [<image>...]

## DESCRIPTION
dracut-catimages creates an initial ramdisk image by concatenating several images from the command line and /var/lib/dracut/images/*.img

## OPTIONS
-f, --force

overwrite existing initramfs file.

-i, --imagedir

Directory with additional images to add (default: /var/lib/dracut/images/)

-o, --overlaydir

Overlay directory, which contains additional files that will be used to create an additional image

--nooverlay

Do not use the overlay directory

--noimagedir

Do not use the additional image directory

-h, --help

display help text and exit.

--debug

output debug information of the build process

-v, --verbose

verbose output during the build process

## FILES
/var/lib/dracut/images/*.img

images to work with

## AUTHORS
Harald Hoyer

## AVAILABILITY
The dracut-catimages command is part of the dracut package and is available from <https://github.com/dracut-ng/dracut-ng> "" <"https://github.com/dracut-ng/dracut-ng">

## SEE ALSO
man:dracut[8]


package: drbd-utils

title: drbd-8.4(8)

summary: The start and stop script for DRBD

text:
# drbd-8.4(8)

## NAME
drbd - The start and stop script for DRBD

## SYNOPSIS
/etc/init.d/drbd [resource] {{start} | {stop} | {status} | {reload} | {restart} | {force-reload}}

## INTRODUCTION
The /etc/init.d/drbd script is used to start and stop drbd on a system V style init system.

In order to use /etc/init.d/drbd you must define a resource, a host, and any other configuration options in the drbd configuration file. See /etc/drbd.conf for details. If resource is omitted, then all of the resources listed in the config file are configured.

This script might ask you “Do you want to abort waiting for other server and make this one primary?”

Only answer this question with “yes” if you are sure that it is impossible to repair the other node.

## VERSION
This document was revised for version 8.4.11 of the DRBD distribution.

## AUTHOR
Written by Philipp Reisner <philipp.reisner@linbit.com> and Lars Ellenberg <lars.ellenberg@linbit.com>.

## REPORTING BUGS
Report bugs to <drbd-user@lists.linbit.com>.

## COPYRIGHT
Copyright 2001-2008 LINBIT Information Technologies, Philipp Reisner, Lars Ellenberg. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

## SEE ALSO
drbd.conf(5), drbdsetup(8)drbdadm(8)DRBD Homepage[1]

## NOTES
1.

DRBD Homepage

http://www.drbd.org/


title: drbd-9.0(8)

summary: The start and stop script for DRBD

text:
# drbd-9.0(8)

## NAME
drbd - The start and stop script for DRBD

## SYNOPSIS
/etc/init.d/drbd {start | stop | status | reload | restart | force-reload}

## INTRODUCTION
The /etc/init.d/drbd script is used to start and stop drbd on a system V style init system.

When using a cluster resource manger such as Pacemaker, DRBD should usually not be started by the init system, but should typically be exclusively controlled by the cluster manager. You should not use, and disable, the init script in this case. chmod -x /etc/init.d/drbd has proven most effective for this.

In order to use /etc/init.d/drbd, define a drbd configuration. See drbd.conf(5) for details.

## VERSION
This document was revised for version 9.0.0 of the DRBD distribution.

## AUTHOR
Written by Philipp Reisner <philipp.reisner@linbit.com> and Lars Ellenberg <lars.ellenberg@linbit.com>.

## REPORTING BUGS
Report bugs to <drbd-user@lists.linbit.com>.

## COPYRIGHT
Copyright 2001-2014 LINBIT Information Technologies, Philipp Reisner, Lars Ellenberg. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

## SEE ALSO
drbd.conf(5), drbdsetup(8), drbdadm(8), DRBD Homepage[1]

## NOTES
1.

DRBD Homepage

http://www.drbd.org/


title: drbdadm-8.4(8)

summary: Administration tool for DRBD

text:
# drbdadm-8.4(8)

## NAME
drbdadm - Administration tool for DRBD

## SYNOPSIS
drbdadm [-d] [-c {file}] [-t {file}] [-s {cmd}] [-m {cmd}] [-S] [-h {host}] [-- {backend-options}] {command} [{all} | {resource[/volume>]...}]

## DESCRIPTION
Drbdadm is the high level tool of the DRBD program suite. Drbdadm is to drbdsetup and drbdmeta what ifup/ifdown is to ifconfig. Drbdadm reads its configuration file and performs the specified commands by calling the drbdsetup and/or the drbdmeta program.

Drbdadm can operate on whole resources or on individual volumes in a resource. The sub commands: attach, detach, primary, secondary, invalidate, invalidate-remote, outdate, resize, verify, pause-sync, resume-sync, role, csytate, dstate, create-md, show-gi, get-gi, dump-md, wipe-md work on whole resources and on individual volumes.

Resource level only commands are: connect, disconnect, up, down, wait-connect and dump.

## OPTIONS
-d, --dry-run

Just prints the calls of drbdsetup to stdout, but does not run the commands.

-c, --config-file file

Specifies the configuration file drbdadm will use. If this parameter is not specified, drbdadm will look for /etc/drbd-84.conf, /etc/drbd-83.conf, /etc/drbd-08.conf and /etc/drbd.conf.

-t, --config-to-test file

Specifies an additional configuration file drbdadm to check. This option is only allowed with the dump and the sh-nop commands.

-s, --drbdsetup file

Specifies the full path to the drbdsetup program. If this option is omitted, drbdadm will look for it beneath itself first, and then in the PATH.

-m, --drbdmeta file

Specifies the full path to the drbdmeta program. If this option is omitted, drbdadm will look for it beneath itself first, and then in the PATH.

-S, --stacked

Specifies that this command should be performed on a stacked resource.

-P, --peer

Specifies to which peer node to connect. Only necessary if there are more than two host sections in the resource you are working on.

-- backend-options

All options following the doubly hyphen are considered backend-options. These are passed through to the backend command. I.e. to drbdsetup, drbdmeta or drbd-proxy-ctl.

## COMMANDS
attach

Attaches a local backing block device to the DRBD resource's device.

detach

Removes the backing storage device from a DRBD resource's device.

connect

Sets up the network configuration of the resource's device. If the peer device is already configured, the two DRBD devices will connect. If there are more than two host sections in the resource you need to use the --peer option to select the peer you want to connect to.

disconnect

Removes the network configuration from the resource. The device will then go into StandAlone state.

syncer

Loads the resynchronization parameters into the device.

up

Is a shortcut for attach and connect.

down

Is a shortcut for disconnect and detach.

primary

Promote the resource's device into primary role. You need to do this before any access to the device, such as creating or mounting a file system.

secondary

Brings the device back into secondary role. This is needed since in a connected DRBD device pair, only one of the two peers may have primary role (except if allow-two-primaries is explicitly set in the configuration file).

invalidate

Forces DRBD to consider the data on the local backing storage device as out-of-sync. Therefore DRBD will copy each and every block from its peer, to bring the local storage device back in sync. To avoid races, you need an established replication link, or be disconnected Secondary.

invalidate-remote

This command is similar to the invalidate command, however, the peer's backing storage is invalidated and hence rewritten with the data of the local node. To avoid races, you need an established replication link, or be disconnected Primary.

resize

Causes DRBD to re-examine all sizing constraints, and resize the resource's device accordingly. For example, if you increased the size of your backing storage devices (on both nodes, of course), then DRBD will adopt the new size after you called this command on one of your nodes. Since new storage space must be synchronised this command only works if there is at least one primary node present.

Note that all of the following options are backend-options (i.e., separated via "--").

The --size option can be used to online shrink the usable size of a drbd device. It's the users responsibility to make sure that a file system on the device is not truncated by that operation. Example:

```
# drbdadm -- --size=10G resize r0
```

The --assume-peer-has-space allows you to resize a device which is currently not connected to the peer. Use with care, since if you do not resize the peer's disk as well, further connect attempts of the two will fail.

The --assume-clean allows you to resize an existing device and avoid syncing the new space. This is useful when adding addtional blank storage to your device. Example:

```
# drbdadm -- --assume-clean resize r0
```

The options --al-stripes and --al-stripe-size-kB may be used to change the layout of the activity log online. In case of internal meta data this may invovle shrinking the user visible size at the same time (unsing the --size) or increasing the avalable space on the backing devices.

check-resize

Calls drbdmeta to eventually move internal meta data. If the backing device was resized, while DRBD was not running, meta data has to be moved to the end of the device, so that the next attach command can succeed.

create-md

Initializes the meta data storage. This needs to be done before a DRBD resource can be taken online for the first time. In case of issues with that command have a look at drbdmeta(8)

get-gi

Shows a short textual representation of the data generation identifiers.

show-gi

Prints a textual representation of the data generation identifiers including explanatory information.

dump-md

Dumps the whole contents of the meta data storage, including the stored bit-map and activity-log, in a textual representation.

outdate

Sets the outdated flag in the meta data.

adjust

Synchronizes the configuration of the device with your configuration file. You should always examine the output of the dry-run mode before actually executing this command.

wait-connect

Waits until the device is connected to its peer device.

role

Shows the current roles of the devices (local/peer). E.g. Primary/Secondary

state

Deprecated alias for "role", see above.

cstate

Shows the current connection state of the devices.

dump

Just parse the configuration file and dump it to stdout. May be used to check the configuration file for syntactic correctness.

outdate

Used to mark the node's data as outdated. Usually used by the peer's fence-peer handler.

verify

Starts online verify. During online verify, data on both nodes is compared for equality. See /proc/drbd for online verify progress. If out-of-sync blocks are found, they are not resynchronized automatically. To do that, disconnect and connect the resource when verification has completed.

See also the notes on data integrity on the drbd.conf manpage.

pause-sync

Temporarily suspend an ongoing resynchronization by setting the local pause flag. Resync only progresses if neither the local nor the remote pause flag is set. It might be desirable to postpone DRBD's resynchronization until after any resynchronization of the backing storage's RAID setup.

resume-sync

Unset the local sync pause flag.

new-current-uuid

Generates a new currend UUID and rotates all other UUID values.

This can be used to shorten the initial resync of a cluster. See the drbdsetup manpage for a more details.

dstate

Show the current state of the backing storage devices. (local/peer)

hidden-commands

Shows all commands undocumented on purpose.

## VERSION
This document was revised for version 8.4.0 of the DRBD distribution.

## AUTHOR
Written by Philipp Reisner <philipp.reisner@linbit.com> and Lars Ellenberg <lars.ellenberg@linbit.com>

## REPORTING BUGS
Report bugs to <drbd-user@lists.linbit.com>.

## COPYRIGHT
Copyright 2001-2011 LINBIT Information Technologies, Philipp Reisner, Lars Ellenberg. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

## SEE ALSO
drbd.conf(5), drbd(8), drbdsetup(8), drbdmeta(8) and the DRBD project web site[1]

## NOTES
1.

DRBD project web site

http://www.drbd.org/


title: drbdadm-9.0(8)

summary: Utility for DRBD administration

text:
# drbdadm-9.0(8)

## NAME
drbdadm - Utility for DRBD administration

## SYNOPSIS
drbdadm [options...] [-- [backend-options...]] {command} {context...}

## DESCRIPTION
The drbdadm utility is used for managing DRBD based on its configuration files, see drbd.conf(5). It translates high-level commands into one or more lower-level commands for the drbdsetup and drbdmeta utilities, which control the kernel module and manipulate the on-disk metadata.

Depending on the command, the drbdadm utility operates on one or more resources, devices, connections, or peer devices. The following command contexts are defined:

resource

A resource specified by name, or the keyword all for all defined resources.

device

A device, specified by minor number (minor-minornumber, e.g. minor-0) or by resource and volume number (resource/volume). If only a resource is specified, the command iterates over all devices of that resource.

connection

A connection, specified by resource and connection name (resource:connection-name). If only a resource is specified, the command iterates over all connections of that resource.

peer_device

A peer device, specified by resource, connection name, and volume number (resource:connection-name/volume). If only a resource, device, or connection is specified, the command iterates over all peer devices of that resource, device, or connection.

All options following a double-dash are passed through to the lower-level utilities as specified. In addition, drbdadm understands most of the options of drbdsetup, and will pass them through even without the double-dash.

## OPTIONS
-d, --dry-run

Show which commands drbdadm would execute instead of actually executing them (for example, drbdadm -d up resource). This can be a useful way to learn how drbdsetup and drbdmeta are used.

-c, --config-file file

Use an alternative configuration file. By default, drbdadm will use the the first of the following files that exists: /etc/drbd-90.conf, /etc/drbd-84.conf, /etc/drbd-83.conf, /etc/drbd-82.conf, /etc/drbd-08.conf, /etc/drbd.conf.

-t, --config-to-test file

Check an additional configuration file. This option is only allowed with the dump and the sh-nop commands.

-s, --drbdsetup file

Specifies the full path to the drbdsetup program. If this option is omitted, drbdadm will look for it beneath itself first, and then in the PATH.

-m, --drbdmeta file

Specifies the full path to the drbdmeta program. If this option is omitted, drbdadm will look for it beneath itself first, and then in the PATH.

-S, --stacked

Perform the command on a stacked resource.

## COMMANDS
adjust {resource}

Adjust the configuration of the kernel module so that it matches the configuration files. The result should be the same as when stopping and restarting all resources (drbdadm down all followed by drbdadm up all), but without the interruptions.

Note that the adjust command can misinterpret the configuration change in some cases. To be safe, check what the command would do (with the --dry-run option) before running the actual command.

adjust-with-progress {resource}

The same as adjust, but with some more information about the command's progress.

apply-al {device}

Apply the activity log of the specified device. See drbdmeta(8) for details.

repair-md {device}

Check and repair metadata of the specified device. See drbdmeta(8) for details.

attach {device}

Attach a lower-level device to an existing replicated device. See drbdsetup(8) for details.

check-resize {device}

Call drbdmeta to eventually move internal meta data. If the backing device was resized, while DRBD was not running, meta data has to be moved to the end of the device, so that the next attach command can succeed.

connect {connection}

Activate an exisiting connection to a peer. The connection needs to be created first with the new-peer command, and have at least one path created with the new-path command. See drbdsetup(8) for details.

create-md {device}

Initialize the metadata of a device. This is necessary before a device can be attached; see drbdmeta(8) for details.

cstate {connection}

Show the current state of a connection. See drbdsetup(8) for details.

detach {device}

Detach the lower-level device of a replicated device. See drbdsetup(8) for details.

disconnect {connection}

Remove a connection to a peer host. See drbdsetup(8) for details.

disk-options {device}

Change the disk options of an attached lower-level device. See drbdsetup(8) for details.

down {resource}

Take a resource down by removing all volumes, connections, and the resource itself. See drbdsetup(8) for details.

dstate {device}

Show the current disk state of a lower-level device. See drbdsetup(8) for details.

dump {resource}

Parse the configuration file and dump it to stdout. This will fail if the configuration file is syntactically incorrect.

dump-md {device}

Dump the metadata of a device in text form, including the bitmap and activity log. See drbdmeta(8) for details.

get-gi {peer_device}

Show the data generation identifiers for a device on a particular connection. Uses drbdsetup for attached devices and drbdmeta for unattached devices. See drbdsetup(8) for details.

hidden-commands

Shows all commands which are not explicitly documented.

invalidate {peer_device}

Replace the local data of a device with that of a peer. See drbdsetup(8) for details.

invalidate-remote {peer_device}

Replace a peer device's data of a resource with the local data. See drbdsetup(8) for details.

net-options {connection}

Change the network options of an existing connection. See drbdsetup(8) for details.

new-current-uuid {device}

Generate a new currend UUID. See drbdsetup(8) for details.

outdate {device}

Mark the data on a lower-level device as outdated. See drbdsetup(8) for details.

pause-sync {peer_device}

Stop resynchronizing between a local and a peer device by setting the local pause flag. See drbdsetup(8) for details.

primary {resource}

Change the role of a node in a resource to primary. See drbdsetup(8) for details.

resize {device}

Resize the lower-level devices of a replicated device on all nodes. This combines the check-resize and resize lower-level commands; see drbdsetup(8) for details.

resource-options {resource}

Change the resource options of an existing resource. See drbdsetup(8) for details.

resume-sync {peer_device}

Allow resynchronization to resume by clearing the local sync pause flag. See drbdsetup(8) for details.

role {[resource] | [connection]}

Show the current role of a resource or the role of a resource on a peer.

secondary {resource}

Change the role of a node in a resource to secondary. This command fails if the replicated device is in use.

show-gi {peer_device}

Show the data generation identifiers for a device on a particular connection. In addition, explain the output. See drbdsetup(8) for details.

state {resource}

This is an alias for drbdsetup role. Deprecated.

up {resource}

Bring up a resource by applying the activity log of all volumes, creating the resource, creating the replicated devices, attaching the lower-level devices, and connecting to all peers. See the apply-al drbdmeta command and the new-resource, new-device, new-minor, attach, and connect drbdsetup commands.

verify {peer_device}

Start online verification, change which part of the device will be verified, or stop online verification. See drbdsetup(8) for details.

wait-connect {[device] | [connection] | [resource]}

Wait until a device on a peer, all devices over a connection, or all devices on all peers are visible. See drbdsetup(8) for details.

wait-sync {[device] | [connection] | [resource]}

Wait until a device is connected and has finished eventual resync operation. Also available on connection and resource level. See drbdsetup(8) for details.

wipe-md {device}

Wipe out the DRBD metadata of a device. See drbdmeta(8) for details.

forget-peer {connection}

Completely remove any reference to an unconnected peer from meta-data. See drbdmeta(8) for details.

## VERSION
This document was revised for version 9.0.0 of the DRBD distribution.

## AUTHOR
Written by Philipp Reisner <philipp.reisner@linbit.com> and Lars Ellenberg <lars.ellenberg@linbit.com>

## REPORTING BUGS
Report bugs to <drbd-user@lists.linbit.com>.

## COPYRIGHT
Copyright 2001-2018 LINBIT Information Technologies, Philipp Reisner, Lars Ellenberg. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

## SEE ALSO
drbd.conf(5), drbd(8), drbdsetup(8), drbdmeta(8) and the DRBD project web site[1]

## NOTES
1.

DRBD project web site

http://www.drbd.org/


title: drbdmeta-8.4(8)

summary: DRBD\*(Aqs meta data management tool

text:
# drbdmeta-8.4(8)

## NAME
drbdmeta - DRBD's meta data management tool

## SYNOPSIS
drbdmeta [--force] [--ignore-sanity-checks] {device} {v06 minor | v07 meta_dev index | v08 meta_dev index} {command} [cmd args...]

## DESCRIPTION
Drbdmeta is used to create, display and modify the contents of DRBD's meta data storage. Usually you do not want to use this command directly, but start it via the frontend drbdadm(8).

This command only works if the DRBD resource is currently down, or at least detached from its backing storage. The first parameter is the device node associated to the resource. With the second parameter you can select the version of the meta data. Currently all major DRBD releases (0.6, 0.7 and 8) are supported.

## OPTIONS
--force

All questions that get asked by drbdmeta are treated as if the user answered 'yes'.

--ignore-sanity-checks

Some sanity checks cause drbdmeta to terminate. E.g. if a file system image would get destroyed by creating the meta data. By using that option you can force drbdmeta to ignore these checks.

## COMMANDS
create-md --peer-max-bio-size val --al-stripes val --al-stripe-size-kB val

Create-md initializes the meta data storage. This needs to be done before a DRBD resource can be taken online for the first time. In case there is already a meta data signature of an older format in place, drbdmeta will ask you if it should convert the older format to the selected format.

If you will use the resource before it is connected to its peer for the first time DRBD may perform better if you use the --peer-max-bio-size option. For DRBD versions of the peer use up to these values: <8.3.7 -> 4k, 8.3.8 -> 32k, 8.3.9 -> 128k, 8.4.0 -> 1M.

If you want to use more than 6433 activity log extents, or live on top of a spriped RAID, you may specify the number of stripes (--al-stripes, default 1), and the stripe size (--al-stripe-size-kB, default 32). To just use a larger linear on-disk ring-buffer, leave the number of stripes at 1, and increase the size only:

drbdmeta 0 v08 /dev/vg23/lv42 internal create-md --al-stripe-size 1M

To avoid a single "spindle" from becoming a bottleneck, increase the number of stripes, to achieve an interleaved layout of the on-disk activity-log transactions. What you give as "stripe-size" should be what is a.k.a. "chunk size" or "granularity" or "strip unit": the minimum skip to the next "spindle".

drbdmeta 0 v08 /dev/vg23/lv42 internal create-md --al-stripes 7 --al-stripe-size 64k

get-gi

Get-gi shows a short textual representation of the data generation identifier. In version 0.6 and 0.7 these are generation counters, while in version 8 it is a set of UUIDs.

show-gi

Show-gi prints a textual representation of the data generation identifiers including explanatory information.

dump-md

Dumps the whole contents of the meta data storage including the stored bit-map and activity-log in a textual representation.

outdate

Sets the outdated flag in the meta data. This is used by the peer node when it wants to become primary, but cannot communicate with the DRBD stack on this host.

dstate

Prints the state of the data on the backing storage. The output is always followed by '/DUnknown' since drbdmeta only looks at the local meta data.

check-resize

Examines the device size of a backing device, and it's last known device size, recorded in a file /var/lib/drbd/drbd-minor-??.lkbd. In case the size of the backing device changed, and the meta data can be found at the old position, it moves the meta data to the right position at the end of the block device.

## EXPERTS COMMANDS
Drbdmeta allows you to modify the meta data as well. This is intentionally omitted for the command's usage output, since you should only use it if you really know what you are doing. By setting the generation identifiers to wrong values, you risk to overwrite your up-to-data data with an older version of your data.

set-gi gi

Set-gi allows you to set the generation identifier. Gi needs to be a generation counter for the 0.6 and 0.7 format, and a UUID set for 8.x. Specify it in the same way as get-gi shows it.

restore-md dump_file

Reads the dump_file and writes it to the meta data.

## VERSION
This document was revised for version 8.3.2 of the DRBD distribution.

## AUTHOR
Written by Philipp Reisner <philipp.reisner@linbit.com> and Lars Ellenberg <lars.ellenberg@linbit.com>.

## REPORTING BUGS
Report bugs to <drbd-user@lists.linbit.com>.

## COPYRIGHT
Copyright 2001-2008 LINBIT Information Technologies, Philipp Reisner, Lars Ellenberg. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

## SEE ALSO
drbdadm(8)


title: drbdmeta-9.0(8)

summary: Manipulate the DRBD on\-disk metadata

text:
# drbdmeta-9.0(8)

## NAME
drbdmeta - Manipulate the DRBD on-disk metadata

## SYNOPSIS
drbdmeta [--force] [--ignore-sanity-checks] {device} {v06 minor | v07 meta_dev index | v08 meta_dev index | v09 meta_dev index} {command} [cmd args...]

## DESCRIPTION
The drbdmeta utility is used for creating, displaying, and modifying DRBD's on-disk metadata. Users usually interact with the drbdadm utility, which provides a more high-level interface to DRBD than drbdmeta. (See drbdadm's --dry-run option to see how drbdadm uses drbdmeta.)

This utility can only be used on devices which are not currently in use by the kernel.

The first argument (device) specifies the drbd device associated with a volume, or “-” if no device is associated with that volume. If the drbd device is specified, the drbdmeta utility makes sure that the drbd device does not currently have a volume attached to prevent meta-data of an active volume from being destroyed.

The second argument specifies the metadata version to use (v06, v07, v08, v09). In most metadata versions, the third argument (meta_dev) specifies the device which contains the metadata; this argument can be the same as device. The fourth argument (index) can be one of the keywords internal (for internal metadata), flex-internal (in v07 for variable-sized metadata; v07 otherwise defaults to fixed-size internal metadata), flex-external (for variable-sized external metadata), or a numeric matadata index (for fixed-size external metadata). See the meta-disk parameter in drbd.conf(5).

## OPTIONS
--force

Assume yes as the answer to all questions drbdmeta would ask.

--ignore-sanity-checks

Normally, drbdmeta performs some sanity checks before writing to the metadata device: for example, if the device appears to contain a file system, it refuses to destroy the file system by writing into it. Use this option to ignore these checks.

## COMMANDS
create-md [--peer-max-bio-size=val] (metadata versions v06, v07, and v08),

create-md {number-of-bitmap-slots} [--peer-max-bio-size=val] [--initialize-bitmap={automatic|zeroout|pwrite|skip}] [--al-stripes=val] [--al-stripe-size-kB=val] (metadata version v09) [--bitmap-block-size=val]

Initialize the metadata. This is necessary before a DRBD resource can be attached. If drbdmeta finds an older version of DRBD metadata on the device, it asks if the format should be converted.

When drbdadm calls drbdmeta's create-md command for a device, it sets the number-of-bitmap-slots argument to the number of peers in the resource. To reserve additional bitmap slots (which allows to add more peers in the future), call drbdmeta directly instead.

When a device is used before being connected to its peers the first time, DRBD assumes that peers can only handle 4 KiB requests by default. The --peer-max-bio-size option allows to set more optimistic values; use this if the versions of DRBD that this device will connect to are known. DRBD supports a maximum bio size of 32 KiB since version 8.3.8, of 128 KiB since version 8.3.9, and of 1 MiB since version 8.4.0.

By default, we explicitly initialize the bitmap area to all zero. With --initialize-bitmap you can chose to only try the fast method (zeroout, try ioctl BLKZEROOUT only), only use explicit pwrite calls, or skip this bitmap initialization phase completely. If you intend to do an initial full sync anyways, you can use skip to leave the bitmap initialization to the kernel. This can make a noticable difference when initializing huge volumes. Default is automatic, which is zeroout with an implicit fallback to pwrite.

If you want to use more than 6433 activity log extents, or live on top of a spriped RAID, you may specify the number of stripes (--al-stripes, default 1), and the stripe size (--al-stripe-size-kB, default 32). To just use a larger linear on-disk ring-buffer, leave the number of stripes at 1, and increase the size only:

drbdmeta 0 v08 /dev/vg23/lv42 internal create-md --al-stripe-size 1M

To avoid a single "spindle" from becoming a bottleneck, increase the number of stripes, to achieve an interleaved layout of the on-disk activity-log transactions. What you give as "stripe-size" should be what is a.k.a. "chunk size" or "granularity" or "strip unit": the minimum skip to the next "spindle".

drbdmeta 0 v08 /dev/vg23/lv42 internal create-md --al-stripes 7 --al-stripe-size 64

With the --bitmap-block-size option you can change the change-tracking bitmap's granularity from 4KiB to another value. Allowed values are: 4k, 8k, 16k, 32k, 64k, 128k, 256k, 512k, 1M. The benefit of a larger block size is a reduced bitmap size and a smaller memory footprint for the DRBD volume. The disadvantage is a higher resync volume if the workload writes to the DRBD devices at a finer granularity, since drbd rounds each modified block up to a complete bitmap block for change tracking, and later resync.

get-gi [--node-id=id]

Show the data generation identifiers for a device on a particular connection. DRBD version 9.0.0 and beyond support multiple peers; use the node-id option to define which peer's data generation identifiers to show.

show-gi [--node-id=id]

Similar to get-gi, but with explanatory information.

dump-md

Dump the metadata of a device in text form, including the bitmap and activity log.

outdate

Mark the data on a lower-level device as outdated. See drbdsetup(8) for details.

dstate

Show the current disk state of a lower-level device.

check-resize

Examine the device size of a lower-level device and its last known device size (saved in /var/lib/drbd/drbd-minor-minor.lkbd by drbdsetup check-resize). For internal metadata, if the size of the lower-level device has changed and the metadata can be found at the previous position, move the metadata to the new position at the end of the block device.

apply-al

Apply the activity log of the specified device. This is necessary before the device can be attached by the kernel again.

repair-md [--tentative]

Repair known problems in metadata. Only problems that can be automatically fixed in a safe manner will be repaired. When --tentative is set, the metadata will only be checked, it will not be changed.

## EXPERT COMMANDS
The drbdmeta utility can be used to fine tune metdata. Please note that this can lead to destroyed metadata or even silent data corruption; use with great care only.

set-gi gi [--node-id=id]

Set the generation identifiers. The gi argument is a generation counter for the v06 and v07 formats, and a set of UUIDs for v08 and beyond. Accepts the same syntax as in the get-gi output. DRBD version 9.0.0 and beyond support multiple peers; use the --node-id option to define which peer's data generation identifiers to set.

restore-md dump_file

Replace the metadata on the device with the contents of dump_file. The dump file format is defined by the output of the dump-md command.

## VERSION
This document was revised for version 9.0.0 of the DRBD distribution.

## AUTHOR
Written by Philipp Reisner <philipp.reisner@linbit.com> and Lars Ellenberg <lars.ellenberg@linbit.com>.

## REPORTING BUGS
Report bugs to <drbd-user@lists.linbit.com>.

## COPYRIGHT
Copyright 2001-2008,2012 LINBIT Information Technologies, Philipp Reisner, Lars Ellenberg. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

## SEE ALSO
drbdadm(8) drbd.conf(5)


drbdmon

title: drbdmon(8)

summary: Monitor DRBD resources realtime

text:
# drbdmon(8)

## NAME
drbdmon - Monitor DRBD resources realtime

## SYNOPSIS
drbdmon [options...] [-- [backend-options...]] {command} {context...}

## DESCRIPTION
The drbdmon utility is used for monitoring volumes and connections realtime, as defined in DRBD resource files. See drbd.conf(5) for more information.

## OPTIONS
-d, --dry-run

Show which commands drbdmon would execute instead of actually executing them (for example, drbdmon -d up resource). This can be a useful way to learn how drbdsetup and drbdmeta are used.

--ascii

Use only ascii characters (no Unicode).

--no-header

Do not display the drbdmon header line

--no-hotkeys

Do not display the hotkeys line.

## COMMANDS
c {device}

Clear screen.

r

Repaint display.

q

Quit.

## VERSION
This document was revised for version 9.0.0 of the DRBD distribution.

## REPORTING BUGS
Report bugs to <drbd-user@lists.linbit.com>.

## COPYRIGHT
Copyright 2016-2017 LINBIT Information Technologies, Robert Altnoeder, Sam Leonard. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

## SEE ALSO
drbd.conf(5), drbd(8), drbdsetup(8), drbdmeta(8) and the DRBD project web site[1]

## AUTHORS
Robert Altnoeder <robert.altnoeder@linbit.com>

Primary author of drbdmon

Sam Leonard <sam@linbit.com>

man page and build system integration

## NOTES
1.

DRBD project web site

http://www.drbd.org/