drbdmeta {
device
} [ v06 minor | v07 meta_dev index | v08 meta_dev index ] {
command
} [
cmd args
...]
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 use it through the front end drbdadm.
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 select which the version of the meta data. Currently all major DRBD releases (0.6, 0.7 and 0.8) are supported.
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.
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 0.8 it is a set of UUIDs.
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. This is used by the peer node when it wants to become primary, but cannot communicate with the DRBD stack on this host.
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.
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.
Written by Philipp Reisner <philipp.reisner@linbit.com>
and Lars Ellenberg <lars.ellenberg@linbit.com>.