bsradm

SYNOPSIS

bsradm [options...] [-- [ backend-options...]] {command} {context...}

DESCRIPTION

The bsradm utility is used for managing bsr based on its configuration files, see bsr.conf(5). It translates high-level commands into one or more lower-level commands for the bsrsetup and bsrmeta utilities, which control the kernel module and manipulate the on-disk metadata.Depending on the command, the bsradm utility operates on one or more resources, devices, connections, or peer devices. The following command contexts are defined:resource

...

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

OPTIONS

-d, --dry-run

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

...

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 ( bsradm down all followed by bsradm 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.

...

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

bsrsetup

...

drbdsetup command {argument...} [option...]

DESCRIPTION

The drbdsetup utility serves to configure the DRBD kernel module and to show its current configuration. Users usually interact with the drbdadm utility, which provides a more high-level interface to DRBD than drbdsetup. (See drbdadm's --dry-run option to see how drbdadm uses drbdsetup.)Some option arguments have a default scale which applies when a plain number is specified (for example Kilo, or 1024 times the numeric value). Such default scales can be overridden by using a suffix (for example, M for Mega). The common suffixes K = 2^10 = 1024, M = 1024 K, and G = 1024 M are supported.

COMMANDS

drbdsetup attach minor lower_dev meta_data_dev meta_data_index, 

drbdsetup disk-options minor

...

The forget-peer command removes all traces of a peer node from the meta-data. It frees a bitmap slot in the meta-data and make it avalable for futher bitmap slot allocation in case a so-far never seen node connects. The connection must be taken down before this command may be used. In case the peer re-connects at a later point a bit-map based resync will be turned into a full-sync.

bsrmeta

...

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

...

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

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.

...