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

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

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

Specifies the full path to the drbdsetup program. If this option is omitted, drbdadm will look for /sbin/drbdsetup and ./drbdsetup.

Specifies the full path to the drbdmeta program. If this option is omitted, drbdadm will look for /sbin/drbdmeta and ./drbdmeta.

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

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

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.

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

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

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.

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

Loads the resynchronization parameters into the device.

Is a shortcut for attach and connect.

Is a shortcut for disconnect and detach.

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.

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).

Forces DRBD to consider the data on the local backing storage device as out-of-sync. Therefore DRBD will copy each and every block over from its peer, to bring the local storage device back in sync.

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.

Causes DRBD to re-examine all sizing constraints, and resize the resource's device accordingly. For example in case you increased the size of your backing storage devices (on both nodes of course), then DRBD will adopt to 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.

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.

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)

Shows a short textual representation of the data generation identifiers.

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

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

Sets the outdated flag in the meta data.

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.

Waits until the device is connected to its peer device.

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

Deprecated alias for "role", see above.

Shows the current connection state of the devices.

Shows the current status of all devices defined in the current config file, in xml-like format. Example output:

<drbd-status version="8.3.2" api="88">
<resources config_file="/etc/drbd.conf">
<resource minor="0" name="s0" cs="SyncTarget" st1="Secondary" st2="Secondary"
          ds1="Inconsistent" ds2="UpToDate" resynced_precent ="5.9" />
<resource minor="1" name="s1" cs="WFConnection" st1="Secondary"
          st2="Unknown" ds1="Inconsistent" ds2="Outdated" />
<resource minor="3" name="dummy" cs="Unconfigured" />
<!-- resource minor="4" name="scratch" not available or not yet created -->
</resources>
</drbd-status>

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

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

Starts online verify. During online verify, data on both nodes is compared for inconsistency. 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.

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.

Unset the local sync pause flag.

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.

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

Shows all commands undocumented on purpose.