drbdmeta(8)

1DRBDMETA(8)                  System Administration                 DRBDMETA(8)
2
3
4

NAME

6       drbdmeta - DRBD's meta data management tool
7

SYNOPSIS

9       drbdmeta [--force] [--ignore-sanity-checks] {device} {v06 minor |
10                v07 meta_dev index | v08 meta_dev index} {command}
11                [cmd args...]
12

DESCRIPTION

14       Drbdmeta is used to create, display and modify the contents of DRBD's
15       meta data storage. Usually you do not want to use this command
16       directly, but start it via the frontend drbdadm(8).
17
18       This command only works if the DRBD resource is currently down, or at
19       least detached from its backing storage. The first parameter is the
20       device node associated to the resource. With the second parameter you
21       can select the version of the meta data. Currently all major DRBD
22       releases (0.6, 0.7 and 8) are supported.
23

OPTIONS

25       --force
26
27           All questions that get asked by drbdmeta are treated as if the user
28           answered 'yes'.
29
30       --ignore-sanity-checks
31
32           Some sanity checks cause drbdmeta to terminate. E.g. if a file
33           system image would get destroyed by creating the meta data. By
34           using that option you can force drbdmeta to ignore these checks.
35

COMMANDS

37       create-md --peer-max-bio-size val --al-stripes val --al-stripe-size-kB
38       val
39
40           Create-md initializes the meta data storage. This needs to be done
41           before a DRBD resource can be taken online for the first time. In
42           case there is already a meta data signature of an older format in
43           place, drbdmeta will ask you if it should convert the older format
44           to the selected format.
45
46           If you will use the resource before it is connected to its peer for
47           the first time DRBD may perform better if you use the
48           --peer-max-bio-size option. For DRBD versions of the peer use up to
49           these values: <8.3.7 -> 4k, 8.3.8 -> 32k, 8.3.9 -> 128k, 8.4.0 ->
50           1M.
51
52           If you want to use more than 6433 activity log extents, or live on
53           top of a spriped RAID, you may specify the number of stripes
54           (--al-stripes, default 1), and the stripe size
55           (--al-stripe-size-kB, default 32). To just use a larger linear
56           on-disk ring-buffer, leave the number of stripes at 1, and increase
57           the size only:
58
59           drbdmeta 0 v08 /dev/vg23/lv42 internal create-md --al-stripe-size
60           1M
61
62           To avoid a single "spindle" from becoming a bottleneck, increase
63           the number of stripes, to achieve an interleaved layout of the
64           on-disk activity-log transactions. What you give as "stripe-size"
65           should be what is a.k.a. "chunk size" or "granularity" or "strip
66           unit": the minimum skip to the next "spindle".
67
68           drbdmeta 0 v08 /dev/vg23/lv42 internal create-md --al-stripes 7
69           --al-stripe-size 64k
70
71       get-gi
72
73           Get-gi shows a short textual representation of the data generation
74           identifier. In version 0.6 and 0.7 these are generation counters,
75           while in version 8 it is a set of UUIDs.
76
77       show-gi
78
79           Show-gi prints a textual representation of the data generation
80           identifiers including explanatory information.
81
82       dump-md
83
84           Dumps the whole contents of the meta data storage including the
85           stored bit-map and activity-log in a textual representation.
86
87       outdate
88
89           Sets the outdated flag in the meta data. This is used by the peer
90           node when it wants to become primary, but cannot communicate with
91           the DRBD stack on this host.
92
93       dstate
94
95           Prints the state of the data on the backing storage. The output is
96           always followed by '/DUnknown' since drbdmeta only looks at the
97           local meta data.
98
99       check-resize
100
101           Examines the device size of a backing device, and it's last known
102           device size, recorded in a file /var/lib/drbd/drbd-minor-??.lkbd.
103           In case the size of the backing device changed, and the meta data
104           can be found at the old position, it moves the meta data to the
105           right position at the end of the block device.
106

EXPERTS COMMANDS

108       Drbdmeta allows you to modify the meta data as well. This is
109       intentionally omitted for the command's usage output, since you should
110       only use it if you really know what you are doing. By setting the
111       generation identifiers to wrong values, you risk to overwrite your
112       up-to-data data with an older version of your data.
113
114       set-gi gi
115
116           Set-gi allows you to set the generation identifier.  Gi needs to be
117           a generation counter for the 0.6 and 0.7 format, and a UUID set for
118           8.x. Specify it in the same way as get-gi shows it.
119
120       restore-md dump_file
121
122           Reads the dump_file and writes it to the meta data.
123

VERSION

125       This document was revised for version 8.3.2 of the DRBD distribution.
126

AUTHOR

128       Written by Philipp Reisner <philipp.reisner@linbit.com> and Lars
129       Ellenberg <lars.ellenberg@linbit.com>.
130

REPORTING BUGS

132       Report bugs to <drbd-user@lists.linbit.com>.
133

COPYRIGHT

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