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.
-d, --dry-runJust 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-08.conf and
/etc/drbd.conf.
-s, --drbdsetup
file Specifies the full path to the drbdsetup program. If this option is
omitted, drbdadm will look for /sbin/drbdsetup and ./drbdsetup.
-m, --drbdmeta
file Specifies the full path to the drbdmeta program. If this option is
omitted, drbdadm will look for /sbin/drbdmeta and
./drbdsetup.
Attaches a local backing block device to the DRBD resource's device. In file system language this would be the mount operation.
Removes the backing storage device from a DRBD resources'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.
Removes the network configuration from the resource. The device will go into StandAllone state.
Loads the resynchronization parameters into the device.
Is a shortcut for attach and connect.
Is a shortcut for disconnect and detach.
Switch the resource's device into primary state. You need to do this before you may mount a filesystem onto the device.
Brings the device back into secondary state. This is needed since in a connected DRBD device pair there might only be one of the two peers in primary state.
This forces DRBD to consider the data on the local backing storage device as out-of-sync. Therefor 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, but the backing storage of the peer is invalidated and hence rewritten with the data of the local node.
DRBD will reexamine all sizing constraints, and re-size the resource's device accordingly. E.g. 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 _both_ nodes.
Create-md initializes the meta data storage. This needs to be done before a DRBD resource can be taken online for the first time.
Get-gi shows a short textual repesentation of the data generation identifier.
Show-gi 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 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 states of the devices (local/peer). E.g. primary/secondary
Shows the current connection status of the devices.
Just parse the configuration file and dump it to stdout. Might 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 oudate-peer handler.
Temporarily suspend an ongoing resynchronisation by setting the local pause flag. Resync only progresses if neighter the local nor the remote pause flag is set. It might be desirable to postpone DRBD's resynchronisation after eventual resynchronisation of the backing storage's RAID setup.
Unset the local sync pause flag.
Show the current state of the backing storeage devices. (local/peer)
Shows all on purpose undocumented commands.
Written by Philipp Reisner <philipp.reisner@linbit.com>
and Lars Ellenberg <lars.ellenberg@linbit.com>