Debian Codegraph @

UG9/cn/administration-manual.po

raw
1 # SOME DESCRIPTIVE TITLE
2 # Copyright (C) YEAR Free Software Foundation, Inc.
3 # This file is distributed under the same license as the PACKAGE package.
4 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
5 #
6 msgid ""
7 msgstr ""
8 "Project-Id-Version: \n"
9 "POT-Creation-Date: 2020-03-03 07:56+0000\n"
10 "PO-Revision-Date: 2020-03-04 19:28+0800\n"
11 "Language: zh\n"
12 "MIME-Version: 1.0\n"
13 "Content-Type: text/plain; charset=UTF-8\n"
14 "Content-Transfer-Encoding: 8bit\n"
15 "Last-Translator: \n"
16 "Language-Team: \n"
17 "X-Generator: Poedit 2.0.6\n"
18
19 #. type: Title ==
20 #, no-wrap
21 msgid "Common administrative tasks"
22 msgstr "常见管理任务"
23
24 #. type: Plain text
25 msgid ""
26 "This chapter outlines typical administrative tasks encountered during day-to-day operations. It does not cover troubleshooting "
27 "tasks, these are covered in detail in <<ch-troubleshooting>>."
28 msgstr "本章概述了日常运营中遇到的典型管理任务。它不包括故障排除任务,故障排除任务在<<ch-troubleshooting>>中有详细介绍。"
29
30 #. type: Title ===
31 #, no-wrap
32 msgid "Checking DRBD status"
33 msgstr "检查DRBD状态"
34
35 #. type: Title ====
36 #, no-wrap
37 msgid "Retrieving status with drbdmon"
38 msgstr "使用drbdmon检索状态"
39
40 #. type: Plain text
41 msgid "One convenient way to look at DRBD's status is the `drbdmon` utility. It updates the state of DRBD resources in realtime."
42 msgstr "查看DRBD状态的一种方便方法是 `drbdmon` 组件。它实时更新DRBD资源的状态。"
43
44 #. type: Title ====
45 #, no-wrap
46 msgid "Retrieving status and interacting with DRBD via drbdtop"
47 msgstr "通过drbdtop检索状态并与DRBD交互"
48
49 #. type: Plain text
50 msgid ""
51 "As its name suggests, `drbdtop` shares similarities with tools like `htop`. On one hand it allows monitoring of DRBD resources as "
52 "well as interacting (e.g., switching them to _Primary_, or even resolving split-brains). A complete overview can be found "
53 "here[https://linbit.github.io/drbdtop/]."
54 msgstr ""
55 "顾名思义,`drbdtop` 与 `htop` 等工具有相似之处。一方面,它允许监控DRBD资源以及交互(例如,将它们切换到 _Primary_ ,甚至解决裂脑问"
56 "题)。完整的概述可以在这里找到[https://linbit.github.io/drbdtop/]。"
57
58 #. type: Title ====
59 #, no-wrap
60 msgid "Status information in `/proc/drbd`"
61 msgstr "`/proc/drbd中的状态信息`"
62
63 #. type: Plain text
64 msgid ""
65 "`/proc/drbd` is deprecated. While it won't be removed in the 8.4 series, we recommend to switch to other means, like <<s-drbdadm-"
66 "status>>; or, for monitoring even more convenient, <<s-drbdsetup-events2>>."
67 msgstr ""
68 "`/proc/drbd` 已弃用。虽然它不会在8.4系列中删除,但我们建议切换到其他方式,如<<s-drbdadm-status>>;或者,为了更方便地监视:<<s-"
69 "drbdsetup-events2>>。"
70
71 #. type: Plain text
72 msgid ""
73 "indexterm:[/proc/drbd]`/proc/drbd` is a virtual file displaying basic information about the DRBD module. It was used extensively "
74 "up to DRBD 8.4, but couldn't keep up with the amount of information provided by DRBD 9."
75 msgstr ""
76 "indexterm:[/proc/drbd]`/proc/drbd` 是一个虚拟文件,显示有关drbd模块的基本信息。在DRBD 8.4之前,它被广泛使用,但无法跟上DRBD 9提供的"
77 "信息量。"
78
79 #. type: delimited block -
80 #, no-wrap
81 msgid ""
82 "$ cat /proc/drbd\n"
83 "version: 9.0.0 (api:1/proto:86-110) FIXME\n"
84 "GIT-hash: XXX build by [email protected], 2011-10-12 09:07:35\n"
85 msgstr ""
86 "$ cat /proc/drbd\n"
87 "version: 9.0.0 (api:1/proto:86-110) FIXME\n"
88 "GIT-hash: XXX build by [email protected], 2011-10-12 09:07:35\n"
89
90 #. type: Plain text
91 msgid ""
92 "The first line, prefixed with `version:`, shows the DRBD version used on your system. The second line contains information about "
93 "this specific build."
94 msgstr "第一行以 `version:` 为前缀,显示系统上使用的DRBD版本。第二行包含有关此特定生成的信息。"
95
96 #. type: Title ====
97 #, no-wrap
98 msgid "Status information via `drbdadm`"
99 msgstr "通过 `drbdadm` 获取状态信息"
100
101 #. type: Plain text
102 msgid "indexterm:[drbdadm, status]In its simplest invocation, we just ask for the status of a single resource."
103 msgstr "indexterm:[drbdadm, status]在其最简单的调用中,我们只需请求单个资源的状态。"
104
105 #. type: delimited block -
106 #, no-wrap
107 msgid ""
108 "# drbdadm status home\n"
109 "home role:Secondary\n"
110 " disk:UpToDate\n"
111 " nina role:Secondary\n"
112 " disk:UpToDate\n"
113 " nino role:Secondary\n"
114 " disk:UpToDate\n"
115 " nono connection:Connecting\n"
116 msgstr ""
117 "# drbdadm status home\n"
118 "home role:Secondary\n"
119 " disk:UpToDate\n"
120 " nina role:Secondary\n"
121 " disk:UpToDate\n"
122 " nino role:Secondary\n"
123 " disk:UpToDate\n"
124 " nono connection:Connecting\n"
125
126 #. type: Plain text
127 msgid ""
128 "This here just says that the resource _home_ is locally, on 'nina', and on 'nino' _UpToDate_ and _Secondary_; so the three nodes "
129 "have the same data on their storage devices, and nobody is using the device currently."
130 msgstr ""
131 "这里表明资源_home_是本地的,在 `nina` 上以及在 `nino` 上,是 _UpToDate_ 的和 _Secondary_ 的,所以这三个节点在他们的存储设备上有相同的"
132 "数据,并且目前没有人在使用这个设备。"
133
134 #. type: Plain text
135 msgid ""
136 "The node 'nono' is not connected, its state is reported as _Connecting_; please see <<s-connection-states>> below for more "
137 "details."
138 msgstr "节点 `nono` 是未连接的,其状态报告为 Connecting_ ;有关详细信息,请参见下面的<<s-connection-states>>。"
139
140 #. type: Plain text
141 msgid ""
142 "You can get more information by passing the `--verbose` and/or `--statistics` arguments to `drbdsetup` (lines broken for "
143 "readability):"
144 msgstr "您可以通过将 `--verbose` 和/或 `--statistics` 参数传递给 `drbdsetup` 来获得更多信息(为了可读性,行输出将被打断):"
145
146 #. type: delimited block -
147 #, no-wrap
148 msgid ""
149 "# drbdsetup status home --verbose --statistics\n"
150 "home node-id:1 role:Secondary suspended:no\n"
151 " write-ordering:none\n"
152 " volume:0 minor:0 disk:UpToDate\n"
153 " size:1048412 read:0 written:1048412 al-writes:0 bm-writes:48 upper-pending:0\n"
154 " lower-pending:0 al-suspended:no blocked:no\n"
155 " nina local:ipv4:10.9.9.111:7001 peer:ipv4:10.9.9.103:7010 node-id:0\n"
156 " connection:Connected role:Secondary\n"
157 " congested:no\n"
158 " volume:0 replication:Connected disk:UpToDate resync-suspended:no\n"
159 " received:1048412 sent:0 out-of-sync:0 pending:0 unacked:0\n"
160 " nino local:ipv4:10.9.9.111:7021 peer:ipv4:10.9.9.129:7012 node-id:2\n"
161 " connection:Connected role:Secondary\n"
162 " congested:no\n"
163 " volume:0 replication:Connected disk:UpToDate resync-suspended:no\n"
164 " received:0 sent:0 out-of-sync:0 pending:0 unacked:0\n"
165 " nono local:ipv4:10.9.9.111:7013 peer:ipv4:10.9.9.138:7031 node-id:3\n"
166 " connection:Connecting\n"
167 msgstr ""
168 "# drbdsetup status home --verbose --statistics\n"
169 "home node-id:1 role:Secondary suspended:no\n"
170 " write-ordering:none\n"
171 " volume:0 minor:0 disk:UpToDate\n"
172 " size:1048412 read:0 written:1048412 al-writes:0 bm-writes:48 upper-pending:0\n"
173 " lower-pending:0 al-suspended:no blocked:no\n"
174 " nina local:ipv4:10.9.9.111:7001 peer:ipv4:10.9.9.103:7010 node-id:0\n"
175 " connection:Connected role:Secondary\n"
176 " congested:no\n"
177 " volume:0 replication:Connected disk:UpToDate resync-suspended:no\n"
178 " received:1048412 sent:0 out-of-sync:0 pending:0 unacked:0\n"
179 " nino local:ipv4:10.9.9.111:7021 peer:ipv4:10.9.9.129:7012 node-id:2\n"
180 " connection:Connected role:Secondary\n"
181 " congested:no\n"
182 " volume:0 replication:Connected disk:UpToDate resync-suspended:no\n"
183 " received:0 sent:0 out-of-sync:0 pending:0 unacked:0\n"
184 " nono local:ipv4:10.9.9.111:7013 peer:ipv4:10.9.9.138:7031 node-id:3\n"
185 " connection:Connecting\n"
186
187 #. type: Plain text
188 msgid ""
189 "Every few lines in this example form a block that is repeated for every node used in this resource, with small format exceptions "
190 "for the local node - see below for more details."
191 msgstr ""
192 "此示例中的每几行组成一个块,对于此资源中使用的每个节点重复此块,对于本地节点则有小的格式例外 - 有关详细信息,请参见下面的内容。"
193
194 #. type: Plain text
195 msgid ""
196 "The first line in each block shows the `node-id` (for the current resource; a host can have different ``node-id``s in different "
197 "resources). Furthermore the `role` (see <<s-roles>>) is shown."
198 msgstr ""
199 "每个块中的第一行显示 `node id`(对于当前资源;主机在不同资源中可以有不同的 `node id` )。此外,还显示了 `role` (请参见<<s-roles>>)。"
200
201 #. type: Plain text
202 msgid ""
203 "The next important line begins with the `volume` specification; normally these are numbered starting by zero, but the "
204 "configuration may specify other IDs as well. This line shows the indexterm:[connection state] connection state in the "
205 "`replication` item (see <<s-connection-states>> for details) and the remote indexterm:[disk state] disk state in `disk` (see <<s-"
206 "disk-states>>). Then there's a line for this volume giving a bit of statistics - data `received`, `sent`, `out-of-sync`, etc; "
207 "please see <<s-performance-indicators>> and <<s-conn-info>> for more information."
208 msgstr ""
209 "下一个重要的行以 `volume` 规范开始;这些规范通常以零开始编号,但配置也可能指定其他id。此行显示 `replication` 项中的 indexterm:"
210 "[connection state] 连接状态。(有关详细信息,请参见<<s-connection-states>>)和 `disk` 磁盘中的远程 indexterm:[disk state] 磁盘状态"
211 "(请参见<<s-disk-states>>)。还有一行是这个卷的,它提供了一些统计信息 - 数据 `已接收` 、`已发送` 、`未同步` 等;有关详细信息,请参见"
212 "<<s-performance-indicators>>和<<s-conn-info>>。"
213
214 #. type: Plain text
215 msgid ""
216 "For the local node the first line shows the resource name, _home_, in our example. As the first block always describes the local "
217 "node, there is no _Connection_ or address information."
218 msgstr "对于本地节点,在我们的示例中,第一行显示资源名 `home` 。由于第一个块始终描述本地节点,因此没有连接或地址信息。"
219
220 #. type: Plain text
221 msgid "please see the `drbd.conf` manual page for more information."
222 msgstr "有关详细信息,请参阅 `drbd.conf` 手册页。"
223
224 #. type: Plain text
225 msgid ""
226 "The other four lines in this example form a block that is repeated for every DRBD device configured, prefixed by the device minor "
227 "number. In this case, this is `0`, corresponding to the device `/dev/drbd0`."
228 msgstr "本例中的其他四行组成一个块,对每个配置的DRBD设备重复该块,前缀为设备次要编号。在本例中,这是 `0` ,对应于设备 `/dev/drbd0` 。"
229
230 #. type: Plain text
231 msgid "The resource-specific output contains various pieces of information about the resource:"
232 msgstr "特定于资源的输出包含有关资源的各种信息:"
233
234 #. //FIXME
235 #. .Replication protocol
236 #. The Replication protocol used by the resource. Either `A`, `B`, or `C`. See
237 #. <<s-replication-protocols>> for details.
238 #. type: Title ====
239 #, no-wrap
240 msgid "One-shot or realtime monitoring via `drbdsetup events2`"
241 msgstr "通过 `drbdsetup events2` 进行单次或实时监视`"
242
243 #. and 8.4.6
244 #. type: Plain text
245 msgid "This is available only with userspace versions 8.9.3 and up."
246 msgstr "这仅适用于8.9.3及更高版本的用户空间。"
247
248 #. type: Plain text
249 msgid "This is a low-level mechanism to get information out of DRBD, suitable for use in automated tools, like monitoring."
250 msgstr "这是一种从DRBD中获取信息的底层机制,适用于自动化工具,如监视。"
251
252 #. type: Plain text
253 msgid ""
254 "In its simplest invocation, showing only the current status, the output looks like this (but, when running on a terminal, will "
255 "include colors):"
256 msgstr "在最简单的调用中,仅显示当前状态,输出如下所示(但是,在终端上运行时,将包括颜色):"
257
258 #. type: delimited block -
259 #, no-wrap
260 msgid ""
261 "# drbdsetup events2 --now r0\n"
262 "exists resource name:r0 role:Secondary suspended:no\n"
263 "exists connection name:r0 peer-node-id:1 conn-name:remote-host connection:Connected role:Secondary\n"
264 "exists device name:r0 volume:0 minor:7 disk:UpToDate\n"
265 "exists device name:r0 volume:1 minor:8 disk:UpToDate\n"
266 "exists peer-device name:r0 peer-node-id:1 conn-name:remote-host volume:0\n"
267 " replication:Established peer-disk:UpToDate resync-suspended:no\n"
268 "exists peer-device name:r0 peer-node-id:1 conn-name:remote-host volume:1\n"
269 " replication:Established peer-disk:UpToDate resync-suspended:no\n"
270 "exists -\n"
271 msgstr ""
272 "# drbdsetup events2 --now r0\n"
273 "exists resource name:r0 role:Secondary suspended:no\n"
274 "exists connection name:r0 peer-node-id:1 conn-name:remote-host connection:Connected role:Secondary\n"
275 "exists device name:r0 volume:0 minor:7 disk:UpToDate\n"
276 "exists device name:r0 volume:1 minor:8 disk:UpToDate\n"
277 "exists peer-device name:r0 peer-node-id:1 conn-name:remote-host volume:0\n"
278 " replication:Established peer-disk:UpToDate resync-suspended:no\n"
279 "exists peer-device name:r0 peer-node-id:1 conn-name:remote-host volume:1\n"
280 " replication:Established peer-disk:UpToDate resync-suspended:no\n"
281 "exists -\n"
282
283 #. type: Plain text
284 msgid "Without the ''--now'', the process will keep running, and send continuous updates like this:"
285 msgstr "如果没有 ''--now'' ,进程将继续运行,并发送连续更新,如下所示:"
286
287 #. type: delimited block -
288 #, no-wrap
289 msgid ""
290 "# drbdsetup events2 r0\n"
291 "...\n"
292 "change connection name:r0 peer-node-id:1 conn-name:remote-host connection:StandAlone\n"
293 "change connection name:r0 peer-node-id:1 conn-name:remote-host connection:Unconnected\n"
294 "change connection name:r0 peer-node-id:1 conn-name:remote-host connection:Connecting\n"
295 msgstr ""
296 "# drbdsetup events2 r0\n"
297 "...\n"
298 "change connection name:r0 peer-node-id:1 conn-name:remote-host connection:StandAlone\n"
299 "change connection name:r0 peer-node-id:1 conn-name:remote-host connection:Unconnected\n"
300 "change connection name:r0 peer-node-id:1 conn-name:remote-host connection:Connecting\n"
301
302 #. type: Plain text
303 msgid ""
304 "Then, for monitoring purposes, there's another argument ''--statistics'', that will produce some performance counters and other "
305 "facts:"
306 msgstr "然后,出于监控的目的,还有另一个参数 ''--statistics'',它将生成一些性能计数器和其他指标:"
307
308 #. type: Plain text
309 msgid "'drbdsetup' **verbose output** (lines broken for readability):"
310 msgstr "`drbdsetup` **verbose output**(为可读性而换行输出):"
311
312 #. type: delimited block -
313 #, no-wrap
314 msgid ""
315 "# drbdsetup events2 --statistics --now r0\n"
316 "exists resource name:r0 role:Secondary suspended:no write-ordering:drain\n"
317 "exists connection name:r0 peer-node-id:1 conn-name:remote-host connection:Connected\n"
318 " role:Secondary congested:no\n"
319 "exists device name:r0 volume:0 minor:7 disk:UpToDate size:6291228 read:6397188\n"
320 " written:131844 al-writes:34 bm-writes:0 upper-pending:0 lower-pending:0\n"
321 " al-suspended:no blocked:no\n"
322 "exists device name:r0 volume:1 minor:8 disk:UpToDate size:104854364 read:5910680\n"
323 " written:6634548 al-writes:417 bm-writes:0 upper-pending:0 lower-pending:0\n"
324 " al-suspended:no blocked:no\n"
325 "exists peer-device name:r0 peer-node-id:1 conn-name:remote-host volume:0\n"
326 " replication:Established peer-disk:UpToDate resync-suspended:no received:0\n"
327 " sent:131844 out-of-sync:0 pending:0 unacked:0\n"
328 "exists peer-device name:r0 peer-node-id:1 conn-name:remote-host volume:1\n"
329 " replication:Established peer-disk:UpToDate resync-suspended:no received:0\n"
330 " sent:6634548 out-of-sync:0 pending:0 unacked:0\n"
331 "exists -\n"
332 msgstr ""
333 "# drbdsetup events2 --statistics --now r0\n"
334 "exists resource name:r0 role:Secondary suspended:no write-ordering:drain\n"
335 "exists connection name:r0 peer-node-id:1 conn-name:remote-host connection:Connected\n"
336 " role:Secondary congested:no\n"
337 "exists device name:r0 volume:0 minor:7 disk:UpToDate size:6291228 read:6397188\n"
338 " written:131844 al-writes:34 bm-writes:0 upper-pending:0 lower-pending:0\n"
339 " al-suspended:no blocked:no\n"
340 "exists device name:r0 volume:1 minor:8 disk:UpToDate size:104854364 read:5910680\n"
341 " written:6634548 al-writes:417 bm-writes:0 upper-pending:0 lower-pending:0\n"
342 " al-suspended:no blocked:no\n"
343 "exists peer-device name:r0 peer-node-id:1 conn-name:remote-host volume:0\n"
344 " replication:Established peer-disk:UpToDate resync-suspended:no received:0\n"
345 " sent:131844 out-of-sync:0 pending:0 unacked:0\n"
346 "exists peer-device name:r0 peer-node-id:1 conn-name:remote-host volume:1\n"
347 " replication:Established peer-disk:UpToDate resync-suspended:no received:0\n"
348 " sent:6634548 out-of-sync:0 pending:0 unacked:0\n"
349 "exists -\n"
350
351 #. type: Plain text
352 msgid "You might also like the ''--timestamp'' parameter."
353 msgstr "您可能还喜欢 ''--timestamp'' 参数。"
354
355 #. type: Title ====
356 #, no-wrap
357 msgid "Connection states"
358 msgstr "连接状态"
359
360 #. type: Plain text
361 msgid ""
362 "indexterm:[drbdadm, cstate]indexterm:[connection state, via drbdadm]A resource's connection state can be observed either by "
363 "issuing the `drbdadm cstate` command:"
364 msgstr "indexterm:[drbdadm, cstate]indexterm:[connection state, via drbdadm]可以通过调用 `drbdadm cstate` 命令来观察资源的连接状态:"
365
366 #. type: delimited block -
367 #, no-wrap
368 msgid ""
369 "# drbdadm cstate <resource>\n"
370 "Connected\n"
371 "Connected\n"
372 "StandAlone\n"
373 msgstr ""
374 "# drbdadm cstate <resource>\n"
375 "Connected\n"
376 "Connected\n"
377 "StandAlone\n"
378
379 #. type: Plain text
380 msgid "If you are interested in only a single connection of a resource, specify the connection name, too:"
381 msgstr "如果只对资源的单个连接感兴趣,请指定连接名称:"
382
383 #. type: Plain text
384 msgid "The default is the peer's hostname as given in the configuration file."
385 msgstr "默认值是配置文件中给定的节点主机名。"
386
387 #. type: delimited block -
388 #, no-wrap
389 msgid ""
390 "# drbdadm cstate <peer>:<resource>\n"
391 "Connected\n"
392 msgstr ""
393 "# drbdadm cstate <peer>:<resource>\n"
394 "Connected\n"
395
396 #. type: Plain text
397 msgid "A resource may have one of the following connection states:"
398 msgstr "资源可能具有以下连接状态之一:"
399
400 #. type: Block title
401 #, no-wrap
402 msgid "_StandAlone_"
403 msgstr "_StandAlone_"
404
405 #. type: Plain text
406 msgid ""
407 "indexterm:[connection state, StandAlone]No network configuration available. The resource has not yet been connected, or has been "
408 "administratively disconnected (using `drbdadm disconnect`), or has dropped its connection due to failed authentication or split "
409 "brain."
410 msgstr ""
411 "indexterm:[connection state, StandAlone]没有可用的网络配置。资源尚未连接,或者已被管理性断开(使用 `drbdadm disconnect` ),或者由于"
412 "身份验证失败或脑裂而断开其连接。"
413
414 #. type: Block title
415 #, no-wrap
416 msgid "_Disconnecting_"
417 msgstr "_Disconnecting_"
418
419 #. type: Plain text
420 msgid "indexterm:[connection state, Disconnecting]Temporary state during disconnection. The next state is _StandAlone_."
421 msgstr "indexterm:[connection state, Disconnecting]断开连接期间的临时状态。下一个状态是 _StandAlone_。"
422
423 #. type: Block title
424 #, no-wrap
425 msgid "_Unconnected_"
426 msgstr "_Unconnected_"
427
428 #. type: Plain text
429 msgid "indexterm:[connection state, Unconnected]Temporary state, prior to a connection attempt. Possible next states: _Connecting_."
430 msgstr "indexterm:[connection state, Unconnected]临时状态,在尝试连接之前。可能的下一个状态: _Connecting_。"
431
432 #. type: Block title
433 #, no-wrap
434 msgid "_Timeout_"
435 msgstr "_Timeout_"
436
437 #. type: Plain text
438 msgid ""
439 "indexterm:[connection state, Timeout]Temporary state following a timeout in the communication with the peer. Next state: "
440 "_Unconnected_."
441 msgstr "indexterm:[connection state, Timeout]与对等方通信超时后的临时状态。下一个状态:_Unconnected_。"
442
443 #. type: Block title
444 #, no-wrap
445 msgid "_BrokenPipe_"
446 msgstr "_BrokenPipe_"
447
448 #. type: Plain text
449 msgid ""
450 "indexterm:[connection state, BrokenPipe]Temporary state after the connection to the peer was lost. Next state: _Unconnected_."
451 msgstr "indexterm:[connection state, BrokenPipe]与对等方的连接丢失后的临时状态。下一个状态: _Unconnected_ 。"
452
453 #. type: Block title
454 #, no-wrap
455 msgid "_NetworkFailure_"
456 msgstr "_NetworkFailure_"
457
458 #. type: Plain text
459 msgid ""
460 "indexterm:[connection state, NetworkFailure]Temporary state after the connection to the partner was lost. Next state: "
461 "_Unconnected_."
462 msgstr "indexterm:[connection, state, NetworkFailure]与伙伴的连接丢失后的临时状态。下一个状态: _Unconnected_。"
463
464 #. type: Block title
465 #, no-wrap
466 msgid "_ProtocolError_"
467 msgstr "_ProtocolError_"
468
469 #. type: Plain text
470 msgid ""
471 "indexterm:[connection state, ProtocolError]Temporary state after the connection to the partner was lost. Next state: "
472 "_Unconnected_."
473 msgstr "indexterm:[connection state, ProtocolError]与伙伴的连接丢失后的临时状态。下一个状态:_Unconnected_。"
474
475 #. type: Block title
476 #, no-wrap
477 msgid "_TearDown_"
478 msgstr "_TearDown_"
479
480 #. type: Plain text
481 msgid "indexterm:[connection state, TearDown]Temporary state. The peer is closing the connection. Next state: _Unconnected_."
482 msgstr "indexterm:[connection state, TearDown]临时状态。对等方正在关闭连接。下一个状态: _Unconnected_。"
483
484 #. type: Block title
485 #, no-wrap
486 msgid "_Connecting_"
487 msgstr "_Connecting_"
488
489 #. type: Plain text
490 msgid "indexterm:[connection state, Connecting]This node is waiting until the peer node becomes visible on the network."
491 msgstr "indexterm:[connection state, Connecting]此节点正在等待,直到对等节点在网络上变为可见。"
492
493 #. type: Block title
494 #, no-wrap
495 msgid "_Connected_"
496 msgstr "_Connected_"
497
498 #. type: Plain text
499 msgid ""
500 "indexterm:[connection state, Connected]A DRBD connection has been established, data mirroring is now active. This is the normal "
501 "state."
502 msgstr "indexterm:[connection state, Connected]已建立DRBD连接,数据镜像现在处于活动状态。这是正常状态。"
503
504 #. type: Title ====
505 #, no-wrap
506 msgid "Replication states"
507 msgstr "复制状态"
508
509 #. type: Plain text
510 msgid "Each volume has over each connection a replication state. The possible replication states are:"
511 msgstr "每个卷在每个连接上都有一个复制状态。可能的复制状态是:"
512
513 #. type: Block title
514 #, no-wrap
515 msgid "_Off_"
516 msgstr "_Off_"
517
518 #. type: Plain text
519 msgid ""
520 "indexterm:[replication state, Off]The volume is not replicated over this connection, since the connection is not _Connected_."
521 msgstr "indexterm:[replication state, Off]由于连接未连接,因此卷未通过此连接进行复制。"
522
523 #. type: Block title
524 #, no-wrap
525 msgid "_Established_"
526 msgstr "_Established_"
527
528 #. type: Plain text
529 msgid "indexterm:[replication state, Established]All writes to that volume are replicated online. This is the normal state."
530 msgstr "indexterm:[replication state, Established]对该卷的所有写入都将在线复制。这是正常状态。"
531
532 #. type: Block title
533 #, no-wrap
534 msgid "_StartingSyncS_"
535 msgstr "_StartingSyncS_"
536
537 #. type: Plain text
538 msgid ""
539 "indexterm:[replication state, StartingSyncS]Full synchronization, initiated by the administrator, is just starting. The next "
540 "possible states are: _SyncSource_ or _PausedSyncS_."
541 msgstr ""
542 "indexterm:[replication state, StartingSyncS]由管理员启动的完全同步正在启动。下一个可能的状态是: _SyncSource_ 或 _PausedSyncS_ 。"
543
544 #. type: Block title
545 #, no-wrap
546 msgid "_StartingSyncT_"
547 msgstr "_StartingSyncT_"
548
549 #. type: Plain text
550 msgid ""
551 "indexterm:[replication state, StartingSyncT]Full synchronization, initiated by the administrator, is just starting. Next state: "
552 "_WFSyncUUID_."
553 msgstr "indexterm:[replication state, StartingSyncT]由管理员启动的完全同步正在启动。下一个状态:_WFSyncUUID_。"
554
555 #. type: Block title
556 #, no-wrap
557 msgid "_WFBitMapS_"
558 msgstr "_WFBitMapS_"
559
560 #. type: Plain text
561 msgid ""
562 "indexterm:[replication state, WFBitMapS]Partial synchronization is just starting. Next possible states: _SyncSource_ or "
563 "_PausedSyncS_."
564 msgstr "indexterm:[replication state, WFBitMapS]部分同步刚刚开始。下一个可能的状态:_SyncSource_或_PausedSyncS_。"
565
566 #. type: Block title
567 #, no-wrap
568 msgid "_WFBitMapT_"
569 msgstr "_WFBitMapT_"
570
571 #. type: Plain text
572 msgid "indexterm:[replication state, WFBitMapT]Partial synchronization is just starting. Next possible state: _WFSyncUUID_."
573 msgstr "indexterm:[replication state, WFBitMapT]部分同步刚刚开始。下一个可能的状态:_WFSyncUUID_。"
574
575 #. type: Block title
576 #, no-wrap
577 msgid "_WFSyncUUID_"
578 msgstr "_WFSyncUUID_"
579
580 #. type: Plain text
581 msgid ""
582 "indexterm:[replication state, WFSyncUUID]Synchronization is about to begin. Next possible states: _SyncTarget_ or _PausedSyncT_."
583 msgstr "indexterm:[replication state, WFSyncUUID]同步即将开始。下一个可能的状态:_SyncTarget_或_PausedSyncT_。"
584
585 #. type: Block title
586 #, no-wrap
587 msgid "_SyncSource_"
588 msgstr "_SyncSource_"
589
590 #. type: Plain text
591 msgid ""
592 "indexterm:[replication state, SyncSource]Synchronization is currently running, with the local node being the source of "
593 "synchronization."
594 msgstr "indexterm:[replication state, SyncSource]同步当前正在运行,本地节点是同步源。"
595
596 #. type: Block title
597 #, no-wrap
598 msgid "_SyncTarget_"
599 msgstr "_SyncTarget_"
600
601 #. type: Plain text
602 msgid ""
603 "indexterm:[replication state, SyncTarget]Synchronization is currently running, with the local node being the target of "
604 "synchronization."
605 msgstr "indexterm:[replication state, SyncTarget]同步当前正在运行,本地节点是同步的目标。"
606
607 #. type: Block title
608 #, no-wrap
609 msgid "_PausedSyncS_"
610 msgstr "_PausedSyncS_"
611
612 #. type: Plain text
613 msgid ""
614 "indexterm:[replication state, PausedSyncS]The local node is the source of an ongoing synchronization, but synchronization is "
615 "currently paused. This may be due to a dependency on the completion of another synchronization process, or due to synchronization "
616 "having been manually interrupted by `drbdadm pause-sync`."
617 msgstr ""
618 "indexterm:[replication, state, PausedSyncS]本地节点是正在进行的同步的源,但同步当前已暂停。这可能是由于依赖于另一个同步进程的完"
619 "成,或者是由于同步已被 `drbdadm pause sync` 手动中断。"
620
621 #. type: Block title
622 #, no-wrap
623 msgid "_PausedSyncT_"
624 msgstr "_PausedSyncT_"
625
626 #. type: Plain text
627 msgid ""
628 "indexterm:[replication state, PausedSyncT]The local node is the target of an ongoing synchronization, but synchronization is "
629 "currently paused. This may be due to a dependency on the completion of another synchronization process, or due to synchronization "
630 "having been manually interrupted by `drbdadm pause-sync`."
631 msgstr ""
632 "indexterm:[replication state, PausedSyncT]本地节点是正在进行的同步的目标,但同步当前已暂停。这可能是由于依赖于另一个同步进程的完"
633 "成,或者是由于同步已被 `drbdadm pause sync` 手动中断。"
634
635 #. type: Block title
636 #, no-wrap
637 msgid "_VerifyS_"
638 msgstr "_VerifyS_"
639
640 #. type: Plain text
641 msgid ""
642 "indexterm:[replication state, VerifyS]On-line device verification is currently running, with the local node being the source of "
643 "verification."
644 msgstr "indexterm:[replication state, VerifyS]联机设备验证当前正在运行,本地节点是验证源。"
645
646 #. type: Block title
647 #, no-wrap
648 msgid "_VerifyT_"
649 msgstr "_VerifyT_"
650
651 #. type: Plain text
652 msgid ""
653 "indexterm:[replication state, VerifyT]On-line device verification is currently running, with the local node being the target of "
654 "verification."
655 msgstr "indexterm:[replicateion state, VerifyT]联机设备验证当前正在运行,本地节点是验证的目标。"
656
657 #. type: Block title
658 #, no-wrap
659 msgid "_Ahead_"
660 msgstr "_Ahead_"
661
662 #. type: Plain text
663 msgid ""
664 "indexterm:[replication state, Ahead]Data replication was suspended, since the link can not cope with the load. This state is "
665 "enabled by the configuration `on-congestion` optione (see <<s-configure-congestion-policy>>)."
666 msgstr ""
667 "indexterm:[replication state, Ahead]数据复制被挂起,因为链接无法处理负载。此状态"
668 "因节点上的配置 `on-congestion` 选项启用 (参考 <<s-configure-congestion-policy>>)."
669
670 #. type: Block title
671 #, no-wrap
672 msgid "_Behind_"
673 msgstr "_Behind_"
674
675 #. type: Plain text
676 msgid ""
677 "indexterm:[replication state, Behind]Data replication was suspended by the peer, since the link can not cope with the load. This "
678 "state is enabled by the configuration `on-congestion` option on the peer node (see <<s-configure-congestion-policy>>)."
679 msgstr ""
680 "indexterm:[replication state, Behind]数据复制被对等方挂起,因为链接无法处理负载。此状态由对等节点上的配置 `on-congestion` 选项启用"
681 "(请参见<<s-configure-congestion-policy>>)。"
682
683 #. type: Title ====
684 #, no-wrap
685 msgid "Resource roles"
686 msgstr "资源角色"
687
688 #. type: Plain text
689 msgid "indexterm:[resource]A resource's role can be observed by issuing the indexterm:[drbdadm, role]`drbdadm role` command:"
690 msgstr "indexterm:[resource]可以通过调用indexterm:[drbdadm, role] `drbdadm role` 命令来观察资源的角色:"
691
692 #. type: delimited block -
693 #, no-wrap
694 msgid ""
695 "# drbdadm role <resource>\n"
696 "Primary\n"
697 msgstr ""
698 "# drbdadm role <resource>\n"
699 "Primary\n"
700
701 #. type: Plain text
702 msgid "You may see one of the following resource roles:"
703 msgstr "您可以看到以下资源角色之一:"
704
705 #. type: Block title
706 #, no-wrap
707 msgid "_Primary_"
708 msgstr "_Primary_"
709
710 #. type: Plain text
711 msgid ""
712 "indexterm:[role, Primary]The resource is currently in the primary role, and may be read from and written to. This role only "
713 "occurs on one of the two nodes, unless <<s-dual-primary-mode,dual-primary mode>> is enabled."
714 msgstr ""
715 "indexterm:[role, Primary]资源当前处于主角色中,可以读取和写入。此角色仅在两个节点中的一个节点上发生,除非启用了<<s-dual-primary-"
716 "mode,dual-primary mode>>。"
717
718 #. type: Block title
719 #, no-wrap
720 msgid "_Secondary_"
721 msgstr "_Secondary_"
722
723 #. type: Plain text
724 msgid ""
725 "indexterm:[role, Secondary]The resource is currently in the secondary role. It normally receives updates from its peer (unless "
726 "running in disconnected mode), but may neither be read from nor written to. This role may occur on one or both nodes."
727 msgstr ""
728 "indexterm:[role, Secondary]资源当前处于辅助角色中。它通常从其对等方接收更新(除非在断开连接模式下运行),但既不能读取也不能写入。"
729 "此角色可能出现在一个或两个节点上。"
730
731 #. type: Block title
732 #, no-wrap
733 msgid "_Unknown_"
734 msgstr "_Unknown_"
735
736 #. type: Plain text
737 msgid ""
738 "indexterm:[role, Unknown]The resource's role is currently unknown. The local resource role never has this status. It is only "
739 "displayed for the peer's resource role, and only in disconnected mode."
740 msgstr ""
741 "indexterm:[role, Unknown]资源的角色当前未知。本地资源角色从未具有此状态。它仅为对等方的资源角色显示,并且仅在断开连接模式下显示。"
742
743 #. type: Title ====
744 #, no-wrap
745 msgid "Disk states"
746 msgstr "磁盘状态"
747
748 #. type: Plain text
749 msgid "A resource's disk state can be observed either by issuing the `drbdadm dstate` command:"
750 msgstr "可以通过调用 `drbdadm dstate` 命令来观察资源的磁盘状态:"
751
752 #. type: delimited block -
753 #, no-wrap
754 msgid ""
755 "# drbdadm dstate <resource>\n"
756 "UpToDate\n"
757 msgstr ""
758 "# drbdadm dstate <resource>\n"
759 "UpToDate\n"
760
761 #. type: Plain text
762 msgid "The disk state may be one of the following:"
763 msgstr "磁盘状态可以是以下之一:"
764
765 #. type: Block title
766 #, no-wrap
767 msgid "_Diskless_"
768 msgstr "_Diskless_"
769
770 #. type: Plain text
771 msgid ""
772 "indexterm:[disk state, Diskless]No local block device has been assigned to the DRBD driver. This may mean that the resource has "
773 "never attached to its backing device, that it has been manually detached using `drbdadm detach`, or that it automatically "
774 "detached after a lower-level I/O error."
775 msgstr ""
776 "indexterm:[disk state, Diskless]没有为DRBD驱动程序分配本地块设备。这可能意味着资源从未连接到其备份设备,它已使用 `drbdadm detach` 手"
777 "动分离,或者在发生较低级别的I/O错误后自动分离。"
778
779 #. type: Block title
780 #, no-wrap
781 msgid "_Attaching_"
782 msgstr "_Attaching_"
783
784 #. type: Plain text
785 msgid "indexterm:[disk state, Attaching]Transient state while reading meta data."
786 msgstr "indexterm:[disk state, Attaching]读取元数据时的临时状态。"
787
788 #. type: Block title
789 #, no-wrap
790 msgid "_Detaching_"
791 msgstr "_Detaching_"
792
793 #. type: Plain text
794 msgid "indexterm:[disk state, Detaching]Transient state while detaching and waiting for ongoing IOs to complete."
795 msgstr "indexterm:[disk state, Detaching]在分离并等待正在进行的IOs完成时的临时状态。"
796
797 #. type: Block title
798 #, no-wrap
799 msgid "_Failed_"
800 msgstr "_Failed_"
801
802 #. type: Plain text
803 msgid ""
804 "indexterm:[disk state, Failed]Transient state following an I/O failure report by the local block device. Next state: _Diskless_."
805 msgstr "indexterm:[disk state, Failed]本地块设备报告I/O失败后的瞬态。下一个状态:_Diskless_。"
806
807 #. type: Block title
808 #, no-wrap
809 msgid "_Negotiating_"
810 msgstr "_Negotiating_"
811
812 #. type: Plain text
813 msgid "indexterm:[disk state, Negotiating]Transient state when an _Attach_ is carried out on an already-__Connected__ DRBD device."
814 msgstr "indexterm:[disk state, Negotiating]在 已经__Connected__ 的DRBD设备上执行附加操作时的瞬态。"
815
816 #. type: Block title
817 #, no-wrap
818 msgid "_Inconsistent_"
819 msgstr "_Inconsistent_"
820
821 #. type: Plain text
822 msgid ""
823 "indexterm:[disk state, Inconsistent]The data is inconsistent. This status occurs immediately upon creation of a new resource, on "
824 "both nodes (before the initial full sync). Also, this status is found in one node (the synchronization target) during "
825 "synchronization."
826 msgstr ""
827 "indexterm:[disk state, Inconsistent]数据不一致。在两个节点上(在初始完全同步之前)创建新资源时立即出现此状态。此外,在同步期间,在"
828 "一个节点(同步目标)中可以找到此状态。"
829
830 #. type: Block title
831 #, no-wrap
832 msgid "_Outdated_"
833 msgstr "_Outdated_"
834
835 #. type: Plain text
836 msgid "indexterm:[disk state, Outdated]Resource data is consistent, but <<s-outdate,outdated>>."
837 msgstr "indexterm:[disk state, Outdated]资源数据一致,但<<s-outdate,outdated>>。"
838
839 #. type: Block title
840 #, no-wrap
841 msgid "_DUnknown_"
842 msgstr "_DUnknown_"
843
844 #. type: Plain text
845 msgid "indexterm:[disk state, DUnknown]This state is used for the peer disk if no network connection is available."
846 msgstr "indexterm:[disk state, DUnknown]如果没有可用的网络连接,则此状态用于对等磁盘。"
847
848 #. type: Block title
849 #, no-wrap
850 msgid "_Consistent_"
851 msgstr "_Consistent_"
852
853 #. type: Plain text
854 msgid ""
855 "indexterm:[disk state, Consistent]Consistent data of a node without connection. When the connection is established, it is decided "
856 "whether the data is _UpToDate_ or _Outdated_."
857 msgstr "indexterm:[disk state, Consistent]没有连接的节点的一致数据。建立连接后,决定数据是 _UpToDate_ 还是 _Outdated_。"
858
859 #. type: Block title
860 #, no-wrap
861 msgid "_UpToDate_"
862 msgstr "_UpToDate_"
863
864 #. type: Plain text
865 msgid "indexterm:[disk state, UpToDate]Consistent, up-to-date state of the data. This is the normal state."
866 msgstr "indexterm:[disk state, UpToDate_]数据的一致、最新状态。这是正常状态。"
867
868 #. type: Title ====
869 #, no-wrap
870 msgid "Connection information data"
871 msgstr "连接信息数据"
872
873 #. type: Block title
874 #, no-wrap
875 msgid "_local_"
876 msgstr "_local_"
877
878 #. type: Plain text
879 msgid "Shows the network family, the local address and port that is used to accept connections from the peer."
880 msgstr "显示网络协议栈、用于接受来自对等方的连接的本地地址和端口。"
881
882 #. type: Block title
883 #, no-wrap
884 msgid "_peer_"
885 msgstr "_peer_"
886
887 #. type: Plain text
888 msgid "Shows the network family, the peer address and port that is used to connect."
889 msgstr "显示网络协议栈、对等方节点地址和用于连接的端口。"
890
891 #. type: Block title
892 #, no-wrap
893 msgid "_congested_"
894 msgstr "_congested_"
895
896 #. type: Plain text
897 msgid "This flag tells whether the TCP send buffer of the data connection is more than 80% filled."
898 msgstr "此标志指示数据连接的TCP发送缓冲区是否已填充80%以上。"
899
900 #. type: Title ====
901 #, no-wrap
902 msgid "Performance indicators"
903 msgstr "性能指标"
904
905 #. type: Plain text
906 msgid "indexterm:[performance indicators] One line of ``drbdadm status``-output includes the following counters and gauges:"
907 msgstr "indexterm:[performance indicators]一行 `drbdadm status` - 输出包括以下计数器和仪表:"
908
909 #. type: Block title
910 #, no-wrap
911 msgid "_send_ (network send)"
912 msgstr "_send_ (network send)"
913
914 #. type: Plain text
915 msgid "Volume of net data sent to the partner via the network connection; in Kibyte."
916 msgstr "通过网络连接发送给伙伴的网络数据量;单位为千字节。"
917
918 #. type: Block title
919 #, no-wrap
920 msgid "_receive_ (network receive)"
921 msgstr "_receive_ (network receive)"
922
923 #. type: Plain text
924 msgid "Volume of net data received by the partner via the network connection; in Kibyte."
925 msgstr "伙伴通过网络连接接收的网络数据量;单位为千字节。"
926
927 #. type: Block title
928 #, no-wrap
929 msgid "_read_ (disk write)"
930 msgstr "_read_ (disk write)"
931
932 #. type: Plain text
933 msgid "Net data written on local hard disk; in Kibyte."
934 msgstr "写在本地硬盘上的网络数据;以千字节为单位。"
935
936 #. type: Block title
937 #, no-wrap
938 msgid "_written_ (disk read)"
939 msgstr "_written_ (disk read)"
940
941 #. type: Plain text
942 msgid "Net data read from local hard disk; in Kibyte."
943 msgstr "从本地硬盘读取的网络数据;单位为千字节。"
944
945 #. type: Block title
946 #, no-wrap
947 msgid "_al-writes_ (activity log)"
948 msgstr "_al-writes_ (activity log)"
949
950 #. type: Plain text
951 msgid "Number of updates of the activity log area of the meta data."
952 msgstr "元数据活动日志区域的更新次数。"
953
954 #. type: Block title
955 #, no-wrap
956 msgid "_bm-writes_ (bit map)"
957 msgstr "_bm-writes_ (bit map)"
958
959 #. type: Plain text
960 msgid "Number of updates of the bitmap area of the meta data."
961 msgstr "元数据位图区域的更新次数。"
962
963 #. type: Block title
964 #, no-wrap
965 msgid "_lower-pending_ (local count)"
966 msgstr "_lower-pending_ (local count)"
967
968 #. type: Plain text
969 msgid "Number of open requests to the local I/O sub-system issued by DRBD."
970 msgstr "DRBD向本地I/O子系统发出的打开请求数。"
971
972 #. type: Block title
973 #, no-wrap
974 msgid "_pending_"
975 msgstr "_pending_"
976
977 #. type: Plain text
978 msgid "Number of requests sent to the partner, but that have not yet been answered by the latter."
979 msgstr "发送给合作伙伴但尚未由后者应答的请求数。"
980
981 #. type: Block title
982 #, no-wrap
983 msgid "_unacked_ (unacknowledged)"
984 msgstr "_unacked_ (unacknowledged)"
985
986 #. type: Plain text
987 msgid "Number of requests received by the partner via the network connection, but that have not yet been answered."
988 msgstr "伙伴通过网络连接接收但尚未应答的请求数。"
989
990 #. type: Block title
991 #, no-wrap
992 msgid "_upper-pending_ (application pending)"
993 msgstr "_upper-pending_ (application pending)"
994
995 #. type: Plain text
996 msgid "Number of block I/O requests forwarded to DRBD, but not yet answered by DRBD."
997 msgstr "转发给DRBD但尚未由DRBD应答的块I/O请求数。"
998
999 #. type: Block title
1000 #, no-wrap
1001 msgid "_write-ordering_ (write order)"
1002 msgstr "_write-ordering_ (write order)"
1003
1004 #. type: Plain text
1005 msgid "Currently used write ordering method: __b__(barrier), __f__(flush), __d__(drain) or __n__(none)."
1006 msgstr "当前使用的写排序方法__b__(barrier), __f__(flush), __d__(drain) 或者 __n__(none)."
1007
1008 #. type: Block title
1009 #, no-wrap
1010 msgid "_out-of-sync_"
1011 msgstr "_out-of-sync_"
1012
1013 #. type: Plain text
1014 msgid "indexterm:[out-of-sync]indexterm:[oos]Amount of storage currently out of sync; in Kibibytes."
1015 msgstr "indexterm:[out-of-sync]indexterm:[oos]当前不同步的存储量;单位为千字节。"
1016
1017 #. type: Block title
1018 #, no-wrap
1019 msgid "_resync-suspended_"
1020 msgstr "_resync-suspended_"
1021
1022 #. type: Plain text
1023 msgid "Whether the resynchronization is currently suspended or not. Possible values are _no_, _user_, _peer_, _dependency_."
1024 msgstr "重新同步是否当前挂起。可能的值是: _no_, _user_, _peer_, _dependency_."
1025
1026 #. type: Block title
1027 #, no-wrap
1028 msgid "_blocked_"
1029 msgstr "_blocked_"
1030
1031 #. type: Plain text
1032 msgid "indexterm:[blocked]Shows local I/O congestion."
1033 msgstr "indexterm:[blocked]显示本地I/O拥塞。"
1034
1035 #. type: Plain text
1036 msgid "_no_: No congestion."
1037 msgstr "_no_: No congestion."
1038
1039 #. type: Plain text
1040 msgid "_upper_: I/O _above_ the DRBD device is blocked, i.e. to the filesystem. Typical causes are"
1041 msgstr "_上面的_ I/O设备被阻塞,即文件系统。典型的原因是"
1042
1043 #. type: Plain text
1044 msgid "I/O suspension by the administrator, see the `suspend-io` command in `drbdadm`."
1045 msgstr "由管理员暂停I/O,请参阅 `drbdadm` 中的 `suspend-io` 命令。"
1046
1047 #. type: Plain text
1048 msgid "transient blocks, e.g. during attach/detach"
1049 msgstr "transient blocks, e.g. during attach/detach"
1050
1051 #. type: Plain text
1052 msgid "buffers depleted, see <<p-performance>>"
1053 msgstr "缓冲区耗尽,请参见<<p-performance>>"
1054
1055 #. type: Plain text
1056 msgid "Waiting for bitmap IO"
1057 msgstr "Waiting for bitmap IO"
1058
1059 #. type: Plain text
1060 msgid "_lower_: Backing device is congested."
1061 msgstr "_lower_: Backing device is congested."
1062
1063 #. type: Plain text
1064 msgid "It's possible to see a value of _upper,lower_, too."
1065 msgstr "也有可能看到一个值 _upper,lower_。"
1066
1067 #. type: Title ===
1068 #, no-wrap
1069 msgid "Enabling and disabling resources"
1070 msgstr "启用和禁用资源"
1071
1072 #. type: Title ====
1073 #, no-wrap
1074 msgid "Enabling resources"
1075 msgstr "使能资源"
1076
1077 #. type: Plain text
1078 msgid "indexterm:[resource]Normally, all configured DRBD resources are automatically enabled"
1079 msgstr "indexterm:[resource]通常,所有配置的DRBD资源都会自动启用"
1080
1081 #. type: Plain text
1082 msgid "by a cluster resource management application at its discretion, based on your cluster configuration, or"
1083 msgstr "由群集资源管理应用程序根据您的群集配置自行决定,或"
1084
1085 #. type: Plain text
1086 msgid "by the `/etc/init.d/drbd` init script on system startup."
1087 msgstr "在系统启动时通过 `/etc/init.d/drbd` init脚本。"
1088
1089 #. type: Plain text
1090 msgid "If, however, you need to enable resources manually for any reason, you may do so by issuing the command"
1091 msgstr "但是,如果出于任何原因需要手动启用资源,可以通过调用命令"
1092
1093 #. type: delimited block -
1094 #, no-wrap
1095 msgid "# drbdadm up <resource>\n"
1096 msgstr "# drbdadm up <resource>\n"
1097
1098 #. type: Plain text
1099 msgid ""
1100 "As always, you may use the keyword `all` instead of a specific resource name if you want to enable all resources configured in `/"
1101 "etc/drbd.conf` at once."
1102 msgstr "与往常一样,如果要同时启用在 `/etc/drbd.conf` 中配置的所有资源,可以使用关键字 `all` 而不是特定的资源名。"
1103
1104 #. type: Title ====
1105 #, no-wrap
1106 msgid "Disabling resources"
1107 msgstr "禁用资源"
1108
1109 #. type: Plain text
1110 msgid "indexterm:[resource]You may temporarily disable specific resources by issuing the command"
1111 msgstr "indexterm:[resource]您可以通过调用命令暂时禁用特定资源"
1112
1113 #. type: delimited block -
1114 #, no-wrap
1115 msgid "# drbdadm down <resource>\n"
1116 msgstr "# drbdadm down <resource>\n"
1117
1118 #. type: Plain text
1119 msgid ""
1120 "Here, too, you may use the keyword `all` in place of a resource name if you wish to temporarily disable all resources listed in `/"
1121 "etc/drbd.conf` at once."
1122 msgstr "在这里,如果您希望一次临时禁用 `/etc/drbd.conf` 中列出的所有资源,也可以使用关键字 `all` 代替资源名。"
1123
1124 #. type: Title ===
1125 #, no-wrap
1126 msgid "Reconfiguring resources"
1127 msgstr "重新配置资源"
1128
1129 #. type: Plain text
1130 msgid "indexterm:[resource]DRBD allows you to reconfigure resources while they are operational. To that end,"
1131 msgstr "indexterm:[resource]DRBD允许您在资源运行时重新配置它们。包括,"
1132
1133 #. type: Plain text
1134 msgid "make any necessary changes to the resource configuration in `/etc/drbd.conf`,"
1135 msgstr "对 `/etc/drbd.conf` 中的资源配置需要进行任何必要的更改,"
1136
1137 #. type: Plain text
1138 msgid "synchronize your `/etc/drbd.conf` file between both nodes,"
1139 msgstr "在两个节点之间同步 `/etc/drbd.conf` 文件,"
1140
1141 #. type: Plain text
1142 msgid "issue the indexterm:[drbdadm, adjust]`drbdadm adjust <resource>` command on both nodes."
1143 msgstr "在两个节点上发出indexterm:[drbdadm,adjust] `drbdadm adjust<resource>` 命令。"
1144
1145 #. type: Plain text
1146 msgid ""
1147 "`drbdadm adjust` then hands off to `drbdsetup` to make the necessary adjustments to the configuration. As always, you are able to "
1148 "review the pending `drbdsetup` invocations by running `drbdadm` with the `-d` (dry-run) option."
1149 msgstr ""
1150 "`drbdadm adjust` 然后切换到 `drbdsetup` 对配置进行必要的调整。与往常一样,您可以通过使用 `-d` (dry-run)选项运行 `drbdadm` 来查看挂起的"
1151 " `drbdsetup` 调用。"
1152
1153 #. type: Plain text
1154 msgid ""
1155 "When making changes to the `common` section in `/etc/drbd.conf`, you can adjust the configuration for all resources in one run, "
1156 "by issuing `drbdadm adjust all`."
1157 msgstr "对 `/etc/drbd.conf` 中的 `common` 部分进行更改时,可以通过发出 `drbdadm adjust all` 来调整一次运行中所有资源的配置。"
1158
1159 #. type: Title ===
1160 #, no-wrap
1161 msgid "Promoting and demoting resources"
1162 msgstr "提升和降级资源"
1163
1164 #. type: Plain text
1165 msgid ""
1166 "indexterm:[resource]Manually switching a <<s-resource-roles,resource's role>> from secondary to primary (promotion) or vice versa "
1167 "(demotion) is done using one of the following commands:"
1168 msgstr ""
1169 "indexterm:[resource]使用以下命令之一手动将a<<s-resource-roles,resource's role>>从次要角色切换到主要角色(提升)或反之亦然(降"
1170 "级):"
1171
1172 #. type: delimited block -
1173 #, no-wrap
1174 msgid ""
1175 "# drbdadm primary <resource>\n"
1176 "# drbdadm secondary <resource>\n"
1177 msgstr ""
1178 "# drbdadm primary <resource>\n"
1179 "# drbdadm secondary <resource>\n"
1180
1181 #. type: Plain text
1182 msgid ""
1183 "In <<s-single-primary-mode,single-primary mode>> (DRBD's default), any resource can be in the primary role on only one node at "
1184 "any given time while the <<s-connection-states,connection state>> is _Connected_. Thus, issuing `drbdadm primary <resource>` on "
1185 "one node while the specified resource is still in the primary role on another node will result in an error."
1186 msgstr ""
1187 "在<<s-single-primary-mode,single-primary mode>>(DRBD的默认设置)中,任何资源在任何给定时间只能在一个节点上处于主要角色,而<<s-"
1188 "connection-states,connection state>>是连接的。因此,在一个节点上发出 `drbdadm primary<resource>` ,而该指定的资源是在另一个节点上的"
1189 "primary角色, 将导致错误。"
1190
1191 #. type: Plain text
1192 msgid ""
1193 "A resource configured to allow <<s-dual-primary-mode,dual-primary mode>> can be switched to the primary role on two nodes; this "
1194 "is e.g. needed for online migration of virtual machines."
1195 msgstr "配置为允许<<s-dual-primary-mode,dual-primary mode>>的资源可以切换到两个节点上的主要角色;这是虚拟机在线迁移所必需的。"
1196
1197 #. type: Title ===
1198 #, no-wrap
1199 msgid "Basic Manual Fail-over"
1200 msgstr "基本手动故障切换"
1201
1202 #. type: Plain text
1203 msgid ""
1204 "If not using Pacemaker and looking to handle fail-overs manually in a passive/active configuration, the process is as follows."
1205 msgstr "如果不使用Pacemaker并希望在被动/主动配置中手动处理故障转移,则过程如下。"
1206
1207 #. type: Plain text
1208 msgid ""
1209 "On the current primary node stop any applications or services using the DRBD device, unmount the DRBD device, and demote the "
1210 "resource to secondary."
1211 msgstr "在当前主节点上,停止使用DRBD设备的任何应用程序或服务,卸载DRBD设备,并将资源降级为次要资源。"
1212
1213 #. type: delimited block -
1214 #, no-wrap
1215 msgid ""
1216 "# umount /dev/drbd/by-res/<resource>/<vol-nr>\n"
1217 "# drbdadm secondary <resource>\n"
1218 msgstr ""
1219 "# umount /dev/drbd/by-res/<resource>/<vol-nr>\n"
1220 "# drbdadm secondary <resource>\n"
1221
1222 #. type: Plain text
1223 msgid "Now on the node we wish to make primary promote the resource and mount the device."
1224 msgstr "现在登录到想提升为primary的节点上,升级资源并装载设备。"
1225
1226 #. type: delimited block -
1227 #, no-wrap
1228 msgid ""
1229 "# drbdadm primary <resource>\n"
1230 "# mount /dev/drbd/by-res/<resource>/<vol-nr> <mountpoint>\n"
1231 msgstr ""
1232 "# drbdadm primary <resource>\n"
1233 "# mount /dev/drbd/by-res/<resource>/<vol-nr> <mountpoint>\n"
1234
1235 #. type: Plain text
1236 msgid ""
1237 "If you're using the `auto-promote` feature, you don't need to change the roles (_Primary_/_Secondary_) manually; only stopping of "
1238 "the services and umounting, respectively mounting, is necessary."
1239 msgstr "如果您使用的是 `自动升级` 功能,则不需要手动更改角色( _Primary_/_Secondary_ );只需要停止服务和及调用mounting/umounting。"
1240
1241 #. type: Title ===
1242 #, no-wrap
1243 msgid "Upgrading DRBD"
1244 msgstr "升级DRBD"
1245
1246 #. type: Plain text
1247 msgid ""
1248 "Upgrading DRBD is a fairly simple process. This section will cover the process of upgrading from 8.4.x to 9.0.x in great detail; "
1249 "for within-9 upgrades it gets to be much easier, see the short version <<s-upgrade-within-9,below>>."
1250 msgstr ""
1251 "升级DRBD是一个相当简单的过程。本节将详细介绍从8.4.x升级到9.0.x的过程;对于9版本内升级,它变得更加容易,请参见下面的简短版本<<s-"
1252 "upgrade-within-9>>。"
1253
1254 #. type: Title ====
1255 #, no-wrap
1256 msgid "General overview"
1257 msgstr "概述"
1258
1259 #. type: Plain text
1260 msgid "The general process for upgrading 8.4 to 9.0 is as follows:"
1261 msgstr "将8.4升级到9.0的一般过程如下:"
1262
1263 #. type: Plain text
1264 msgid "Configure the <<s-updating-your-repo,new repositories>> (if using packages from LINBIT)"
1265 msgstr "配置<<s-updating-your-repo,新仓库>>(如果使用来自LINBIT的包)"
1266
1267 #. type: Plain text
1268 msgid "Make sure that the current situation <<s-upgrade-check,is okay>>"
1269 msgstr "确保当前情况<<s-upgrade-check, 检查良好>>"
1270
1271 #. type: Plain text
1272 msgid "<<s-upgrade-pausing-the-cluster,Pause>> any cluster manager"
1273 msgstr "<<s-upgrade-pausing-the-cluster,Pause>>任何群集管理器"
1274
1275 #. type: Plain text
1276 msgid "Get <<s-Upgrading-the-packages,new versions>> installed"
1277 msgstr "安装<<s-Upgrading-the-packages,新版本>>"
1278
1279 #. type: Plain text
1280 msgid ""
1281 "If wanting to move to more than 2 nodes, then you'll need to resize the lower-level storage to provide room for the additional "
1282 "meta-data; this topic is discussed in the <<ch-lvm,LVM Chapter>>."
1283 msgstr "如果要移动到2个以上的节点,则需要调整较低级别的存储空间,以便为其他元数据提供空间;本主题将在<<ch-lvm,LVM Chapter>>中讨论。"
1284
1285 #. type: Plain text
1286 msgid "Deconfigure resources, unload DRBD 8.4, and <<s-upgrade-reload-kernel-mod,load the v9 kernel module>>"
1287 msgstr "取消配置资源,卸载DRBD 8.4,然后<<s-upgrade-reload-kernel-mod,load the v9 kernel module>>"
1288
1289 #. type: Plain text
1290 msgid "<<s-upgrade-convert,Convert DRBD meta-data>> to format `v09`, perhaps changing the number of bitmaps in the same step"
1291 msgstr "<<s-upgrade-convert,Convert DRBD meta-data>>格式为 `v09` ,可能在同一步骤中需要更改位图的数量"
1292
1293 #. type: Plain text
1294 msgid "Take the DRBD <<s-upgrade-start-drbd,resources up>>, and be happy"
1295 msgstr "启动新版本DRBD<<s-upgrade-start-drbd,resources up>>"
1296
1297 #. type: Title ====
1298 #, no-wrap
1299 msgid "Updating your repository"
1300 msgstr "更新仓库"
1301
1302 #. type: Plain text
1303 msgid ""
1304 "Due to the number of changes between the 8.4 and 9.0 branches we have created separate repositories for each. Perform this "
1305 "repository update on both servers."
1306 msgstr "由于8.4和9.0分支之间的更改众多,我们为每个分支创建了单独的仓库。在两台服务器上执行此仓库更新。"
1307
1308 #. type: Title =====
1309 #, no-wrap
1310 msgid "RHEL/CentOS systems"
1311 msgstr "RHEL/CentOS系统"
1312
1313 #. type: Plain text
1314 msgid "Edit your `/etc/yum.repos.d/linbit.repo` file to reflect the following changes."
1315 msgstr "编辑 `/etc/yum.repos.d/linbit.repo` 文件。"
1316
1317 #. type: delimited block -
1318 #, no-wrap
1319 msgid ""
1320 "[drbd-9.0]\n"
1321 "name=DRBD 9.0\n"
1322 "baseurl=http://packages.linbit.com/<hash>/yum/rhel7/drbd-9.0/<arch>\n"
1323 "gpgcheck=0\n"
1324 msgstr ""
1325 "[drbd-9.0]\n"
1326 "name=DRBD 9.0\n"
1327 "baseurl=http://packages.linbit.com/<hash>/yum/rhel7/drbd-9.0/<arch>\n"
1328 "gpgcheck=0\n"
1329
1330 #. type: Plain text
1331 msgid "You will have to populate the <hash> and <arch> variables. The <hash> is provided by LINBIT support services."
1332 msgstr "必须填充<hash>和<arch>变量。<hash>由LINBIT支持服务提供。"
1333
1334 #. type: Title =====
1335 #, no-wrap
1336 msgid "Debian/Ubuntu systems"
1337 msgstr "Debian/Ubuntu系统"
1338
1339 #. type: Plain text
1340 msgid "Edit `/etc/apt/sources.list` (or a file in `/etc/apt/sources.d/`) to reflect the following changes."
1341 msgstr "编辑 `/etc/apt/sources.list` (或 `/etc/apt/sources.d/` 中的文件)加入以下更改。"
1342
1343 #. type: delimited block -
1344 #, no-wrap
1345 msgid "deb http://packages.linbit.com/<hash>/ stretch drbd-9.0\n"
1346 msgstr "deb http://packages.linbit.com/<hash>/ stretch drbd-9.0\n"
1347
1348 #. type: Plain text
1349 msgid "In case you're not using the `stretch` release, but some other, you'll need to change that line."
1350 msgstr "如果您不使用 `stretch` 版本,而是使用其他版本,则需要更改到对应的版本名称。"
1351
1352 #. type: Plain text
1353 msgid "You will have to populate the `<hash>` variable. The `<hash>` is provided by LINBIT support services."
1354 msgstr "您必须填充 `<hash>` 变量。`<hash>` 由LINBIT支持服务提供。"
1355
1356 #. type: Plain text
1357 msgid "Next you will want to add the DRBD signing key to your trusted keys."
1358 msgstr "接下来,您需要将DRBD签名密钥添加到您的受信任密钥中。"
1359
1360 #. type: delimited block -
1361 #, no-wrap
1362 msgid ""
1363 "# gpg --keyserver subkeys.pgp.net --recv-keys 0x282B6E23\n"
1364 "# gpg --export -a 282B6E23 | apt-key add -\n"
1365 msgstr ""
1366 "# gpg --keyserver subkeys.pgp.net --recv-keys 0x282B6E23\n"
1367 "# gpg --export -a 282B6E23 | apt-key add -\n"
1368
1369 #. type: Plain text
1370 msgid "Lastly perform an `apt update` so Debian recognizes the updated repository."
1371 msgstr "最后执行 `apt update` ,以便Debian识别更新的存储库。"
1372
1373 #. type: delimited block -
1374 #, no-wrap
1375 msgid "# apt update\n"
1376 msgstr "# apt update\n"
1377
1378 #. type: Title ====
1379 #, no-wrap
1380 msgid "Checking the DRBD state"
1381 msgstr "检查DRBD状态"
1382
1383 #. type: Plain text
1384 msgid ""
1385 "Before you begin make sure your resources are in sync. The output of `cat /proc/drbd` (which is only available _before_ 9.0) "
1386 "should show _UpToDate/UpToDate_."
1387 msgstr "在开始之前,请确保资源同步。`cat/proc/drbd` 的输出(仅在9.0之前可用)应显示 _UpToDate/UpToDate_ 。"
1388
1389 #. type: delimited block -
1390 #, no-wrap
1391 msgid "bob# cat /proc/drbd\n"
1392 msgstr "bob# cat /proc/drbd\n"
1393
1394 #. type: delimited block -
1395 #, no-wrap
1396 msgid ""
1397 "version: 8.4.9-1 (api:1/proto:86-101)\n"
1398 "GIT-hash: e081fb0570183db40caa29b26cb8ee907e9a7db3 build by linbit@buildsystem, 2016-11-18 14:49:21\n"
1399 msgstr ""
1400 "version: 8.4.9-1 (api:1/proto:86-101)\n"
1401 "GIT-hash: e081fb0570183db40caa29b26cb8ee907e9a7db3 build by linbit@buildsystem, 2016-11-18 14:49:21\n"
1402
1403 #. type: delimited block -
1404 #, no-wrap
1405 msgid ""
1406 " 0: cs:Connected ro:Secondary/Secondary ds:UpToDate/UpToDate C r-----\n"
1407 " ns:0 nr:211852 dw:211852 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0\n"
1408 msgstr ""
1409 " 0: cs:Connected ro:Secondary/Secondary ds:UpToDate/UpToDate C r-----\n"
1410 " ns:0 nr:211852 dw:211852 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:d oos:0\n"
1411
1412 #. type: Title ====
1413 #, no-wrap
1414 msgid "Pausing the cluster"
1415 msgstr "暂停群集"
1416
1417 #. type: Plain text
1418 msgid ""
1419 "Now that you know the resources are in sync, start by upgrading the secondary node. This can be done manually or if you're using "
1420 "Pacemaker put the node in standby mode. Both processes are covered below. If you're running Pacemaker do not use the manual "
1421 "method."
1422 msgstr ""
1423 "既然您知道资源是同步的,就从升级辅助节点开始。这可以手动完成,或者如果您正在使用Pacemaker,请将节点置于待机模式。下面将介绍这两个"
1424 "过程。如果你正在运行Pacemaker,不要使用手动方法。"
1425
1426 #. type: Plain text
1427 msgid "Manual Method"
1428 msgstr "手动方法"
1429
1430 #. type: delimited block -
1431 #, no-wrap
1432 msgid "bob# /etc/init.d/drbd stop\n"
1433 msgstr "bob# /etc/init.d/drbd stop\n"
1434
1435 #. type: Plain text
1436 msgid "Pacemaker"
1437 msgstr "Pacemaker"
1438
1439 #. type: Plain text
1440 msgid "Put the secondary node into standby mode. In this example 'bob' is secondary."
1441 msgstr "将辅助节点置于待机模式。在本例中,`bob` 是辅助节点。"
1442
1443 #. type: delimited block -
1444 #, no-wrap
1445 msgid "bob# crm node standby bob\n"
1446 msgstr "bob# crm node standby bob\n"
1447
1448 #. type: Plain text
1449 msgid ""
1450 "You can watch the status of your cluster using `crm_mon -rf` or watch `cat /proc/drbd` until it shows _Unconfigured_ for your "
1451 "resources."
1452 msgstr "您可以使用 `crm-mon-rf` 或 `cat/proc/drbd` 监视群集的状态,直到它显示您的资源为 `未配置` 。"
1453
1454 #. type: Title ====
1455 #, no-wrap
1456 msgid "Upgrading the packages"
1457 msgstr "升级包"
1458
1459 #. type: Plain text
1460 msgid "Now update your packages with either yum or apt."
1461 msgstr "现在用yum或apt更新包。"
1462
1463 #. type: delimited block -
1464 #, no-wrap
1465 msgid "bob# yum upgrade\n"
1466 msgstr "bob# yum upgrade\n"
1467
1468 #. type: delimited block -
1469 #, no-wrap
1470 msgid "bob# apt upgrade\n"
1471 msgstr "bob# apt upgrade\n"
1472
1473 #. type: Plain text
1474 msgid ""
1475 "Once the upgrade is finished will now have the latest DRBD 9.0 kernel module and drbd-utils installed on your secondary node, "
1476 "'bob'."
1477 msgstr "升级完成后,将在次节点 `bob` 上安装最新的DRBD 9.0内核模块和DRBD实用程序。"
1478
1479 #. type: Plain text
1480 msgid "But the kernel module is not active yet."
1481 msgstr "但是内核模块还没有激活。"
1482
1483 #. type: Title ====
1484 #, no-wrap
1485 msgid "Loading the new Kernel module"
1486 msgstr "加载新的内核模块"
1487
1488 #. type: Plain text
1489 msgid "By now the DRBD module should not be in use anymore, so we unload it via"
1490 msgstr "现在旧的DRBD内核模块不应该再使用了,所以我们通过"
1491
1492 #. type: delimited block -
1493 #, no-wrap
1494 msgid "bob# rmmod drbd\n"
1495 msgstr "bob# rmmod drbd\n"
1496
1497 #. type: Plain text
1498 msgid ""
1499 "If there's a message like `ERROR: Module drbd is in use`, then not all resources have been correctly stopped yet. + Retry <<s-"
1500 "upgrading-drbd>>, and/or run the command `drbdadm down all` to find out which resources are still active."
1501 msgstr ""
1502 "如果出现类似 `ERROR:Module drbd is in use` (错误:模块drbd正在使用)的消息,则并非所有资源都已正确停止。+ 重试<<s-upgrading-"
1503 "drbd>>,和/或运行命令 `drbdadm down all` 以确定哪些资源仍处于活动状态。"
1504
1505 #. type: Plain text
1506 msgid "Typical issues that might prevent unloading are these:"
1507 msgstr "可能阻止卸载的典型问题有:"
1508
1509 #. type: Plain text
1510 msgid "NFS export on a DRBD-backed filesystem (see `exportfs -v` output)"
1511 msgstr "在DRBD支持的文件系统上有导出NFS的操作(参见 `exportfs -v` 输出)"
1512
1513 #. type: Plain text
1514 msgid "Filesystem still mounted - check `grep drbd /proc/mounts`"
1515 msgstr "文件系统仍在安装-检查 `grep drbd/proc/mounts` "
1516
1517 #. type: Plain text
1518 msgid "Loopback device active (`losetup -l`)"
1519 msgstr "Loopback 设备仍然处于活动状态( `losetup -l` )"
1520
1521 #. type: Plain text
1522 msgid "Device mapper using DRBD, directly or indirectly (`dmsetup ls --tree`)"
1523 msgstr "直接或间接使用DRBD的device mapper( `dmsetup ls --tree` )"
1524
1525 #. type: Plain text
1526 msgid "LVM with a DRBD-PV (`pvs`)"
1527 msgstr "有带DRBD-PV的LVM(`pvs`)"
1528
1529 #. type: Plain text
1530 msgid "Please note that this list isn't complete - these are just the most common examples."
1531 msgstr "请注意,这个列表并不完整 - 这些只是最常见的例子。"
1532
1533 #. type: Plain text
1534 msgid "Now we can load the new DRBD module:"
1535 msgstr "现在我们可以加载新的DRBD内核模块:"
1536
1537 #. type: delimited block -
1538 #, no-wrap
1539 msgid "bob# modprobe drbd\n"
1540 msgstr "bob# modprobe drbd\n"
1541
1542 #. type: Plain text
1543 msgid ""
1544 "Now you should check the contents of `/proc/drbd` and verify that the correct (new) version is loaded; if the installed packages "
1545 "is for the wrong kernel version, the `modprobe` would be successful, but you'd be left with the old version being active again."
1546 msgstr ""
1547 "现在您应该检查 `/proc/drbd` 的内容,并验证是否加载了正确的(新的)版本;如果安装的软件包的内核版本不正确,`modprobe` 也会成功,但旧版"
1548 "本将再次处于活动状态。"
1549
1550 #. type: Plain text
1551 msgid "The output of `cat /proc/drbd` should now show 9.0.x and look similar to this."
1552 msgstr "`cat /proc/drbd` 的输出现在应该显示为9.0.x,看起来与此类似。"
1553
1554 #. type: delimited block -
1555 #, no-wrap
1556 msgid ""
1557 "version: 9.0.0 (api:2/proto:86-110)\n"
1558 "GIT-hash: 768965a7f158d966bd3bd4ff1014af7b3d9ff10c build by root@bob, 2015-09-03 13:58:02\n"
1559 "Transports (api:10): tcp (1.0.0)\n"
1560 msgstr ""
1561 "version: 9.0.0 (api:2/proto:86-110)\n"
1562 "GIT-hash: 768965a7f158d966bd3bd4ff1014af7b3d9ff10c build by root@bob, 2015-09-03 13:58:02\n"
1563 "Transports (api:10): tcp (1.0.0)\n"
1564
1565 #. type: Plain text
1566 msgid "On the primary node, alice, 'cat /proc/drbd' will still show the prior version, until you upgrade it."
1567 msgstr "在主节点,alice上, `cat /proc/drbd` 将仍然显示先前的版本,直到您升级它。"
1568
1569 #. At this point the cluster is running two different versions of DRBD. While
1570 #. this
1571 #. is not recommended to be used for longer time spans, it is inevitable for
1572 #. the (short) upgrade period.
1573 #. Stop
1574 #. any service using DRBD and then DRBD on the primary node, alice, and
1575 #. promote
1576 #. 'bob'. Again this can be done either manually or via the Pacemaker shell.
1577 #. * Manually
1578 #. ----------------------------
1579 #. alice # umount /dev/drbd/by-res/r0
1580 #. alice # /etc/init.d/drbd stop
1581 #. bob # drbdadm primary r0
1582 #. bob # mount /dev/drbd/by-res/r0/0 /mnt/drbd
1583 #. ----------------------------
1584 #. Please note that the mount command now references '/0' which defines
1585 #. the volume number of a resource. See <<s-recent-changes-volumes>> for
1586 #. more information on the new volumes feature.
1587 #. * Pacemaker
1588 #. ----------------------------
1589 #. # crm node standby alice
1590 #. ----------------------------
1591 #. WARNING: This will interrupt running services by stopping them and
1592 #. migrating them to the secondary server, bob.
1593 #. At this point you can safely upgrade DRBD by using yum or apt.
1594 #. ----------------------------
1595 #. alice# yum upgrade
1596 #. ----------------------------
1597 #. ----------------------------
1598 #. alice# apt upgrade
1599 #. ----------------------------
1600 #. Once the upgrade is complete you will now have the latest version
1601 #. of DRBD on alice and can start DRBD.
1602 #. * Manually
1603 #. ----------------------------
1604 #. alice# /etc/init.d/drbd start
1605 #. ----------------------------
1606 #. * Pacemaker
1607 #. ----------------------------
1608 #. alice# crm node online alice
1609 #. ----------------------------
1610 #. NOTE: Services will still be located on bob and will remain there
1611 #. until you migrate them back.
1612 #. Both servers should now show the latest version of DRBD in a connected
1613 #. state.
1614 #. ----------------------------
1615 #. # cat /proc/drbd
1616 #. version: 9.0.0 (api:2/proto:86-110)
1617 #. GIT-hash: 768965a7f158d966bd3bd4ff1014af7b3d9ff10c build by root@bob,
1618 #. 2015-09-03 13:58:02
1619 #. Transports (api:10): tcp (1.0.0)
1620 #. # drbdsetup status
1621 #. r0 role:Secondary
1622 #. disk:UpToDate
1623 #. bob role:Secondary
1624 #. peer-disk:UpToDate
1625 #. ----------------------------
1626 #. type: Title ====
1627 #, no-wrap
1628 msgid "Migrating your configuration files"
1629 msgstr "迁移配置文件"
1630
1631 #. type: Plain text
1632 msgid ""
1633 "DRBD 9.0 is backward compatible with the 8.4 configuration files; however, some syntax has changed. See <<s-recent-changes-"
1634 "config>> for a full list of changes. In the meantime you can port your old configs fairly easily by using 'drbdadm dump all' "
1635 "command. This will output both a new global config followed by the new resource config files. Take this output and make changes "
1636 "accordingly."
1637 msgstr ""
1638 "DRBD 9.0与8.4配置文件向后兼容;但是,某些语法已更改。有关更改的完整列表,请参见<<s-recent-changes-config>>。同时,您可以使用"
1639 "`drbdadm dump all` 命令轻松移植旧配置。这将输出一个新的全局配置和一个新的资源配置文件。获取此输出并相应地进行更改。"
1640
1641 #. type: Title ====
1642 #, no-wrap
1643 msgid "Changing the meta-data"
1644 msgstr "更改元数据"
1645
1646 #. type: Plain text
1647 msgid ""
1648 "Now you need to convert the on-disk metadata to the new version; this is really easy, it's just running one command and "
1649 "acknowledging two questions."
1650 msgstr "现在您需要将磁盘上的元数据转换为新版本;这非常简单,只需运行一个命令并确认两个问题。"
1651
1652 #. type: Plain text
1653 msgid ""
1654 "If you want to change the number of nodes, you should already have increased the size of the lower level device, so that there is "
1655 "enough space to store the additional bitmaps; in that case, you'd run the command below with an additional argument `--max-"
1656 "peers=__<N>__`. When determining the number of (possible) peers please take setups like the <<s-drbd-client>> into account."
1657 msgstr ""
1658 "如果要更改节点数,您应该已经增加了底层设备的大小,以便有足够的空间存储增加的位图;在这种情况下,您将使用附加参数 `--max "
1659 "peers=__<N>__` 。当需要确定(可能的)节点个数时,请参考 <<s-drbd-client> 做相应的配置。"
1660
1661 #. type: Plain text
1662 msgid "Upgrading the DRBD metadata is as easy as running one command, and acknowledging the two questions:"
1663 msgstr "升级DRBD元数据只需运行一个命令并确认两个问题:"
1664
1665 #. type: delimited block -
1666 #, no-wrap
1667 msgid ""
1668 "# drbdadm create-md <resource>\n"
1669 "You want me to create a v09 style flexible-size internal meta data block.\n"
1670 "There appears to be a v08 flexible-size internal meta data block\n"
1671 "already in place on <disk> at byte offset <offset>\n"
1672 msgstr ""
1673 "# drbdadm create-md <resource>\n"
1674 "You want me to create a v09 style flexible-size internal meta data block.\n"
1675 "There appears to be a v08 flexible-size internal meta data block\n"
1676 "already in place on <disk> at byte offset <offset>\n"
1677
1678 #. type: delimited block -
1679 #, no-wrap
1680 msgid ""
1681 "Valid v08 meta-data found, convert to v09?\n"
1682 "[need to type 'yes' to confirm] yes\n"
1683 msgstr ""
1684 "Valid v08 meta-data found, convert to v09?\n"
1685 "[need to type 'yes' to confirm] yes\n"
1686
1687 #. type: delimited block -
1688 #, no-wrap
1689 msgid ""
1690 "md_offset <offsets...>\n"
1691 "al_offset <offsets...>\n"
1692 "bm_offset <offsets...>\n"
1693 msgstr ""
1694 "md_offset <offsets...>\n"
1695 "al_offset <offsets...>\n"
1696 "bm_offset <offsets...>\n"
1697
1698 #. type: delimited block -
1699 #, no-wrap
1700 msgid "Found some data\n"
1701 msgstr "Found some data\n"
1702
1703 #. type: delimited block -
1704 #, no-wrap
1705 msgid " ==> This might destroy existing data! <==\n"
1706 msgstr " ==> This might destroy existing data! <==\n"
1707
1708 #. type: delimited block -
1709 #, no-wrap
1710 msgid ""
1711 "Do you want to proceed?\n"
1712 "[need to type 'yes' to confirm] yes\n"
1713 msgstr ""
1714 "Do you want to proceed?\n"
1715 "[need to type 'yes' to confirm] yes\n"
1716
1717 #. type: delimited block -
1718 #, no-wrap
1719 msgid ""
1720 "Writing meta data...\n"
1721 "New drbd meta data block successfully created.\n"
1722 "success\n"
1723 msgstr ""
1724 "Writing meta data...\n"
1725 "New drbd meta data block successfully created.\n"
1726 "success\n"
1727
1728 #. type: Plain text
1729 msgid ""
1730 "Of course, you can pass `all` for the resource names, too; and if you feel really lucky, you can avoid the questions via a "
1731 "commandline like this here, too. (Yes, the order is important.)"
1732 msgstr ""
1733 "当然,您也可以传递 `all` 作为资源名;如果您感到自己是个幸运儿,也可以通过如下这样的命令行来避免在运行过程中回答问题。(注意,顺序很"
1734 "重要。)"
1735
1736 #. type: delimited block -
1737 #, no-wrap
1738 msgid "drbdadm -v --max-peers=<N> -- --force create-md <resources>\n"
1739 msgstr "drbdadm -v --max-peers=<N> -- --force create-md <resources>\n"
1740
1741 #. type: Title ====
1742 #, no-wrap
1743 msgid "Starting DRBD again"
1744 msgstr "重新启动DRBD"
1745
1746 #. type: Plain text
1747 msgid ""
1748 "Now, the only thing left to do is to get the DRBD devices up and running again - a simple `drbdadm up all` should do the trick."
1749 msgstr "现在,唯一要做的就是让DRBD设备重新启动并再次运行- 一个简单的命令 `drbdadm up all` 应该能做到这一点。"
1750
1751 #. type: Plain text
1752 msgid ""
1753 "Now, depending on whether you've got a cluster manager or keep track of your resources manually, there are two different ways "
1754 "again."
1755 msgstr "现在,根据您是否有集群管理器或手动跟踪资源,又有两种不同的方法。"
1756
1757 #. type: Plain text
1758 msgid "Manually"
1759 msgstr "手动"
1760
1761 #. type: delimited block -
1762 #, no-wrap
1763 msgid "bob# /etc/init.d/drbd start\n"
1764 msgstr "bob# /etc/init.d/drbd start\n"
1765
1766 #. type: delimited block -
1767 #, no-wrap
1768 msgid "# crm node online bob\n"
1769 msgstr "# crm node online bob\n"
1770
1771 #. type: Plain text
1772 msgid "This should make DRBD connect to the other node, and the resynchronization process will start."
1773 msgstr "这将使DRBD连接到另一个节点,并且重新同步过程将启动。"
1774
1775 #. type: Plain text
1776 msgid ""
1777 "When the two nodes are _UpToDate_ on all resources again, you can move your applications to the already upgraded node (here "
1778 "'bob'), and then follow the same steps on the cluster node still running 8.4."
1779 msgstr ""
1780 "当所有资源上的两个节点都是 _UpToDate_ 时,您可以将应用程序移动到已升级的节点(此处为 `bob` ),然后在仍在运行8.4的群集节点上执行相同"
1781 "的步骤。"
1782
1783 #. type: Title ====
1784 #, no-wrap
1785 msgid "From DRBD 9 to DRBD 9"
1786 msgstr "从DRBD 9到DRBD 9"
1787
1788 #. type: Plain text
1789 msgid ""
1790 "If you are already running 9.0, it is sufficient to <<s-Upgrading-the-packages,install new package versions>>, make the cluster "
1791 "node <<s-upgrade-pausing-the-cluster,_standby_>>, <<s-upgrade-reload-kernel-mod,unload/reload>> the kernel module, <<s-upgrade-"
1792 "start-drbd,start the resources>>, and make the cluster node _online_ againfootnote:[At least that's the state at the time of "
1793 "writing - that's how it has been in the past, and we want to keep it that easy. But who knows? Who can tell? ;)]."
1794 msgstr ""
1795 "如果您已经在运行9.0,则只需<<s-Upgrading-the-packages,install new package versions>>,使群集节点<<s-upgrade-pausing-the-cluster,"
1796 "_standby_>>,<<s-upgrade-reload-kernel-mod,unload/reload>>内核模块,<<s-upgrade-start-drbd,start the resources>>,并使集群节点重新"
1797 "联机footnote:[至少这是编写时的状态-这是过去的情况,我们希望保持它的简单性。但谁知道呢?谁能讲明白呢?;)]."
1798
1799 #. type: Plain text
1800 msgid "These individual steps have been detailed above, so we won't repeat them here."
1801 msgstr "上面已经详细介绍了这些步骤,因此我们在这里不再重复。"
1802
1803 #. type: Title ===
1804 #, no-wrap
1805 msgid "Enabling dual-primary mode"
1806 msgstr "启用双主模式"
1807
1808 #. type: Plain text
1809 msgid ""
1810 "Dual-primary mode allows a resource to assume the primary role simultaneously on more than one node. Doing so is possible on "
1811 "either a permanent or a temporary basis."
1812 msgstr "双主模式允许资源在多个节点上同时承担主角色。这样做可以是永久性的,也可以是暂时性的。"
1813
1814 #. type: delimited block =
1815 msgid ""
1816 "Dual-primary mode requires that the resource is configured to replicate synchronously (protocol C). Because of this it is latency "
1817 "sensitive, and ill suited for WAN environments."
1818 msgstr "双主模式要求将资源配置为同步复制(protocol C)。因此,它对延迟敏感,不适合广域网环境。"
1819
1820 #. type: delimited block =
1821 msgid ""
1822 "Additionally, as both resources are always primary, any interruption in the network between nodes will result in a split-brain."
1823 msgstr "另外,由于这两种资源都是主要的,节点之间网络的任何中断都会导致脑裂。"
1824
1825 #. type: Plain text
1826 msgid "In DRBD 9.0.x Dual-Primary mode is limited to exactly 2 Primaries for the use in live migration."
1827 msgstr "在DRBD 9.0.x中,双主模式仅限于2个主节点,通常用于实时迁移。"
1828
1829 #. type: Title ====
1830 #, no-wrap
1831 msgid "Permanent dual-primary mode"
1832 msgstr "永久双主模式"
1833
1834 #. type: Plain text
1835 msgid ""
1836 "indexterm:[multiple primaries]indexterm:[dual-primary mode]To enable dual-primary mode, set the `allow-two-primaries` option to "
1837 "`yes` in the `net` section of your resource configuration:"
1838 msgstr ""
1839 "indexterm:[multiple primaries]indexterm:[dual primary mode]要启用双主模式,请在资源配置的 `net` 部分将 `allow two primaries` 选项设置"
1840 "为 `yes` :"
1841
1842 #. type: delimited block -
1843 #, no-wrap
1844 msgid ""
1845 "resource <resource>\n"
1846 " net {\n"
1847 " protocol C;\n"
1848 " allow-two-primaries yes;\n"
1849 " fencing resource-and-stonith;\n"
1850 " }\n"
1851 " handlers {\n"
1852 " fence-peer \"...\";\n"
1853 " unfence-peer \"...\";\n"
1854 " }\n"
1855 " ...\n"
1856 "}\n"
1857 msgstr ""
1858 "resource <resource>\n"
1859 " net {\n"
1860 " protocol C;\n"
1861 " allow-two-primaries yes;\n"
1862 " fencing resource-and-stonith;\n"
1863 " }\n"
1864 " handlers {\n"
1865 " fence-peer \"...\";\n"
1866 " unfence-peer \"...\";\n"
1867 " }\n"
1868 " ...\n"
1869 "}\n"
1870
1871 #. type: Plain text
1872 msgid "After that, do not forget to synchronize the configuration between nodes. Run `drbdadm adjust _<resource>_` on both nodes."
1873 msgstr "之后,不要忘记同步节点之间的配置。在两个节点上都运行 `drbdadm adjust` 。"
1874
1875 #. type: Plain text
1876 msgid "You can now change both nodes to role primary at the same time with `drbdadm primary _<resource>_`."
1877 msgstr "现在可以使用 `drbdadm primary` 将两个节点同时更改为role primary。"
1878
1879 #. type: Plain text
1880 msgid ""
1881 "You should always implement suitable fencing policies. Using 'allow-two-primaries' without fencing is a very bad idea, even "
1882 "worse than using single-primary without fencing."
1883 msgstr "您应该始终执行适当的围栏策略。使用 `allow-two-primaries` 而没有围栏策略是个坏主意,比在无围栏使用单主节点更糟糕。"
1884
1885 #. type: Title ====
1886 #, no-wrap
1887 msgid "Temporary dual-primary mode"
1888 msgstr "临时双主模式"
1889
1890 #. type: Plain text
1891 msgid ""
1892 "To temporarily enable dual-primary mode for a resource normally running in a single-primary configuration, issue the following "
1893 "command:"
1894 msgstr "要临时为通常在单个主配置中运行的资源启用双主模式,请使用以下命令:"
1895
1896 #. type: delimited block -
1897 #, no-wrap
1898 msgid "# drbdadm net-options --protocol=C --allow-two-primaries <resource>\n"
1899 msgstr "# drbdadm net-options --protocol=C --allow-two-primaries <resource>\n"
1900
1901 #. type: Plain text
1902 msgid ""
1903 "To end temporary dual-primary mode, run the same command as above but with `--allow-two-primaries=no` (and your desired "
1904 "replication protocol, if applicable)."
1905 msgstr "要结束临时双主模式,请运行与上面相同的命令,但使用 `--allow two primaries=no` (以及所需的复制协议,如果适用)。"
1906
1907 #. type: Title ===
1908 #, no-wrap
1909 msgid "Using on-line device verification"
1910 msgstr "使用在线设备验证"
1911
1912 #. type: Title ====
1913 #, no-wrap
1914 msgid "Enabling on-line verification"
1915 msgstr "启用在线验证"
1916
1917 #. type: Plain text
1918 msgid ""
1919 "indexterm:[on-line device verification]<<s-online-verify,On-line device verification>> for resources is not enabled by default. "
1920 "To enable it, add the following lines to your resource configuration in `/etc/drbd.conf`:"
1921 msgstr ""
1922 "indexterm:[on-line device verification]默认情况下,资源的<<s-online-verify,On-line device verification>>未启用。要启用它,请将以下"
1923 "行添加到 `/etc/drbd.conf` 中的资源配置中:"
1924
1925 #. type: delimited block -
1926 #, no-wrap
1927 msgid ""
1928 "resource <resource>\n"
1929 " net {\n"
1930 " verify-alg <algorithm>;\n"
1931 " }\n"
1932 " ...\n"
1933 "}\n"
1934 msgstr ""
1935 "resource <resource>\n"
1936 " net {\n"
1937 " verify-alg <algorithm>;\n"
1938 " }\n"
1939 " ...\n"
1940 "}\n"
1941
1942 #. type: Plain text
1943 msgid ""
1944 "_<algorithm>_ may be any message digest algorithm supported by the kernel crypto API in your system's kernel configuration. "
1945 "Normally, you should be able to choose at least from `sha1`, `md5`, and `crc32c`."
1946 msgstr ""
1947 "_<algorithm>_ 可能是系统内核配置中内核加密API支持的任何消息摘要算法。通常,您至少可以从 `sha1` , `md5` 和 `crc32c` 中进行选择。"
1948
1949 #. type: Plain text
1950 msgid ""
1951 "If you make this change to an existing resource, as always, synchronize your `drbd.conf` to the peer, and run `drbdadm adjust "
1952 "_<resource>_` on both nodes."
1953 msgstr "如果对现有资源进行此更改,请一如既往地将 `drbd.conf` 同步到对等节点,并在两个节点上运行 `drbdadm adjust _<resource>_` 。"
1954
1955 #. type: Title ====
1956 #, no-wrap
1957 msgid "Invoking on-line verification"
1958 msgstr "调用联机验证"
1959
1960 #. type: Plain text
1961 msgid ""
1962 "indexterm:[on-line device verification]After you have enabled on-line verification, you will be able to initiate a verification "
1963 "run using the following command:"
1964 msgstr "indexterm:[on-line device verification]启用联机验证后,可以使用以下命令启动验证运行:"
1965
1966 #. type: delimited block -
1967 #, no-wrap
1968 msgid "# drbdadm verify <resource>\n"
1969 msgstr "# drbdadm verify <resource>\n"
1970
1971 #. type: Plain text
1972 msgid ""
1973 "When you do so, DRBD starts an online verification run for _<resource>_, and if it detects any blocks that are not in sync, will "
1974 "mark those blocks as such and write a message to the kernel log. Any applications using the device at that time can continue to "
1975 "do so unimpeded, and you may also <<s-switch-resource-roles,switch resource roles>> at will."
1976 msgstr ""
1977 "输入上述命令后,DRBD将针对 _<resource>_ 启动联机验证运行,如果它检测到任何不同步的块,则会将这些块标记为此类并向内核日志中写入一条"
1978 "消息。所有使用该设备的应用程序那时可以继续不受阻碍地执行此操作, 并且您也根据<<s-switch-resource-roles,switch resource roles>>进"
1979 "行定制化。"
1980
1981 #. type: Plain text
1982 msgid ""
1983 "If out-of-sync blocks were detected during the verification run, you may resynchronize them using the following commands after "
1984 "verification has completed:"
1985 msgstr "如果在验证运行期间检测到不同步块,则可以在验证完成后使用以下命令重新同步它们:"
1986
1987 #. type: delimited block -
1988 #, no-wrap
1989 msgid ""
1990 "# drbdadm disconnect <resource>\n"
1991 "# drbdadm connect <resource>\n"
1992 msgstr ""
1993 "# drbdadm disconnect <resource>\n"
1994 "# drbdadm connect <resource>\n"
1995
1996 #. type: Title ====
1997 #, no-wrap
1998 msgid "Automating on-line verification"
1999 msgstr "自动在线验证"
2000
2001 #. type: Plain text
2002 msgid ""
2003 "indexterm:[on-line device verification]Most users will want to automate on-line device verification. This can be easily "
2004 "accomplished. Create a file with the following contents, named `/etc/cron.d/drbd-verify` on *one* of your nodes:"
2005 msgstr ""
2006 "indexterm:[on-line device verification]大多数用户都希望自动化联机设备验证。这很容易实现。在任一节点上创建一个包含以下内容的文件,"
2007 "名为 `/etc/cron.d/drbd-verify` :"
2008
2009 #. type: delimited block -
2010 #, no-wrap
2011 msgid "42 0 * * 0 root /sbin/drbdadm verify <resource>\n"
2012 msgstr "42 0 * * 0 root /sbin/drbdadm verify <resource>\n"
2013
2014 #. type: Plain text
2015 msgid ""
2016 "This will have `cron` invoke a device verification every Sunday at 42 minutes past midnight; so, if you come into the office on "
2017 "Monday morning, a quick look at the resource's status would show the result. If your devices are very big, and the \\~32 hours "
2018 "were not enough, then you'll notice _VerifyS_ or _VerifyT_ as connection state, meaning that the `verify` is still in progress."
2019 msgstr ""
2020 "这将使 `cron` 在每周日午夜后42分钟调用一个设备验证;因此,假设您在周一上午进入办公室,快速查看资源的状态将显示结果。如果您的设备很"
2021 "大,而且32小时还不够,那么您将注意到 _VerifyS_ 或 _VerifyT_ 作为连接状态,这意味着 `verify` 仍在进行中。"
2022
2023 #. type: Plain text
2024 msgid ""
2025 "If you have enabled on-line verification for all your resources (for example, by adding `verify-alg _<algorithm>_` to the "
2026 "`common` section in `/etc/drbd.d/global_common.conf`), you may also use:"
2027 msgstr ""
2028 "如果您已经为所有资源启用了联机验证(例如,通过在 `/etc/drbd.d/global_common.conf` 中的 `common` 部分添加 `verify-alg _<algorithm>_`,"
2029 "您就可以使用:"
2030
2031 #. type: delimited block -
2032 #, no-wrap
2033 msgid "42 0 * * 0 root /sbin/drbdadm verify all\n"
2034 msgstr "42 0 * * 0 root /sbin/drbdadm verify all\n"
2035
2036 #. type: Title ===
2037 #, no-wrap
2038 msgid "Configuring the rate of synchronization"
2039 msgstr "配置同步速率"
2040
2041 #. type: Plain text
2042 msgid ""
2043 "indexterm:[synchronization]Normally, one tries to ensure that background synchronization (which makes the data on the "
2044 "synchronization target temporarily inconsistent) completes as quickly as possible. However, it is also necessary to keep "
2045 "background synchronization from hogging all bandwidth otherwise available for foreground replication, which would be detrimental "
2046 "to application performance. Thus, you must configure the synchronization bandwidth to match your hardware -- which you may do in "
2047 "a permanent fashion or on-the-fly."
2048 msgstr ""
2049 "indexterm:[synchronization]通常,会尝试确保后台同步(这会使同步目标上的数据暂时不一致)尽快完成。但是,还必须防止后台同步占用前台"
2050 "复制所需的所有带宽,这将对应用程序性能造成损害。因此,您必须配置同步带宽以匹配您的硬件 - 您可以永久地或动态地这样做。"
2051
2052 #. type: Plain text
2053 msgid ""
2054 "It does not make sense to set a synchronization rate that is higher than the maximum write throughput on your secondary node. You "
2055 "must not expect your secondary node to miraculously be able to write faster than its I/O subsystem allows, just because it "
2056 "happens to be the target of an ongoing device synchronization."
2057 msgstr ""
2058 "设置高于辅助节点上最大写入吞吐量的同步速率是没有意义的。您不能期望辅助节点奇迹般地能够比其I/O子系统所允许的写入速度快,因为它恰好"
2059 "是正在进行的设备同步的目标。"
2060
2061 #. type: Plain text
2062 msgid ""
2063 "Likewise, and for the same reasons, it does not make sense to set a synchronization rate that is higher than the bandwidth "
2064 "available on the replication network."
2065 msgstr "同样,出于同样的原因,设置高于复制网络上可用带宽的同步速率是没有意义的。"
2066
2067 #. type: Title ====
2068 #, no-wrap
2069 msgid "Estimating a synchronization speed"
2070 msgstr "估计同步速度"
2071
2072 #. type: Plain text
2073 msgid ""
2074 "A good rule of thumb for this value is to use about 30% of the available replication bandwidth. Thus, if you had an I/O subsystem "
2075 "capable of sustaining write throughput of 400MB/s, and a Gigabit Ethernet network capable of sustaining 110 MB/s network "
2076 "throughput (the network being the bottleneck), you would calculate:"
2077 msgstr ""
2078 "对于这个值,一个很好的经验法则是使用大约30%的可用复制带宽。因此,如果有一个I/O子系统能够维持400MB/s的写吞吐量,而一个千兆以太网网"
2079 "络能够维持110MB/s的网络吞吐量(网络是瓶颈),您可以如下计算:"
2080
2081 #. type: Block title
2082 #, no-wrap
2083 msgid "Syncer rate example, 110MB/s effective available bandwidth"
2084 msgstr "同步速率示例,110MB/s有效可用带宽"
2085
2086 #. type: Target for macro image
2087 #, no-wrap
2088 msgid "images/sync-rate-example1.svg"
2089 msgstr "images/sync-rate-example1.svg"
2090
2091 #. type: Plain text
2092 msgid "Thus, the recommended value for the `rate` option would be `33M`."
2093 msgstr "因此,`rate` 选项的建议值为 `33M` 。"
2094
2095 #. type: Plain text
2096 msgid ""
2097 "By contrast, if you had an I/O subsystem with a maximum throughput of 80MB/s and a Gigabit Ethernet connection (the I/O subsystem "
2098 "being the bottleneck), you would calculate:"
2099 msgstr "相比之下,如果您有一个最大吞吐量为80MB/s的I/O子系统和一个千兆以太网连接(I/O子系统是瓶颈),您将计算:"
2100
2101 #. type: Block title
2102 #, no-wrap
2103 msgid "Syncer rate example, 80MB/s effective available bandwidth"
2104 msgstr "同步速率示例,80MB/s有效可用带宽"
2105
2106 #. type: Target for macro image
2107 #, no-wrap
2108 msgid "images/sync-rate-example2.svg"
2109 msgstr "images/sync-rate-example2.svg"
2110
2111 #. type: Plain text
2112 msgid "In this case, the recommended value for the `rate` option would be `24M`."
2113 msgstr "在这种情况下,`rate` 选项的建议值为 `24M` 。"
2114
2115 #. type: Plain text
2116 msgid ""
2117 "Similarly, for a storage speed of 800MB/s and a 10Gbe network connection, you would shoot for \\~240MB/s synchronization rate."
2118 msgstr "类似地,对于800MB/s的存储速度和10Gbe的网络连接,您将获得大约\\~240MB/s的同步速率。"
2119
2120 #. type: Title ====
2121 #, no-wrap
2122 msgid "Variable sync rate configuration"
2123 msgstr "可变同步速率配置"
2124
2125 #. type: Plain text
2126 msgid ""
2127 "When multiple DRBD resources share a single replication/synchronization network, synchronization with a fixed rate may not be an "
2128 "optimal approach. So, in DRBD 8.4.0 the variable-rate synchronization was enabled by default. In this mode, DRBD uses an "
2129 "automated control loop algorithm to determine, and adjust, the synchronization rate. This algorithm ensures that there is always "
2130 "sufficient bandwidth available for foreground replication, greatly mitigating the impact that background synchronization has on "
2131 "foreground I/O."
2132 msgstr ""
2133 "当多个DRBD资源共享一个复制/同步网络时,以固定速率同步可能不是最佳方法。因此,在DRBD 8.4.0中,默认情况下启用了可变速率同步。在这种"
2134 "模式下,DRBD使用自动控制环路算法来确定和调整同步速率。该算法保证了前台复制始终有足够的带宽,大大减轻了后台同步对前台I/O的影响。"
2135
2136 #. type: Plain text
2137 msgid ""
2138 "The optimal configuration for variable-rate synchronization may vary greatly depending on the available network bandwidth, "
2139 "application I/O pattern and link congestion. Ideal configuration settings also depend on whether <<s-drbd-proxy,DRBD Proxy>> is "
2140 "in use or not. It may be wise to engage professional consultancy in order to optimally configure this DRBD feature. An _example_ "
2141 "configuration (which assumes a deployment in conjunction with DRBD Proxy) is provided below:"
2142 msgstr ""
2143 "可变速率同步的最佳配置可能因可用的网络带宽、应用程序I/O模式和链路拥塞而有很大差异。理想的配置设置还取决于<<s-drbd-proxy,DRBD "
2144 "Proxy>>是否正在使用。为了优化配置这个DRBD特性,最好聘请专业顾问。下面提供了一个配置示例(假设与DRBD代理一起部署):"
2145
2146 #. type: delimited block -
2147 #, no-wrap
2148 msgid ""
2149 "resource <resource> {\n"
2150 " disk {\n"
2151 " c-plan-ahead 5;\n"
2152 " c-max-rate 10M;\n"
2153 " c-fill-target 2M;\n"
2154 " }\n"
2155 "}\n"
2156 msgstr ""
2157 "resource <resource> {\n"
2158 " disk {\n"
2159 " c-plan-ahead 5;\n"
2160 " c-max-rate 10M;\n"
2161 " c-fill-target 2M;\n"
2162 " }\n"
2163 "}\n"
2164
2165 #. type: Plain text
2166 msgid "A good starting value for `c-fill-target` is _BDP * 2_, where _BDP_ is your bandwidth-delay-product on the replication link."
2167 msgstr "`c-fill-target` 的一个很好的初始值是 _BDP * 2_, 其中 _BDP_ 是复制链接上的带宽延迟产品。"
2168
2169 #. type: Plain text
2170 msgid ""
2171 "For example, when using a 1GBit/s crossover connection, you'll end up with about 200µs latencyfootnote:[The rule-of-thumb is "
2172 "using the time reported by `ping`.]. + 1GBit/s means about 120MB/s; times 200*10^-6^ seconds gives 24000 Byte. Just round that "
2173 "value up to the next MB, and you're good to go."
2174 msgstr ""
2175 "例如,当使用1GBit/s交叉连接时,您将得到大约200微秒的延迟footnote:[经验法则是使用 `ping` 报告的时间]。 + 1GBit/s意味着大约120MB/s;乘"
2176 "以200*10^-6^秒得到24000字节。把这个值四舍五入到下一个MB,你就得到了值。"
2177
2178 #. type: Plain text
2179 msgid ""
2180 "Another example: a 100MBit WAN connection with 200ms latency means 12MB/s times 0.2s, or about 2.5MB \"on the wire\". Here a good "
2181 "starting value for `c-fill-target` would be 3MB."
2182 msgstr ""
2183 "另一个例子:一个100兆位的广域网连接,200毫秒的延迟意味着12兆字节/秒乘以0.2秒,或者说大约2.5兆字节 \"on the wire\"\"在线\"。在这"
2184 "里, `c-fill-target` 的初始值可预设为是3MB。"
2185
2186 #. type: Plain text
2187 msgid "Please see the `drbd.conf` manual page for more details on the other configuration items."
2188 msgstr "有关其他配置项的详细信息,请参见 `drbd.conf` 手册页。"
2189
2190 #. type: Title ====
2191 #, no-wrap
2192 msgid "Permanent fixed sync rate configuration"
2193 msgstr "永久固定同步速率配置"
2194
2195 #. type: Plain text
2196 msgid ""
2197 "In a few, very restricted situationsfootnote:[Like benchmarking.], it might make sense to just use some fixed synchronization "
2198 "rate. In this case, first of all you need to turn the dynamic sync rate controller off, by using `c-plan-ahead 0;`."
2199 msgstr ""
2200 "在一些非常受限的情况下,footnote:[就像基准测试一样],使用一些固定的同步速率可能是有意义的。在这种情况下,首先需要使用 `c-plan-"
2201 "ahead 0;` 关闭动态同步速率控制器。"
2202
2203 #. type: Plain text
2204 msgid ""
2205 "Then, the maximum bandwidth a resource uses for background re-synchronization is determined by the `resync-rate` option for a "
2206 "resource. This must be included in the resource's `disk` section in `/etc/drbd.conf`:"
2207 msgstr "然后,资源用于后台重新同步的最大带宽由资源的 `resync-rate` 选项确定。这必须包含在 `/etc/drbd.conf` 的资源定义的 `disk` 条目中:"
2208
2209 #. type: delimited block -
2210 #, no-wrap
2211 msgid ""
2212 "resource <resource>\n"
2213 " disk {\n"
2214 " resync-rate 40M;\n"
2215 " ...\n"
2216 " }\n"
2217 " ...\n"
2218 "}\n"
2219 msgstr ""
2220 "resource <resource>\n"
2221 " disk {\n"
2222 " resync-rate 40M;\n"
2223 " ...\n"
2224 " }\n"
2225 " ...\n"
2226 "}\n"
2227
2228 #. type: Plain text
2229 msgid ""
2230 "Note that the rate setting is given in _bytes_, not _bits_ per second; the default unit is _Kibibyte_, so a value of `4096` would "
2231 "be interpreted as `4MiB`."
2232 msgstr "请注意,速率设置以字节为单位,而不是以比特/秒为单位;默认单位是字节,因此值 `4096` 将被解释为 `4MiB` 。"
2233
2234 #. type: Plain text
2235 msgid ""
2236 "This just defines a rate that DRBD tries to achieve. If there is a bottleneck with lower throughput (network, storage speed), the "
2237 "defined speed (aka the \"wished-for\" performance ;) won't be reached."
2238 msgstr "这只是定义了DRBD试图达到的速率。如果存在吞吐量较低的瓶颈(网络、存储速度),则无法达到定义的速度(也称为\"期望\"性能;)。"
2239
2240 #. type: Title ====
2241 #, no-wrap
2242 msgid "Some more hints about synchronization"
2243 msgstr "关于同步的更多提示"
2244
2245 #. type: Plain text
2246 msgid ""
2247 "When some amount of the to-be-synchronized data isn't really in use anymore (e.g. because files got deleted while one node wasn't "
2248 "connected), you might benefit from the <<s-trim-discard>>."
2249 msgstr "当一些要同步的数据不再实际使用时(例如,因为文件在一个节点未连接时被删除),您可能会从<<s-trim-discard>>中受益。"
2250
2251 #. type: Plain text
2252 msgid ""
2253 "Furthermore, `c-min-rate` is easy to misunderstand - it doesn't define a *minimum* synchronization speed, but rather a limit "
2254 "below which DRBD will not slow down further *on purpose*. + Whether you manage to *reach* that synchronization rate depends on "
2255 "your network and storage speed, network latency (which might be highly variable for shared links), and application IO (which not "
2256 "might be able to do anything about)."
2257 msgstr ""
2258 "此外, `c-min-rate` 很容易被误解 - 它没有定义*最小*同步速度,而是一个限制,低于这个限制,DRBD就不会进一步 *故意* 减速。 + 您是否能够达"
2259 "到同步速率取决于您的网络和存储速度、网络延迟(对于共享链接来说,这可能是高度可变的)和应用程序IO(对此可能无能为力)。"
2260
2261 #. type: Title ===
2262 #, no-wrap
2263 msgid "Configuring checksum-based synchronization"
2264 msgstr "配置基于校验和的同步"
2265
2266 #. type: Plain text
2267 msgid ""
2268 "indexterm:[checksum-based synchronization]<<p-checksum-sync,Checksum-based synchronization>> is not enabled for resources by "
2269 "default. To enable it, add the following lines to your resource configuration in `/etc/drbd.conf`:"
2270 msgstr ""
2271 "indexterm:[checksum-based synchronization]<<p-checksum-sync,Checksum-based synchronization>>默认情况下不为资源启用。要启用它,请将"
2272 "以下行添加到 `/etc/drbd.conf` 中的资源配置中:"
2273
2274 #. type: delimited block -
2275 #, no-wrap
2276 msgid ""
2277 "resource <resource>\n"
2278 " net {\n"
2279 " csums-alg <algorithm>;\n"
2280 " }\n"
2281 " ...\n"
2282 "}\n"
2283 msgstr ""
2284 "resource <resource>\n"
2285 " net {\n"
2286 " csums-alg <algorithm>;\n"
2287 " }\n"
2288 " ...\n"
2289 "}\n"
2290
2291 #. type: Title ===
2292 #, no-wrap
2293 msgid "Configuring congestion policies and suspended replication"
2294 msgstr "配置拥塞策略和挂起复制"
2295
2296 #. type: Plain text
2297 msgid ""
2298 "In an environment where the replication bandwidth is highly variable (as would be typical in WAN replication setups), the "
2299 "replication link may occasionally become congested. In a default configuration, this would cause I/O on the primary node to "
2300 "block, which is sometimes undesirable."
2301 msgstr ""
2302 "在复制带宽高度可变的环境中(这在广域网复制设置中是典型的),复制链路有时可能会变得拥挤。在默认配置中,这将导致主节点上的I/O阻塞,"
2303 "这有时是不可取的。"
2304
2305 #. type: Plain text
2306 msgid ""
2307 "Instead, you may configure DRBD to _suspend_ the ongoing replication in this case, causing the Primary's data set to _pull ahead_ "
2308 "of the Secondary. In this mode, DRBD keeps the replication channel open -- it never switches to disconnected mode -- but does not "
2309 "actually replicate until sufficient bandwidth becomes available again."
2310 msgstr ""
2311 "相反,在这种情况下,您可以将DRBD配置为挂起正在进行的复制,从而使主数据集位于次数据集的 _前拉_ _pull ahead_ 位置。在这种模式下,DRBD"
2312 "保持复制通道打开 - 它从不切换到断开连接的模式 - 但直到有足够的带宽再次可用时才真正进行复制。"
2313
2314 #. type: Plain text
2315 msgid "The following example is for a DRBD Proxy configuration:"
2316 msgstr "以下示例适用于DRBD代理配置:"
2317
2318 #. type: delimited block -
2319 #, no-wrap
2320 msgid ""
2321 "resource <resource> {\n"
2322 " net {\n"
2323 " on-congestion pull-ahead;\n"
2324 " congestion-fill 2G;\n"
2325 " congestion-extents 2000;\n"
2326 " ...\n"
2327 " }\n"
2328 " ...\n"
2329 "}\n"
2330 msgstr ""
2331 "resource <resource> {\n"
2332 " net {\n"
2333 " on-congestion pull-ahead;\n"
2334 " congestion-fill 2G;\n"
2335 " congestion-extents 2000;\n"
2336 " ...\n"
2337 " }\n"
2338 " ...\n"
2339 "}\n"
2340
2341 #. type: Plain text
2342 msgid "It is usually wise to set both `congestion-fill` and `congestion-extents` together with the `pull-ahead` option."
2343 msgstr "通常明智的做法是将 `congestion-fill` 和 `congestion-extents` 与 `pull-ahead` 选项一起设置。"
2344
2345 #. type: Plain text
2346 msgid "A good value for `congestion-fill` is 90%"
2347 msgstr "`congestion-fill` 的理想值是90%"
2348
2349 #. type: Plain text
2350 msgid "of the allocated DRBD proxy buffer memory, when replicating over DRBD Proxy, or"
2351 msgstr "当通过DRBD proxy进行复制时,分配的DRBD proxy缓冲存储器,或"
2352
2353 #. type: Plain text
2354 msgid "of the TCP network send buffer, in non-DRBD Proxy setups."
2355 msgstr "在非DRBD代理设置中的TCP网络发送缓冲区。"
2356
2357 #. type: Plain text
2358 msgid "A good value for `congestion-extents` is 90% of your configured `al-extents` for the affected resources."
2359 msgstr "`congestion-extents` 的理想值是受影响资源配置的 `al-extents` 的90%。"
2360
2361 #. type: Title ===
2362 #, no-wrap
2363 msgid "Configuring I/O error handling strategies"
2364 msgstr "配置I/O错误处理策略"
2365
2366 #. type: Plain text
2367 msgid ""
2368 "indexterm:[I/O errors]indexterm:[drbd.conf]DRBD's <<s-handling-disk-errors,strategy for handling lower-level I/O errors>> is "
2369 "determined by the `on-io-error` option, included in the resource `disk` configuration in `/etc/drbd.conf`:"
2370 msgstr ""
2371 "indexterm:[I/O error s]indexterm:[drbd.conf]DRBD的<<s-handling-disk-errors,strategy for handling lower-level I/O errors>>由 `/etc/"
2372 "drbd.conf` 文件中resource下的 `disk` 配置中的 `on-io-error` 选项确定:"
2373
2374 #. type: delimited block -
2375 #, no-wrap
2376 msgid ""
2377 "resource <resource> {\n"
2378 " disk {\n"
2379 " on-io-error <strategy>;\n"
2380 " ...\n"
2381 " }\n"
2382 " ...\n"
2383 "}\n"
2384 msgstr ""
2385 "resource <resource> {\n"
2386 " disk {\n"
2387 " on-io-error <strategy>;\n"
2388 " ...\n"
2389 " }\n"
2390 " ...\n"
2391 "}\n"
2392
2393 #. type: Plain text
2394 msgid ""
2395 "You may, of course, set this in the `common` section too, if you want to define a global I/O error handling policy for all "
2396 "resources."
2397 msgstr "当然,如果要为所有资源定义全局I/O错误处理策略,也可以在 `common` 部分中设置此值。"
2398
2399 #. type: Plain text
2400 msgid "_<strategy>_ may be one of the following options:"
2401 msgstr "_<strategy>_ 可能是以下选项之一:"
2402
2403 #. type: Block title
2404 #, no-wrap
2405 msgid "`detach`"
2406 msgstr "`detach`"
2407
2408 #. type: Plain text
2409 msgid ""
2410 "This is the default and recommended option. On the occurrence of a lower-level I/O error, the node drops its backing device, and "
2411 "continues in diskless mode."
2412 msgstr "这是默认和推荐的选项。在发生较低级别的I/O错误时,节点将丢弃其备份设备,并继续以无盘模式运行。"
2413
2414 #. type: Block title
2415 #, no-wrap
2416 msgid "`pass-on`"
2417 msgstr "`pass-on`"
2418
2419 #. type: Plain text
2420 msgid ""
2421 "This causes DRBD to report the I/O error to the upper layers. On the primary node, it is reported to the mounted file system. On "
2422 "the secondary node, it is ignored (because the secondary has no upper layer to report to)."
2423 msgstr "这导致DRBD向上层报告I/O错误。在主节点上,它将报告给已装入的文件系统。在次节点上,它被忽略(因为次节点没有要报告的上层)。"
2424
2425 #. type: Block title
2426 #, no-wrap
2427 msgid "`call-local-io-error`"
2428 msgstr "`call-local-io-error`"
2429
2430 #. type: Plain text
2431 msgid ""
2432 "Invokes the command defined as the local I/O error handler. This requires that a corresponding `local-io-error` command "
2433 "invocation is defined in the resource's `handlers` section. It is entirely left to the administrator's discretion to implement I/"
2434 "O error handling using the command (or script) invoked by `local-io-error`."
2435 msgstr ""
2436 "调用定义为本地I/O错误处理程序的命令。这要求在资源的 `handlers` 部分中定义相应的 `local-io-error` 命令调用。完全由管理员自行决定使用"
2437 " `local-io-error` 调用的命令(或脚本)来实现I/O错误处理。"
2438
2439 #. type: Plain text
2440 msgid ""
2441 "Early DRBD versions (prior to 8.0) included another option, `panic`, which would forcibly remove the node from the cluster by way "
2442 "of a kernel panic, whenever a local I/O error occurred. While that option is no longer available, the same behavior may be "
2443 "mimicked via the `local-io-error`/`call-local-io-error` interface. You should do so only if you fully understand the implications "
2444 "of such behavior."
2445 msgstr ""
2446 "早期的DRBD版本(8.0之前)包含另一个选项 `panic` ,每当发生本地I/O错误时,该选项将通过内核panic从集群中强制删除节点。虽然该选项不再可"
2447 "用,但可以通过 `local-io-error` / `call-local-io-error` 接口来模拟相同的行为。只有当你完全理解这种行为的含义时,你才应该这样做。"
2448
2449 #. type: Plain text
2450 msgid "You may reconfigure a running resource's I/O error handling strategy by following this process:"
2451 msgstr "您可以按照此过程重新配置正在运行的资源的I/O错误处理策略:"
2452
2453 #. type: Plain text
2454 msgid "Edit the resource configuration in `/etc/drbd.d/__<resource>__.res`."
2455 msgstr "在 `/etc/drbd.d/__<resource>__.res` 中编辑资源配置。"
2456
2457 #. type: Plain text
2458 msgid "Copy the configuration to the peer node."
2459 msgstr "将配置复制到对等节点。"
2460
2461 #. type: Plain text
2462 msgid "Issue `drbdadm adjust _<resource>_` on both nodes."
2463 msgstr "在两个节点上都运行 `drbdadm adjust` 命令。"
2464
2465 #. type: Title ===
2466 #, no-wrap
2467 msgid "Configuring replication traffic integrity checking"
2468 msgstr "配置复制通信完整性检查"
2469
2470 #. type: Plain text
2471 msgid ""
2472 "indexterm:[replication traffic integrity checking]<<s-integrity-check,Replication traffic integrity checking>> is not enabled for "
2473 "resources by default. To enable it, add the following lines to your resource configuration in `/etc/drbd.conf`:"
2474 msgstr ""
2475 "indexterm:[replication traffic integrity checking]<<s-integrity-check,Replication traffic integrity checking>>默认情况下不为资源启"
2476 "用。要启用它,请将以下行添加到 `/etc/drbd.conf` 中的资源配置中:"
2477
2478 #. type: delimited block -
2479 #, no-wrap
2480 msgid ""
2481 "resource <resource>\n"
2482 " net {\n"
2483 " data-integrity-alg <algorithm>;\n"
2484 " }\n"
2485 " ...\n"
2486 "}\n"
2487 msgstr ""
2488 "resource <resource>\n"
2489 " net {\n"
2490 " data-integrity-alg <algorithm>;\n"
2491 " }\n"
2492 " ...\n"
2493 "}\n"
2494
2495 #. type: Plain text
2496 msgid ""
2497 "This feature is not intended for production use. Enable only if you need to diagnose data corruption problems, and want to see "
2498 "whether the transport path (network hardware, drivers, switches) might be at fault!"
2499 msgstr "此功能不用于生产用途。仅当需要诊断数据损坏问题并希望查看传输路径(网络硬件、驱动程序、交换机)是否有故障时才启用!"
2500
2501 #. type: Title ===
2502 #, no-wrap
2503 msgid "Resizing resources"
2504 msgstr "调整资源大小"
2505
2506 #. type: Title ====
2507 #, no-wrap
2508 msgid "Growing on-line"
2509 msgstr "在线扩容"
2510
2511 #. type: Plain text
2512 msgid ""
2513 "indexterm:[resource]If the backing block devices can be grown while in operation (online), it is also possible to increase the "
2514 "size of a DRBD device based on these devices during operation. To do so, two criteria must be fulfilled:"
2515 msgstr ""
2516 "indexterm:[resource]如果支持块设备可以在操作(联机)时增长,那么也可以在操作期间基于这些设备增加DRBD设备的大小。为此,必须满足两个"
2517 "标准:"
2518
2519 #. type: Plain text
2520 msgid "The affected resource's backing device must be one managed by a logical volume management subsystem, such as LVM."
2521 msgstr "受影响资源的备份设备必须由逻辑卷管理子系统(如LVM)管理。"
2522
2523 #. type: Plain text
2524 msgid "The resource must currently be in the _Connected_ connection state."
2525 msgstr "资源当前必须处于连接状态。"
2526
2527 #. type: Plain text
2528 msgid "Having grown the backing block devices on all nodes, ensure that only one node is in primary state. Then enter on one node:"
2529 msgstr "在所有节点上增加了备份块设备后,请确保只有一个节点处于主状态。然后在一个节点上输入:"
2530
2531 #. type: delimited block -
2532 #, no-wrap
2533 msgid "# drbdadm resize <resource>\n"
2534 msgstr "# drbdadm resize <resource>\n"
2535
2536 #. type: Plain text
2537 msgid "This triggers a synchronization of the new section. The synchronization is done from the primary node to the secondary node."
2538 msgstr "这将触发新增部分的同步。同步是以从主节点到辅助节点的顺序完成的。"
2539
2540 #. type: Plain text
2541 msgid "If the space you're adding is clean, you can skip syncing the additional space by using the --assume-clean option."
2542 msgstr "如果要添加的空间是干净的,可以使用--assume clean选项跳过同步新增的空间。"
2543
2544 #. type: delimited block -
2545 #, no-wrap
2546 msgid "# drbdadm -- --assume-clean resize <resource>\n"
2547 msgstr "# drbdadm -- --assume-clean resize <resource>\n"
2548
2549 #. type: Title ====
2550 #, no-wrap
2551 msgid "Growing off-line"
2552 msgstr "离线扩容"
2553
2554 #. type: Plain text
2555 msgid ""
2556 "indexterm:[resource]When the backing block devices on both nodes are grown while DRBD is inactive, and the DRBD resource is using "
2557 "<<s-external-meta-data,external meta data>>, then the new size is recognized automatically. No administrative intervention is "
2558 "necessary. The DRBD device will have the new size after the next activation of DRBD on both nodes and a successful establishment "
2559 "of a network connection."
2560 msgstr ""
2561 "indexterm:[resource]当两个节点上的备份块设备在DRBD处于非活动状态时增长,并且DRBD资源正在使用<<s-external-meta-data,external meta "
2562 "data>>,则自动识别新大小。不需要人为干预。下次在两个节点上激活DRBD并成功建立网络连接后,DRBD设备将具有新的大小。"
2563
2564 #. type: Plain text
2565 msgid ""
2566 "If however the DRBD resource is configured to use <<s-internal-meta-data,internal meta data>>, then this meta data must be moved "
2567 "to the end of the grown device before the new size becomes available. To do so, complete the following steps:"
2568 msgstr ""
2569 "然而,如果DRBD资源被配置为使用<<s-internal-meta-data,internal meta data>>,则在新的扩容空间可用之前,必须将该元数据移动到所生长设"
2570 "备的末端。为此,请完成以下步骤:"
2571
2572 #. type: Plain text
2573 msgid "This is an advanced procedure. Use at your own discretion."
2574 msgstr "这是一个高级功能。请自己斟酌使用。"
2575
2576 #. type: Plain text
2577 msgid "Unconfigure your DRBD resource:"
2578 msgstr "取消配置您的DRBD资源:"
2579
2580 #. type: Plain text
2581 msgid "Save the meta data in a text file prior to resizing:"
2582 msgstr "在调整大小之前,请将元数据保存在文本文件中:"
2583
2584 #. type: delimited block -
2585 #, no-wrap
2586 msgid "# drbdadm dump-md <resource> > /tmp/metadata\n"
2587 msgstr "# drbdadm dump-md <resource> > /tmp/metadata\n"
2588
2589 #. type: Plain text
2590 msgid ""
2591 "You must do this on both nodes, using a separate dump file for every node. *Do not* dump the meta data on one node, and simply "
2592 "copy the dump file to the peer. *This. will. not. work.*"
2593 msgstr ""
2594 "必须在两个节点上执行此操作,对每个节点使用单独的转储文件。 *不要* 在一个节点上转储元数据,只需将转储文件复制到对等节点。*这. 行. "
2595 "不. 通.*"
2596
2597 #. type: Plain text
2598 msgid "Grow the backing block device on both nodes."
2599 msgstr "在两个节点上扩展备份块设备。"
2600
2601 #. type: Plain text
2602 msgid ""
2603 "Adjust the size information (`la-size-sect`) in the file `/tmp/metadata` accordingly, on both nodes. Remember that `la-size-sect` "
2604 "must be specified in sectors."
2605 msgstr "在两个节点上相应地调整文件 `/tmp/metadata` 中的大小信息( `la-size-sect` )。请记住,必须在扇区中指定 `la-size-sect`。"
2606
2607 #. type: Plain text
2608 msgid "Re-initialize the metadata area:"
2609 msgstr "重新初始化元数据区域:"
2610
2611 #. type: delimited block -
2612 #, no-wrap
2613 msgid "# drbdadm create-md <resource>\n"
2614 msgstr "# drbdadm create-md <resource>\n"
2615
2616 #. type: Plain text
2617 msgid "Re-import the corrected meta data, on both nodes:"
2618 msgstr "在两个节点上重新导入更正的元数据:"
2619
2620 #. type: delimited block -
2621 #, no-wrap
2622 msgid ""
2623 "# drbdmeta_cmd=$(drbdadm -d dump-md <resource>)\n"
2624 "# ${drbdmeta_cmd/dump-md/restore-md} /tmp/metadata\n"
2625 "Valid meta-data in place, overwrite? [need to type 'yes' to confirm]\n"
2626 "yes\n"
2627 "Successfully restored meta data\n"
2628 msgstr ""
2629 "# drbdmeta_cmd=$(drbdadm -d dump-md <resource>)\n"
2630 "# ${drbdmeta_cmd/dump-md/restore-md} /tmp/metadata\n"
2631 "Valid meta-data in place, overwrite? [need to type 'yes' to confirm]\n"
2632 "yes\n"
2633 "Successfully restored meta data\n"
2634
2635 #. type: Plain text
2636 msgid ""
2637 "This example uses `bash` parameter substitution. It may or may not work in other shells. Check your `SHELL` environment variable "
2638 "if you are unsure which shell you are currently using."
2639 msgstr ""
2640 "此示例使用 `bash` 参数替换。它可能在其他SHELL中工作,也可能不工作。如果不确定当前使用的是哪个SHELL,请检查您的 `SHELL` 环境变量。"
2641
2642 #. type: Plain text
2643 msgid "Re-enable your DRBD resource:"
2644 msgstr "重新启用DRBD资源:"
2645
2646 #. type: Plain text
2647 msgid "On one node, promote the DRBD resource:"
2648 msgstr "在一个节点上,升级DRBD资源:"
2649
2650 #. type: delimited block -
2651 #, no-wrap
2652 msgid "# drbdadm primary <resource>\n"
2653 msgstr "# drbdadm primary <resource>\n"
2654
2655 #. type: Plain text
2656 msgid "Finally, grow the file system so it fills the extended size of the DRBD device."
2657 msgstr "最后,扩展文件系统,使其填充DRBD设备的扩展大小。"
2658
2659 #. type: Title ====
2660 #, no-wrap
2661 msgid "Shrinking on-line"
2662 msgstr "在线缩容"
2663
2664 #. type: Plain text
2665 msgid "Online shrinking is only supported with external metadata."
2666 msgstr "仅外部元数据支持在线缩容。"
2667
2668 #. type: Plain text
2669 msgid ""
2670 "indexterm:[resource]Before shrinking a DRBD device, you _must_ shrink the layers above DRBD, i.e. usually the file system. Since "
2671 "DRBD cannot ask the file system how much space it actually uses, you have to be careful in order not to cause data loss."
2672 msgstr ""
2673 "indexterm:[resource]在缩容DRBD设备之前,_必须_ 收缩DRBD上面的层,通常是文件系统。由于DRBD无法询问文件系统实际使用了多少空间,因此必"
2674 "须小心操作,以免造成数据丢失。"
2675
2676 #. type: Plain text
2677 msgid ""
2678 "Whether or not the _filesystem_ can be shrunk on-line depends on the filesystem being used. Most filesystems do not support on-"
2679 "line shrinking. XFS does not support shrinking at all."
2680 msgstr "_文件系统_是否可以在线缩容取决于所使用的文件系统。大多数文件系统不支持在线缩容。XFS完全不支持缩容。"
2681
2682 #. type: Plain text
2683 msgid "To shrink DRBD on-line, issue the following command _after_ you have shrunk the file system residing on top of it:"
2684 msgstr "要在线缩小DRBD,请先缩小位于其上的文件系统, _之后_ , 输入以下命令:"
2685
2686 #. type: delimited block -
2687 #, no-wrap
2688 msgid "# drbdadm resize --size=<new-size> <resource>\n"
2689 msgstr "# drbdadm resize --size=<new-size> <resource>\n"
2690
2691 #. type: Plain text
2692 msgid ""
2693 "You may use the usual multiplier suffixes for _<new-size>_ (K, M, G etc.). After you have shrunk DRBD, you may also shrink the "
2694 "containing block device (if it supports shrinking)."
2695 msgstr "您可以使用常用的单位来表示 _<new-size>_ (K、M、G等)。收缩DRBD后,还可以收缩其包含的块设备(如果它支持收缩)。"
2696
2697 #. type: Plain text
2698 msgid ""
2699 "It might be a good idea to issue `drbdadm resize _<resource>_` after resizing the lower level device, so that the DRBD metadata "
2700 "*really* gets written into the expected space at the end of the volume."
2701 msgstr "在调整底层设备的大小后,最好输入 `drbdadm resize _<resource>_` 命令,以便将DRBD元数据*真正*写入卷末尾的预期空间。"
2702
2703 #. type: Title ====
2704 #, no-wrap
2705 msgid "Shrinking off-line"
2706 msgstr "离线缩容"
2707
2708 #. type: Plain text
2709 msgid ""
2710 "indexterm:[resource]If you were to shrink a backing block device while DRBD is inactive, DRBD would refuse to attach to this "
2711 "block device during the next attach attempt, since it is now too small (in case external meta data is used), or it would be "
2712 "unable to find its meta data (in case internal meta data is used). To work around these issues, use this procedure (if you cannot "
2713 "use <<s-shrinking-online,on-line shrinking>>):"
2714 msgstr ""
2715 "indexterm:[resource]如果在DRBD处于非活动状态时收缩备份块设备,DRBD将在下次尝试连接时拒绝连接到此块设备,因为它现在太小(如果使用外"
2716 "部元数据),或者找不到它的元数据(如果使用内部元数据)。要解决这些问题,请使用以下步骤(如果无法使用<<s-shrinking-online,on-line "
2717 "shrinking>>):"
2718
2719 #. type: Plain text
2720 msgid "Shrink the file system from one node, while DRBD is still configured."
2721 msgstr "在DRBD仍然配置的情况下,从一个节点缩容文件系统。"
2722
2723 #. type: Plain text
2724 msgid "Save the meta data in a text file prior to shrinking:"
2725 msgstr "在缩容之前将元数据保存在文本文件中:"
2726
2727 #. type: Plain text
2728 msgid "Shrink the backing block device on both nodes."
2729 msgstr "缩容两个节点上的备份块设备。"
2730
2731 #. type: Plain text
2732 #, no-wrap
2733 msgid ""
2734 "*Only if you are using internal metadata* (which at this time have\n"
2735 "probably been lost due to the shrinking process), re-initialize the\n"
2736 "metadata area:\n"
2737 msgstr "*仅当您使用内部元数据时* (此时可能由于收缩过程而丢失),才需要重新初始化元数据区域\n"
2738
2739 #. type: Title ===
2740 #, no-wrap
2741 msgid "Disabling backing device flushes"
2742 msgstr "禁用备份设备刷新"
2743
2744 #. type: Plain text
2745 msgid ""
2746 "You should only disable device flushes when running DRBD on devices with a battery-backed write cache (BBWC). Most storage "
2747 "controllers allow to automatically disable the write cache when the battery is depleted, switching to write-through mode when the "
2748 "battery dies. It is strongly recommended to enable such a feature."
2749 msgstr ""
2750 "在使用电池备份写缓存(BBWC)的设备上运行DRBD时,应禁用设备刷新。大多数存储控制器允许在电池耗尽时自动禁用写缓存,在电池耗尽时切换到"
2751 "直写模式。强烈建议启用此功能。"
2752
2753 #. type: Plain text
2754 msgid ""
2755 "Disabling DRBD's flushes when running without BBWC, or on BBWC with a depleted battery, is _likely to cause data loss_ and should "
2756 "not be attempted."
2757 msgstr "在没有BBWC的情况下运行或在电池耗尽的BBWC上运行时,禁用DRBD的刷新 _可能会导致数据丢失_ ,不应尝试。"
2758
2759 #. type: Plain text
2760 msgid ""
2761 "DRBD allows you to enable and disable <<s-disk-flush-support,backing device flushes>> separately for the replicated data set and "
2762 "DRBD's own meta data. Both of these options are enabled by default. If you wish to disable either (or both), you would set this "
2763 "in the `disk` section for the DRBD configuration file, `/etc/drbd.conf`."
2764 msgstr ""
2765 "DRBD允许对复制的数据集和DRBD自己的元数据分别启用和禁用<<s-disk-flush-support,backing device flushes>>。默认情况下,这两个选项都已"
2766 "启用。如果您希望禁用其中一个(或两个),您可以在DRBD配置文件 `/etc/DRBD.conf` 的 `disk` 部分中设置它。"
2767
2768 #. type: Plain text
2769 msgid "To disable disk flushes for the replicated data set, include the following line in your configuration:"
2770 msgstr "要禁用复制数据集的磁盘刷新,请在配置中包含以下行:"
2771
2772 #. type: delimited block -
2773 #, no-wrap
2774 msgid ""
2775 "resource <resource>\n"
2776 " disk {\n"
2777 " disk-flushes no;\n"
2778 " ...\n"
2779 " }\n"
2780 " ...\n"
2781 "}\n"
2782 msgstr ""
2783 "resource <resource>\n"
2784 " disk {\n"
2785 " disk-flushes no;\n"
2786 " ...\n"
2787 " }\n"
2788 " ...\n"
2789 "}\n"
2790
2791 #. type: Plain text
2792 msgid "To disable disk flushes on DRBD's meta data, include the following line:"
2793 msgstr "要禁用DRBD元数据上的磁盘刷新,请包括以下行:"
2794
2795 #. type: delimited block -
2796 #, no-wrap
2797 msgid ""
2798 "resource <resource>\n"
2799 " disk {\n"
2800 " md-flushes no;\n"
2801 " ...\n"
2802 " }\n"
2803 " ...\n"
2804 "}\n"
2805 msgstr ""
2806 "resource <resource>\n"
2807 " disk {\n"
2808 " md-flushes no;\n"
2809 " ...\n"
2810 " }\n"
2811 " ...\n"
2812 "}\n"
2813
2814 #. type: Plain text
2815 msgid ""
2816 "After you have modified your resource configuration (and synchronized your `/etc/drbd.conf` between nodes, of course), you may "
2817 "enable these settings by issuing this command on both nodes:"
2818 msgstr "在修改了资源配置(当然,在节点之间同步了 `/etc/drbd.conf` )之后,可以通过在两个节点上输入以下命令来启用这些设置:"
2819
2820 #. type: delimited block -
2821 #, no-wrap
2822 msgid "# drbdadm adjust <resource>\n"
2823 msgstr "# drbdadm adjust <resource>\n"
2824
2825 #. type: Plain text
2826 msgid ""
2827 "In case only one of the serves has a BBWCfootnote:[For example, in the DR site you might be using different hardware, right?], "
2828 "you should move the setting into a host section, like this:"
2829 msgstr "如果只有一个服务有BBWCfootnote:[例如,在DR站点中,您可能使用不同的硬件,对吗?],应将设置移动到主机部分,如下所示:"
2830
2831 #. type: delimited block -
2832 #, no-wrap
2833 msgid ""
2834 "resource <resource> {\n"
2835 " disk {\n"
2836 " ... common settings ...\n"
2837 " }\n"
2838 msgstr ""
2839 "resource <resource> {\n"
2840 " disk {\n"
2841 " ... common settings ...\n"
2842 " }\n"
2843
2844 #. type: delimited block -
2845 #, no-wrap
2846 msgid ""
2847 " on host-1 {\n"
2848 " disk {\n"
2849 " md-flushes no;\n"
2850 " }\n"
2851 " ...\n"
2852 " }\n"
2853 " ...\n"
2854 "}\n"
2855 msgstr ""
2856 " on host-1 {\n"
2857 " disk {\n"
2858 " md-flushes no;\n"
2859 " }\n"
2860 " ...\n"
2861 " }\n"
2862 " ...\n"
2863 "}\n"
2864
2865 #. type: Title ===
2866 #, no-wrap
2867 msgid "Configuring split brain behavior"
2868 msgstr "配置裂脑行为"
2869
2870 #. type: Title ====
2871 #, no-wrap
2872 msgid "Split brain notification"
2873 msgstr "裂脑通知"
2874
2875 #. type: Plain text
2876 msgid ""
2877 "DRBD invokes the `split-brain` handler, if configured, at any time split brain is _detected_. To configure this handler, add the "
2878 "following item to your resource configuration:"
2879 msgstr "DRBD调用 `split brain` 处理程序(如果已配置),随时检测到split brain。要配置此处理程序,请将以下项添加到资源配置中:"
2880
2881 #. type: delimited block -
2882 #, no-wrap
2883 msgid ""
2884 "resource <resource>\n"
2885 " handlers {\n"
2886 " split-brain <handler>;\n"
2887 " ...\n"
2888 " }\n"
2889 " ...\n"
2890 "}\n"
2891 msgstr ""
2892 "resource <resource>\n"
2893 " handlers {\n"
2894 " split-brain <handler>;\n"
2895 " ...\n"
2896 " }\n"
2897 " ...\n"
2898 "}\n"
2899
2900 #. type: Plain text
2901 msgid "_<handler>_ may be any executable present on the system."
2902 msgstr "_<handler>_ 可以是系统中存在的任何可执行文件。"
2903
2904 #. type: Plain text
2905 msgid ""
2906 "The DRBD distribution contains a split brain handler script that installs as `/usr/lib/drbd/notify-split-brain.sh`. It simply "
2907 "sends a notification e-mail message to a specified address. To configure the handler to send a message to `root@localhost` (which "
2908 "is expected to be an email address that forwards the notification to a real system administrator), configure the `split-brain "
2909 "handler` as follows:"
2910 msgstr ""
2911 "DRBD发行版包含一个split brain handler脚本,安装为 `/usr/lib/DRBD/notify-split-brain.sh` 。它会将通知电子邮件发送到指定的地址。要将处"
2912 "理程序配置为将消息发送到 `root@localhost` (预期是将通知转发给实际系统管理员的电子邮件地址),请按如下所示配置 `split-brain handler` :"
2913
2914 #. type: delimited block -
2915 #, no-wrap
2916 msgid ""
2917 "resource <resource>\n"
2918 " handlers {\n"
2919 " split-brain \"/usr/lib/drbd/notify-split-brain.sh root\";\n"
2920 " ...\n"
2921 " }\n"
2922 " ...\n"
2923 "}\n"
2924 msgstr ""
2925 "resource <resource>\n"
2926 " handlers {\n"
2927 " split-brain \"/usr/lib/drbd/notify-split-brain.sh root\";\n"
2928 " ...\n"
2929 " }\n"
2930 " ...\n"
2931 "}\n"
2932
2933 #. type: Plain text
2934 msgid ""
2935 "After you have made this modification on a running resource (and synchronized the configuration file between nodes), no "
2936 "additional intervention is needed to enable the handler. DRBD will simply invoke the newly-configured handler on the next "
2937 "occurrence of split brain."
2938 msgstr ""
2939 "对正在运行的资源进行此修改(并在节点之间同步配置文件)后,无需进行其他干预即可启用处理程序。DRBD只需在下一次出现split brain时调用"
2940 "新配置的处理程序。"
2941
2942 #. type: Title ====
2943 #, no-wrap
2944 msgid "Automatic split brain recovery policies"
2945 msgstr "自动裂脑恢复策略"
2946
2947 #. type: Plain text
2948 msgid ""
2949 "Configuring DRBD to automatically resolve data divergence siutaions resulting from split-brain (or other) scenarios is "
2950 "configuring for potential *automatic data loss*. Understand the implications, and don't do it if you don't mean to."
2951 msgstr ""
2952 "将DRBD配置为自动解决由于裂脑(或其他)情况导致的数据分歧问题,是在配置潜在的*自动数据丢失*。请认真理解其中的含义,如果非必要情况请"
2953 "不要这么做。"
2954
2955 #. type: Plain text
2956 msgid ""
2957 "You rather want to look into fencing policies, quorum settings, cluster manager integration, and redundant cluster manager "
2958 "communication links to *avoid* data divergence in the first place."
2959 msgstr "您应该花更多时间研究围栏策略、仲裁设置、群集管理器集成和冗余群集管理器通信链接,以便在第一时间*避免*数据差异。"
2960
2961 #. type: Plain text
2962 msgid ""
2963 "In order to be able to enable and configure DRBD's automatic split brain recovery policies, you must understand that DRBD offers "
2964 "several configuration options for this purpose. DRBD applies its split brain recovery procedures based on the number of nodes in "
2965 "the Primary role at the time the split brain is detected. To that end, DRBD examines the following keywords, all found in the "
2966 "resource's `net` configuration section:"
2967 msgstr ""
2968 "为了能够启用和配置DRBD的自动裂脑恢复策略,您必须了解DRBD为此提供了几个配置选项。DRBD根据检测到裂脑时主要角色的节点数应用其裂脑恢复"
2969 "程序。为此,DRBD检查以下关键字,这些关键字都可以在资源的 `net` 配置部分找到:"
2970
2971 #. type: Block title
2972 #, no-wrap
2973 msgid "`after-sb-0pri`"
2974 msgstr "`after-sb-0pri`"
2975
2976 #. type: Plain text
2977 msgid ""
2978 "Split brain has just been detected, but at this time the resource is not in the Primary role on any host. For this option, DRBD "
2979 "understands the following keywords:"
2980 msgstr "裂脑被检测到,但此时资源在任何主机上都不是主要角色。对于这个选项,DRBD理解以下关键字:"
2981
2982 #. type: Plain text
2983 msgid ""
2984 "`disconnect`: Do not recover automatically, simply invoke the `split-brain` handler script (if configured), drop the connection "
2985 "and continue in disconnected mode."
2986 msgstr "`disconnect` :不要自动恢复,只需调用 `split brain` 处理程序脚本(如果已配置),断开连接并以断开模式继续。"
2987
2988 #. type: Plain text
2989 msgid "`discard-younger-primary`: Discard and roll back the modifications made on the host which assumed the Primary role last."
2990 msgstr "`discard-younger-primary` :放弃并回滚对最后担任主服务器角色的主机所做的修改。"
2991
2992 #. type: Plain text
2993 msgid "`discard-least-changes`: Discard and roll back the modifications on the host where fewer changes occurred."
2994 msgstr "`discard-least-changes`:丢弃并回滚发生较少更改的主机上的更改。"
2995
2996 #. type: Plain text
2997 msgid ""
2998 "`discard-zero-changes`: If there is any host on which no changes occurred at all, simply apply all modifications made on the "
2999 "other and continue."
3000 msgstr "`discard-zero-changes`:如果有任何主机根本没有发生任何更改,只需在另一个主机上应用所做的所有修改并继续。"
3001
3002 #. type: Block title
3003 #, no-wrap
3004 msgid "`after-sb-1pri`"
3005 msgstr "`after-sb-1pri`"
3006
3007 #. type: Plain text
3008 msgid ""
3009 "Split brain has just been detected, and at this time the resource is in the Primary role on one host. For this option, DRBD "
3010 "understands the following keywords:"
3011 msgstr "裂脑被检测到,此时资源在一个主机上扮演主要角色。对于这个选项,DRBD理解以下关键字:"
3012
3013 #. type: Plain text
3014 msgid ""
3015 "`disconnect`: As with `after-sb-0pri`, simply invoke the `split-brain` handler script (if configured), drop the connection and "
3016 "continue in disconnected mode."
3017 msgstr "`disconnect`:与 `after-sb-0pri` 一样,只需调用 `split brain` 处理程序脚本(如果已配置),断开连接并以断开模式继续。"
3018
3019 #. type: Plain text
3020 msgid ""
3021 "`consensus`: Apply the same recovery policies as specified in `after-sb-0pri`. If a split brain victim can be selected after "
3022 "applying these policies, automatically resolve. Otherwise, behave exactly as if `disconnect` were specified."
3023 msgstr ""
3024 "`consensus`:应用 `after-sb-0pri` 中指定的相同恢复策略。如果在应用这些策略后可以选择裂脑受害者,则自动解决。否则,行为就像指定了"
3025 " `disconnect` 一样。"
3026
3027 #. type: Plain text
3028 msgid ""
3029 "`call-pri-lost-after-sb`: Apply the recovery policies as specified in `after-sb-0pri`. If a split brain victim can be selected "
3030 "after applying these policies, invoke the `pri-lost-after-sb` handler on the victim node. This handler must be configured in the "
3031 "`handlers` section and is expected to forcibly remove the node from the cluster."
3032 msgstr ""
3033 "`call-pri-lost-after-sb`:应用 `after-sb-0pri` 中指定的恢复策略。如果在应用这些策略后可以选择裂脑受害者,请调用受害者节点上的 `pri-"
3034 "lost-after-sb` 处理程序。必须在 `handlers` 部分中配置此处理程序,并要求将节点从集群中强制删除。"
3035
3036 #. type: Plain text
3037 msgid "`discard-secondary`: Whichever host is currently in the Secondary role, make that host the split brain victim."
3038 msgstr "`discard-secondary`:无论哪个主机当前处于第二个角色,使该主机成为裂脑受害者。"
3039
3040 #. type: Block title
3041 #, no-wrap
3042 msgid "`after-sb-2pri`"
3043 msgstr "`after-sb-2pri`"
3044
3045 #. type: Plain text
3046 msgid ""
3047 "Split brain has just been detected, and at this time the resource is in the Primary role on both hosts. This option accepts the "
3048 "same keywords as `after-sb-1pri` except `discard-secondary` and `consensus`."
3049 msgstr ""
3050 "裂脑被检测到,此时资源在两个主机上都处于主要角色。此选项接受与 `after-sb-1pri` 相同的关键字,但 `discard-secondary` 和 `consensus` 除"
3051 "外。"
3052
3053 #. type: Plain text
3054 msgid ""
3055 "DRBD understands additional keywords for these three options, which have been omitted here because they are very rarely used. "
3056 "Refer to the man page of `drbd.conf` for details on split brain recovery keywords not discussed here."
3057 msgstr ""
3058 "DRBD理解这三个选项的附加关键字,这里省略了这些关键字,因为它们很少使用。请参阅 `drbd.conf` 的手册页,以了解此处未讨论的脑分裂恢复关"
3059 "键字的详细信息。"
3060
3061 #. type: Plain text
3062 msgid ""
3063 "For example, a resource which serves as the block device for a GFS or OCFS2 file system in dual-Primary mode may have its "
3064 "recovery policy defined as follows:"
3065 msgstr "例如,在双主模式下用作GFS或OCFS2文件系统的块设备的资源的恢复策略定义如下:"
3066
3067 #. type: delimited block -
3068 #, no-wrap
3069 msgid ""
3070 "resource <resource> {\n"
3071 " handlers {\n"
3072 " split-brain \"/usr/lib/drbd/notify-split-brain.sh root\"\n"
3073 " ...\n"
3074 " }\n"
3075 " net {\n"
3076 " after-sb-0pri discard-zero-changes;\n"
3077 " after-sb-1pri discard-secondary;\n"
3078 " after-sb-2pri disconnect;\n"
3079 " ...\n"
3080 " }\n"
3081 " ...\n"
3082 "}\n"
3083 msgstr ""
3084 "resource <resource> {\n"
3085 " handlers {\n"
3086 " split-brain \"/usr/lib/drbd/notify-split-brain.sh root\"\n"
3087 " ...\n"
3088 " }\n"
3089 " net {\n"
3090 " after-sb-0pri discard-zero-changes;\n"
3091 " after-sb-1pri discard-secondary;\n"
3092 " after-sb-2pri disconnect;\n"
3093 " ...\n"
3094 " }\n"
3095 " ...\n"
3096 "}\n"
3097
3098 #. type: Title ===
3099 #, no-wrap
3100 msgid "Creating a stacked three-node setup"
3101 msgstr "创建堆叠的三节点设置"
3102
3103 #. type: Plain text
3104 msgid "A three-node setup involves one DRBD device _stacked_ atop another."
3105 msgstr "三个节点的设置包括一个堆叠在另一个设备上的DRBD设备。"
3106
3107 #. type: Plain text
3108 msgid ""
3109 "Stacking is deprecated in DRBD version 9.x, as more nodes can be implemented on a single level. See <<s-drbdconf-conns>> for "
3110 "details."
3111 msgstr "在DRBD版本9.x中,堆叠是不推荐使用的,因为可以在单个级别上实现更多节点。有关详细信息,请参见<<s-drbdconf-conns>>。"
3112
3113 #. type: Title ====
3114 #, no-wrap
3115 msgid "Device stacking considerations"
3116 msgstr "设备堆叠注意事项"
3117
3118 #. type: Plain text
3119 msgid "The following considerations apply to this type of setup:"
3120 msgstr "以下注意事项适用于此类型的设置:"
3121
3122 #. type: Plain text
3123 msgid ""
3124 "The stacked device is the active one. Assume you have configured one DRBD device `/dev/drbd0`, and the stacked device atop it is "
3125 "`/dev/drbd10`, then `/dev/drbd10` will be the device that you mount and use."
3126 msgstr ""
3127 "堆叠的设备是活动的。假设您已经配置了一个DRBD设备 `/dev/drbd0` ,并且上面的堆叠设备是 `/dev/drbd10` ,那么 `/dev/drbd10` 将是您装载和使用"
3128 "的设备。"
3129
3130 #. type: Plain text
3131 msgid ""
3132 "Device meta data will be stored twice, on the underlying DRBD device _and_ the stacked DRBD device. On the stacked device, you "
3133 "must always use <<s-internal-meta-data,internal meta data>>. This means that the effectively available storage area on a stacked "
3134 "device is slightly smaller, compared to an unstacked device."
3135 msgstr ""
3136 "设备元数据将存储两次,分别存储在底层DRBD设备 _和_ 堆叠的DRBD设备上。在堆叠设备上,必须始终使用<<s-internal-meta-data,internal "
3137 "meta data>>。这意味着,与未堆叠的设备相比,堆叠设备上的有效可用存储区域稍微小一些。"
3138
3139 #. type: Plain text
3140 msgid "To get the stacked upper level device running, the underlying device must be in the primary role."
3141 msgstr "要使堆叠的上层设备运行,底层设备必须处于primary角色。"
3142
3143 #. type: Plain text
3144 msgid "To be able to synchronize the backup node, the stacked device on the active node must be up and in the primary role."
3145 msgstr "要同步备份节点,活动节点上的堆叠设备必须处于启动状态并且处于主要角色。"
3146
3147 #. type: Title ====
3148 #, no-wrap
3149 msgid "Configuring a stacked resource"
3150 msgstr "配置堆叠资源"
3151
3152 #. type: Plain text
3153 msgid ""
3154 "In the following example, nodes are named 'alice', 'bob', and 'charlie', with 'alice' and 'bob' forming a two-node cluster, and "
3155 "'charlie' being the backup node."
3156 msgstr "在下面的示例中,节点名为 `alice` 、`bob` 和 `charlie` ,其中 `alice` 和 `bob` 组成一个两节点集群, `charlie` 是备份节点。"
3157
3158 #. type: delimited block -
3159 #, no-wrap
3160 msgid ""
3161 "resource r0 {\n"
3162 " protocol C;\n"
3163 " device /dev/drbd0;\n"
3164 " disk /dev/sda6;\n"
3165 " meta-disk internal;\n"
3166 msgstr ""
3167 "resource r0 {\n"
3168 " protocol C;\n"
3169 " device /dev/drbd0;\n"
3170 " disk /dev/sda6;\n"
3171 " meta-disk internal;\n"
3172
3173 #. type: delimited block -
3174 #, no-wrap
3175 msgid ""
3176 " on alice {\n"
3177 " address 10.0.0.1:7788;\n"
3178 " }\n"
3179 msgstr ""
3180 " on alice {\n"
3181 " address 10.0.0.1:7788;\n"
3182 " }\n"
3183
3184 #. type: delimited block -
3185 #, no-wrap
3186 msgid ""
3187 " on bob {\n"
3188 " address 10.0.0.2:7788;\n"
3189 " }\n"
3190 "}\n"
3191 msgstr ""
3192 " on bob {\n"
3193 " address 10.0.0.2:7788;\n"
3194 " }\n"
3195 "}\n"
3196
3197 #. type: delimited block -
3198 #, no-wrap
3199 msgid ""
3200 "resource r0-U {\n"
3201 " protocol A;\n"
3202 msgstr ""
3203 "resource r0-U {\n"
3204 " protocol A;\n"
3205
3206 #. type: delimited block -
3207 #, no-wrap
3208 msgid ""
3209 " stacked-on-top-of r0 {\n"
3210 " device /dev/drbd10;\n"
3211 " address 192.168.42.1:7789;\n"
3212 " }\n"
3213 msgstr ""
3214 " stacked-on-top-of r0 {\n"
3215 " device /dev/drbd10;\n"
3216 " address 192.168.42.1:7789;\n"
3217 " }\n"
3218
3219 #. type: delimited block -
3220 #, no-wrap
3221 msgid ""
3222 " on charlie {\n"
3223 " device /dev/drbd10;\n"
3224 " disk /dev/hda6;\n"
3225 " address 192.168.42.2:7789; # Public IP of the backup node\n"
3226 " meta-disk internal;\n"
3227 " }\n"
3228 "}\n"
3229 msgstr ""
3230 " on charlie {\n"
3231 " device /dev/drbd10;\n"
3232 " disk /dev/hda6;\n"
3233 " address 192.168.42.2:7789; # Public IP of the backup node\n"
3234 " meta-disk internal;\n"
3235 " }\n"
3236 "}\n"
3237
3238 #. type: Plain text
3239 msgid ""
3240 "As with any `drbd.conf` configuration file, this must be distributed across all nodes in the cluster -- in this case, three "
3241 "nodes. Notice the following extra keyword not found in an unstacked resource configuration:"
3242 msgstr ""
3243 "与任何 `drbd.conf` 配置文件一样,它必须分布在集群中的所有节点上 - 在本例中是三个节点。请注意,在未备份的资源配置中未找到以下额外关键"
3244 "字:"
3245
3246 #. type: Block title
3247 #, no-wrap
3248 msgid "`stacked-on-top-of`"
3249 msgstr "`stacked-on-top-of`"
3250
3251 #. type: Plain text
3252 msgid ""
3253 "This option informs DRBD that the resource which contains it is a stacked resource. It replaces one of the `on` sections normally "
3254 "found in any resource configuration. Do not use `stacked-on-top-of` in an lower-level resource."
3255 msgstr ""
3256 "此选项通知DRBD包含它的资源是堆叠资源。它替换了通常在任何资源配置中找到的 `on` 部分之一。不要在较低级别的资源中使用 `stacked-on-top-"
3257 "of` 。"
3258
3259
3260 #. type: Plain text
3261 msgid ""
3262 "It is not a requirement to use <<fp-protocol-a,Protocol A>> for stacked resources. You may select any of DRBD's replication "
3263 "protocols depending on your application."
3264 msgstr "对于堆叠资源,不需要使用<<fp-protocol-a,Protocol A>>。您可以根据您的应用程序选择任何DRBD的复制协议。"
3265
3266
3267 #. type: Block title
3268 #, no-wrap
3269 msgid "Single stacked setup"
3270 msgstr "单堆叠设置"
3271
3272 #. type: Target for macro image
3273 #, no-wrap
3274 msgid "images/single-stacked.svg"
3275 msgstr "images/single-stacked.svg"
3276
3277 #. type: Title ====
3278 #, no-wrap
3279 msgid "Enabling stacked resources"
3280 msgstr "启用堆叠资源"
3281
3282 #. type: Plain text
3283 msgid ""
3284 "To enable a stacked resource, you first enable its lower-level resource and "
3285 "promote it:"
3286 msgstr ""
3287 "如果要启用堆叠资源,请先启用底层级别"
3288 "的资源后, 并将其提升:"
3289
3290 #. type: delimited block -
3291 #, no-wrap
3292 msgid ""
3293 "drbdadm up r0\n"
3294 "drbdadm primary r0\n"
3295 msgstr ""
3296 "drbdadm up r0\n"
3297 "drbdadm primary r0\n"
3298
3299 #. type: Plain text
3300 msgid ""
3301 "As with unstacked resources, you must create DRBD meta data on the stacked resources. This is done using the following command:"
3302 msgstr "与未堆叠的资源一样,必须在堆叠的资源上创建DRBD元数据。使用以下命令完成此操作:"
3303
3304 #. type: delimited block -
3305 #, no-wrap
3306 msgid "# drbdadm create-md --stacked r0-U\n"
3307 msgstr "# drbdadm create-md --stacked r0-U\n"
3308
3309 #. type: Plain text
3310 msgid "Then, you may enable the stacked resource:"
3311 msgstr "然后,可以启用堆叠资源:"
3312
3313 #. type: delimited block -
3314 #, no-wrap
3315 msgid ""
3316 "# drbdadm up --stacked r0-U\n"
3317 "# drbdadm primary --stacked r0-U\n"
3318 msgstr ""
3319 "# drbdadm up --stacked r0-U\n"
3320 "# drbdadm primary --stacked r0-U\n"
3321
3322 #. type: Plain text
3323 msgid "After this, you may bring up the resource on the backup node, enabling three-node replication:"
3324 msgstr "之后,您可以在备份节点上调出资源,启用三节点复制:"
3325
3326 #. type: delimited block -
3327 #, no-wrap
3328 msgid ""
3329 "# drbdadm create-md r0-U\n"
3330 "# drbdadm up r0-U\n"
3331 msgstr ""
3332 "# drbdadm create-md r0-U\n"
3333 "# drbdadm up r0-U\n"
3334
3335 #. type: Plain text
3336 msgid ""
3337 "In order to automate stacked resource management, you may integrate stacked resources in your cluster manager configuration. See "
3338 "<<s-pacemaker-stacked-resources>> for information on doing this in a cluster managed by the Pacemaker cluster management "
3339 "framework."
3340 msgstr ""
3341 "为了自动化堆叠资源管理,可以在群集管理器配置中集成堆叠资源。有关在Pacemaker群集管理框架管理的群集中执行此操作的信息,请参见<<s-"
3342 "pacemaker-stacked-resources>>。"
3343
3344 #. type: Title ===
3345 #, no-wrap
3346 msgid "Permanently diskless nodes"
3347 msgstr "永久无盘节点"
3348
3349 #. type: Plain text
3350 msgid ""
3351 "A node might be permanently diskless in DRBD. Here is a configuration example showing a resource with 3 diskful nodes (servers) "
3352 "and one permanently diskless node (client)."
3353 msgstr ""
3354 "在DRBD中,节点可能是永久无盘的。下面是一个配置示例,显示一个具有3个diskful节点(服务器)和一个永久无磁盘节点(客户端)的资源。"
3355
3356 #. type: delimited block -
3357 #, no-wrap
3358 msgid ""
3359 "resource kvm-mail {\n"
3360 " device /dev/drbd6;\n"
3361 " disk /dev/vg/kvm-mail;\n"
3362 " meta-disk internal;\n"
3363 msgstr ""
3364 "resource kvm-mail {\n"
3365 " device /dev/drbd6;\n"
3366 " disk /dev/vg/kvm-mail;\n"
3367 " meta-disk internal;\n"
3368
3369 #. type: delimited block -
3370 #, no-wrap
3371 msgid ""
3372 " on store1 {\n"
3373 " address 10.1.10.1:7006;\n"
3374 " node-id 0;\n"
3375 " }\n"
3376 " on store2 {\n"
3377 " address 10.1.10.2:7006;\n"
3378 " node-id 1;\n"
3379 " }\n"
3380 " on store3 {\n"
3381 " address 10.1.10.3:7006;\n"
3382 " node-id 2;\n"
3383 " }\n"
3384 msgstr ""
3385 " on store1 {\n"
3386 " address 10.1.10.1:7006;\n"
3387 " node-id 0;\n"
3388 " }\n"
3389 " on store2 {\n"
3390 " address 10.1.10.2:7006;\n"
3391 " node-id 1;\n"
3392 " }\n"
3393 " on store3 {\n"
3394 " address 10.1.10.3:7006;\n"
3395 " node-id 2;\n"
3396 " }\n"
3397
3398 #. type: delimited block -
3399 #, no-wrap
3400 msgid ""
3401 " on for-later-rebalancing {\n"
3402 " address 10.1.10.4:7006;\n"
3403 " node-id 3;\n"
3404 " }\n"
3405 msgstr ""
3406 " on for-later-rebalancing {\n"
3407 " address 10.1.10.4:7006;\n"
3408 " node-id 3;\n"
3409 " }\n"
3410
3411 #. type: delimited block -
3412 #, no-wrap
3413 msgid ""
3414 " # DRBD \"client\"\n"
3415 " floating 10.1.11.6:8006 {\n"
3416 " disk none;\n"
3417 " node-id 4;\n"
3418 " }\n"
3419 msgstr ""
3420 " # DRBD \"client\"\n"
3421 " floating 10.1.11.6:8006 {\n"
3422 " disk none;\n"
3423 " node-id 4;\n"
3424 " }\n"
3425
3426 #. type: delimited block -
3427 #, no-wrap
3428 msgid ""
3429 " # rest omitted for brevity\n"
3430 " ...\n"
3431 "}\n"
3432 msgstr ""
3433 " # rest omitted for brevity\n"
3434 " ...\n"
3435 "}\n"
3436
3437 #. type: Plain text
3438 msgid ""
3439 "For permanently diskless nodes no bitmap slot gets allocated. For such nodes the diskless status is displayed in green color "
3440 "since it is not an error or unexpected state."
3441 msgstr "对于永久无盘节点,不分配位图插槽。对于此类节点,无盘状态显示为绿色,因为它不是错误或意外状态。"
3442
3443 #. type: delimited block =
3444 msgid ""
3445 "This _DRBD client_ is an easy way to get data over the wire, but it doesn't have any of the advanced iSCSI features like "
3446 "_Persistent Reservations_. + If your setup has only basic I/O needs, like _read_, _write_, _trim_/_discard_ and perhaps _resize_ "
3447 "(e.g. for a virtual machine), you should be fine."
3448 msgstr ""
3449 "这个 _DRBD cliet_ 是一种通过网络获取数据的简单方法,但它没有任何高级的iSCSI功能,比如 _Persistent Reservations_。 + 如果您的设置只需要基本的I/O需求,比如"
3450 " _read_, _write_, _trim_/_discard_ 又或是 _resize_ "
3451 "(比如虚拟机),它应该会运转正常并满足基本的工作需求。"
3452
3453 #. type: Title ===
3454 #, no-wrap
3455 msgid "Data rebalancing"
3456 msgstr "数据再平衡"
3457
3458 #. type: Plain text
3459 msgid ""
3460 "indexterm:[rebalance]Given the (example) policy that data needs to be available on 3 nodes, you need at least 3 servers for your "
3461 "setup."
3462 msgstr "indexterm:[rebalance]考虑到(示例)策略,即数据需要在3个节点上可用,您的设置至少需要3个服务器。"
3463
3464 #. type: Plain text
3465 msgid ""
3466 "Now, as your storage demands grow, you will encounter the need for additional servers. Rather than having to buy 3 more servers "
3467 "at the same time, you can _rebalance_ your data across a single additional node."
3468 msgstr "现在,随着存储需求的增长,您将需要更多的服务器。不必同时购买3台以上的服务器,您可以在一个额外的节点上重新平衡数据。"
3469
3470 #. type: Block title
3471 #, no-wrap
3472 msgid "DRBD data rebalancing"
3473 msgstr "DRBD数据再平衡"
3474
3475 #. type: Target for macro image
3476 #, no-wrap
3477 msgid "images/rebalance.svg"
3478 msgstr "images/rebalance.svg"
3479
3480 #. type: Plain text
3481 msgid ""
3482 "In the figure above you can see the _before_ and _after_ states: from 3 nodes with three 25TiB volumes each (for a net 75TiB), to "
3483 "4 nodes, with net 100TiB."
3484 msgstr "在上图中,您可以看到 _before_ 和 _after_ 状态:从3个节点(每个节点有3个25TiB卷)(净容量 75TiB)到4个节点(净容量 100TiB)。"
3485
3486 #. type: Plain text
3487 msgid ""
3488 "To redistribute the data across your cluster you have to choose a _new_ node, and one where you want to remove this DRBD "
3489 "resource. + Please note that removing the resource from a currently _active_ node (i.e. where DRBD is _Primary_) will involve "
3490 "either migrating the service or running this resource on this node as a <<s-drbd-client,DRBD client>>; it's easier to choose a "
3491 "node in _Secondary_ role. (Of course, that might not always be possible.)"
3492 msgstr ""
3493 "要在集群中重新分配数据,必须选择一个 _新_ 的节点,以及一个要删除此DRBD资源的节点。+ 请注意,从当前 _活动_ 节点(即DRBD中 _主节点_ )中删除资源"
3494 "将涉及迁移服务或作为<<s-drbd-client,DRBD client>>在此节点上运行此资源;更容易选择处于 _次要角色_ 的节点。(当然,这并不总是可能的。)"
3495
3496 #. type: Title ====
3497 #, no-wrap
3498 msgid "Prepare a bitmap slot"
3499 msgstr "准备位图插槽"
3500
3501 #. type: Plain text
3502 msgid ""
3503 "You will need to have a free <<s-quick-sync-bitmap,bitmap slot>> for temporary use, on each of the nodes that have the resource "
3504 "that is to be moved."
3505 msgstr "您需要在每个具有要移动的资源的节点上有一个空闲的<<s-quick-sync-bitmap,bitmap slot>>供临时使用。"
3506
3507 #. type: Plain text
3508 msgid ""
3509 "You can allocate one more at <<s-first-time-up,`drbdadm create-md` time>>, or simply put a placeholder in your configuration, so "
3510 "that `drbdadm` sees that it should reserve one more slot:"
3511 msgstr ""
3512 "您可以使用<<s-first-time-up,`drbdadm create-md` time>>再分配一个,或者只需在您的配置中放置一个占位符,这样 `drbdadm` 看到后就会"
3513 "再保留一个插槽:"
3514
3515 #. type: delimited block -
3516 #, no-wrap
3517 msgid ""
3518 "resource r0 {\n"
3519 " ...\n"
3520 " on for-later-rebalancing {\n"
3521 " address 10.254.254.254:65533;\n"
3522 " node-id 3;\n"
3523 " }\n"
3524 "}\n"
3525 msgstr ""
3526 "resource r0 {\n"
3527 " ...\n"
3528 " on for-later-rebalancing {\n"
3529 " address 10.254.254.254:65533;\n"
3530 " node-id 3;\n"
3531 " }\n"
3532 "}\n"
3533
3534 #. type: delimited block =
3535 msgid "If you need to make that slot available during live use, you will have to"
3536 msgstr "如果您需要在实时使用期间提供该插槽,则必须"
3537
3538 #. type: delimited block =
3539 msgid "dump the metadata,"
3540 msgstr "转储元数据,"
3541
3542 #. type: delimited block =
3543 msgid "enlarge the metadata space,"
3544 msgstr "扩大元数据空间,"
3545
3546 #. type: delimited block =
3547 msgid "edit the dumpfile,"
3548 msgstr "编辑转储文件,"
3549
3550 #. type: delimited block =
3551 msgid "load the changed metadata."
3552 msgstr "加载更改后的元数据。"
3553
3554 #. type: delimited block =
3555 msgid ""
3556 "In a future version `drbdadm` will have a shortcut for you; most probably you'll be able to say `drbdadm resize --peers _N_` and "
3557 "have the kernel rewrite the metadata for you."
3558 msgstr "在未来的版本中,`drbdadm` 将为您提供一个快捷方式;很可能您可以通过使用 `drbdadm resize--peers _N_` ,并让内核为您重写元数据。"
3559
3560 #. type: Title ====
3561 #, no-wrap
3562 msgid "Preparing and activating the new node"
3563 msgstr "准备和激活新节点"
3564
3565 #. type: Plain text
3566 msgid ""
3567 "First of all you have to create the underlying storage volume on the new node (using e.g. `lvcreate`). Then the placeholder in "
3568 "the configuration can be filled with the correct host name, address, and storage path. Now copy the resource configuration to all "
3569 "relevant nodes."
3570 msgstr ""
3571 "首先,您必须在新节点上创建基础存储卷(使用例如 `lvcreate` )。然后,可以用正确的主机名、地址和存储路径填充配置中的占位符。现在将资源"
3572 "配置复制到所有相关节点。"
3573
3574 #. type: Plain text
3575 msgid "On the new node initialize the meta-data (once) by doing"
3576 msgstr "在新节点上,通过执行以下操作初始化元数据(一次)"
3577
3578 #. type: delimited block -
3579 #, no-wrap
3580 msgid ""
3581 "# drbdadm create-md <resource>\n"
3582 "v09 Magic number not found\n"
3583 "Writing meta data...\n"
3584 "initialising activity log\n"
3585 "NOT initializing bitmap\n"
3586 "New drbd meta data block sucessfully created.\n"
3587 msgstr ""
3588 "# drbdadm create-md <resource>\n"
3589 "v09 Magic number not found\n"
3590 "Writing meta data...\n"
3591 "initialising activity log\n"
3592 "NOT initializing bitmap\n"
3593 "New drbd meta data block sucessfully created.\n"
3594
3595 #. type: Title ====
3596 #, no-wrap
3597 msgid "Starting the initial sync"
3598 msgstr "开始初始同步"
3599
3600 #. type: Plain text
3601 msgid "Now the new node needs to get the data."
3602 msgstr "现在新节点需要获取数据。"
3603
3604 #. type: Plain text
3605 msgid "This is done by defining the network connection on the existing nodes via"
3606 msgstr "通过定义现有节点上的网络连接来完成操作"
3607
3608 #. type: Plain text
3609 msgid "and starting the DRBD device on the new node via"
3610 msgstr "然后启动新节点上的DRBD设备"
3611
3612 #. type: Title ====
3613 #, no-wrap
3614 msgid "Check connectivity"
3615 msgstr "检查连接"
3616
3617 #. type: Plain text
3618 msgid "At this time please do a"
3619 msgstr "现在运行"
3620
3621 #. type: delimited block -
3622 #, no-wrap
3623 msgid "# drbdadm status <resource>\n"
3624 msgstr "# drbdadm status <resource>\n"
3625
3626 #. type: Plain text
3627 msgid "on the new node, and check that _all_ other nodes are connected."
3628 msgstr "在新节点上,检查是否连接了所有其他节点。"
3629
3630 #. type: Title ====
3631 #, no-wrap
3632 msgid "After the initial sync"
3633 msgstr "初始同步后"
3634
3635 #. type: Plain text
3636 msgid ""
3637 "As soon as the new host is _UpToDate_, one of the other nodes in the configuration can be renamed to `for-later-rebalancing`, and "
3638 "kept for another migration."
3639 msgstr "只要新主机是 _UpToDate_ 的,配置中的其他节点之一就可以重命名为 `for-later-rebalancing` ,并保留以进行另一次迁移。"
3640
3641 #. type: Plain text
3642 msgid ""
3643 "Perhaps you want to comment the section; although that has the risk that doing a `drbdadm create-md` for a new node has too few "
3644 "bitmap slots for the next rebalancing. + It might be easier to use a reserved (unused) IP address and host name."
3645 msgstr ""
3646 "也许您想对该节进行注释;尽管这样做的风险是,为新节点执行 `drbdadm create md` 时,下次重新平衡的位图插槽太少。+ 使用保留(未使用)的IP"
3647 "地址和主机名可能更容易。"
3648
3649 #. type: Plain text
3650 msgid "Copy the changed configuration around again, and use it by running"
3651 msgstr "再次复制更改的配置,并运行如下命令"
3652
3653 #. type: Plain text
3654 msgid "on all nodes."
3655 msgstr "在所有节点上。"
3656
3657 #. type: Title ====
3658 #, no-wrap
3659 msgid "Cleaning up"
3660 msgstr "清理"
3661
3662 #. type: Plain text
3663 msgid ""
3664 "On the one node that had the data up to now, but isn't used anymore for this resource, you can now take the DRBD device down by "
3665 "starting"
3666 msgstr "在目前拥有数据但不再用于此资源的一个节点上,现在可以通过启动"
3667
3668 #. type: Plain text
3669 msgid ""
3670 "Now the lower level storage device isn't used anymore, and can either be re-used for other purposes or, if it is a logical "
3671 "volume, its space can be returned to the volume group via `lvremove`."
3672 msgstr "现在,较低级别的存储设备不再使用,可以重新用于其他目的,或者,如果它是逻辑卷,则可以通过 `lvremove` 将其空间返回给卷组。"
3673
3674 #. type: Title ====
3675 #, no-wrap
3676 msgid "Conclusion and further steps"
3677 msgstr "结论和进一步步骤"
3678
3679 #. type: Plain text
3680 msgid ""
3681 "One of the resources has been migrated to the new node. The same could be done for one or more other resources, to free space on "
3682 "two or three nodes in the existing cluster."
3683 msgstr "其中一个资源已迁移到新节点。对于一个或多个其他资源也可以这样做,以释放现有集群中两个或三个节点上的空间。"
3684
3685 #. type: Plain text
3686 msgid "Then new resources can be configured, as there're enough nodes with free space to achieve 3-way redundancy again."
3687 msgstr "然后可以配置新的资源,因为有足够的空闲空间节点可以再次实现3路冗余。"
3688
3689 #. type: Plain text
3690 msgid "Still, you might want to compare the steps above with the procedure when using DRBD Manage: <<s-dm-rebalance>>..."
3691 msgstr "不过,在使用DRBD Manage时,您可能需要将上述步骤与过程进行比较: <<s-dm-rebalance>>..."
3692
3693 #. type: Title ===
3694 #, no-wrap
3695 msgid "Configuring quorum"
3696 msgstr "配置仲裁"
3697
3698 #. type: Plain text
3699 msgid ""
3700 "In order to avoid split brain or diverging data of replicas one has to configure fencing. All the options for fencing rely on "
3701 "redundant communication in the end. That might be in the form of a management network that connects the nodes to the IPMI "
3702 "network interfaces of the peer machines. In case of the crm-fence-peer script it is necessary that Pacemakers communication stays "
3703 "available when DRBD's network link breaks."
3704 msgstr ""
3705 "为了避免复制品的裂脑或数据分散,必须配置围栏。所有的围栏策略最终都依赖于冗余通信。这可能是一个管理网络的形式,它将节点连接到对"
3706 "等机的IPMI网络接口。在crm-fence-peer脚本的情况下,当DRBD的网络链路断开时,Pacemakers通信必须保持可用。"
3707
3708 #. type: Plain text
3709 msgid ""
3710 "The quorum mechanism on the other hand takes a completely difference approach. The basic idea is that a cluster partition may "
3711 "only modify the replicated data set if the number of nodes that can communicate is greater then the half of the overall number of "
3712 "nodes. A node of such a partition _has quorum_. On the other hand a node does not have quorum needs to guarantee that the "
3713 "replicated data set it not touched, that it does not create a diverging data set."
3714 msgstr ""
3715 "另一方面,仲裁机制则采取了完全不同的做法。基本思想是,如果可以通信的节点数大于总节点数的一半,那么集群分区只能修改复制的数据集。具备这"
3716 "样一个分区的节点 _具有仲裁_。另一方面,一个没有仲裁权的节点需要保证它没有接触到复制的数据集,它不会创建一个发散的数据集。"
3717
3718 #. type: Plain text
3719 msgid ""
3720 "The quorum implementation in DRBD gets enabled by setting the `quorum` resource option to `majority`, `all` or a numeric value. "
3721 "Where `majority` selects the behavior that was described in the previous paragraph."
3722 msgstr "通过将 `quorum` 资源选项设置为 `majority` 、`all` 或某个数值,可以启用DRBD中的仲裁实现。其中 `majority` 就是上一段中描述的行为。"
3723
3724 #. type: Title ====
3725 #, no-wrap
3726 msgid "Guaranteed minimal redundancy"
3727 msgstr "保证最小冗余"
3728
3729 #. type: Plain text
3730 msgid ""
3731 "By default every node with a disk gets a vote in the quorum election. In other words only diskless nodes do not count. So a "
3732 "partition with two _Inconsistent_ disks gets quorum, while a partition with one _UpToDate_ node will have quorum in a 3 node "
3733 "cluster. By configuring `quorum-minimum-redundancy` this behavior can be changed so that only nodes that are `UpToDate` have a "
3734 "vote in the quorum election. The option takes the same arguments as the `quorum` option."
3735 msgstr ""
3736 "默认情况下,具有磁盘的每个节点都可以在仲裁选举中获得投票权。换句话说,只有无盘节点不计算在内。因此,具有两个 _不一致磁盘_ 的分区将获得"
3737 "仲裁,而具有一个 _UpToDate_ 分区的节点将在3节点群集中具有仲裁。通过配置 `quorum minimum redundancy` ,可以更改此行为,以便使得只有 `UpToDate` 节点"
3738 "在quorum选举中有投票权。该选项采用与 `quorum` 选项相同的参数。"
3739
3740 #. type: Plain text
3741 msgid ""
3742 "With this option you express that you rather want to wait until eventually necessary resync operations finish before any services "
3743 "start. So in a way you prefer that the minimal redundancy of your data is guaranteed over the availability of your service. "
3744 "Financial data and services is an example that comes to mind."
3745 msgstr ""
3746 "使用此选项,表示您更希望等到最终必要的重新同步操作完成后再启动任何服务。因此,在某种程度上,您希望数据的最小冗余比服务的可用"
3747 "性得到保证。金融数据和服务就是一个浮现在脑海中的例子。"
3748
3749 #. type: Plain text
3750 msgid ""
3751 "Consider following example for a 5 node cluster. It requires a partitions to have at least 3 nodes, and two of them must be "
3752 "`UpToDate`:"
3753 msgstr "考虑以下5节点集群的示例。它要求一个分区至少有3个节点,其中两个必须是 `UpToDate`:"
3754
3755 #. type: delimited block -
3756 #, no-wrap
3757 msgid ""
3758 "resource quorum-demo {\n"
3759 " quorum majority;\n"
3760 " quorum-minimum-redundancy 2;\n"
3761 " ...\n"
3762 "}\n"
3763 msgstr ""
3764 "resource quorum-demo {\n"
3765 " quorum majority;\n"
3766 " quorum-minimum-redundancy 2;\n"
3767 " ...\n"
3768 "}\n"
3769
3770 #. type: Title ====
3771 #, no-wrap
3772 msgid "Actions on loss of quorum"
3773 msgstr "丧失仲裁后的动作"
3774
3775 #. type: Plain text
3776 msgid ""
3777 "When a node that is running the service loses quorum it needs to cease write-operations on the data set immediately. That means "
3778 "that IO immediately starts to complete all IO requests with errors. Usually that means that a graceful shutdown is not possible, "
3779 "since that would require more modifications to the data set. The IO errors propagate from the block level to the file system and "
3780 "from the file system to the user space application(s)."
3781 msgstr ""
3782 "当运行服务的节点失去仲裁时,它需要立即停止对数据集的写操作。这意味着IO会立即开始完成所有有错误的IO请求。通常这意味着不可能正常关"
3783 "闭,因为这需要对数据集进行更多修改。IO错误从块级别传播到文件系统,从文件系统传播到用户空间应用程序。"
3784
3785 #. type: Plain text
3786 msgid ""
3787 "Ideally the application simply terminates in case of IO errors. This allows then Pacemaker to unmount the filesystem and to "
3788 "demote the DRBD resource to secondary role. If that is true you should set the `on-no-quorum` resource option to `io-error`. "
3789 "Here is an example:"
3790 msgstr ""
3791 "理想情况下,应用程序会在IO错误时终止。这允许Pacemaker卸载文件系统并将DRBD资源降级为次要角色。如果是这样,则应将 `on-no-quorum` 资"
3792 "源选项设置为 `io-error` 。下面是一个例子:"
3793
3794 #. type: delimited block -
3795 #, no-wrap
3796 msgid ""
3797 "resource quorum-demo {\n"
3798 " quorum majority;\n"
3799 " on-no-quorum io-error;\n"
3800 " ...\n"
3801 "}\n"
3802 msgstr ""
3803 "resource quorum-demo {\n"
3804 " quorum majority;\n"
3805 " on-no-quorum io-error;\n"
3806 " ...\n"
3807 "}\n"
3808
3809 #. type: Plain text
3810 msgid ""
3811 "If you application does not terminate on the first IO error, you can choose to freeze IO instead and to reboot the node. Here is "
3812 "a configuration example:"
3813 msgstr "如果应用程序未在第一个IO错误时终止,则可以选择冻结IO并重新启动节点。下面是一个配置示例:"
3814
3815 #. type: delimited block -
3816 #, no-wrap
3817 msgid ""
3818 "resource quorum-demo {\n"
3819 " quorum majority;\n"
3820 " on-no-quorum suspend-io;\n"
3821 " ...\n"
3822 msgstr ""
3823 "resource quorum-demo {\n"
3824 " quorum majority;\n"
3825 " on-no-quorum suspend-io;\n"
3826 " ...\n"
3827
3828 #. type: delimited block -
3829 #, no-wrap
3830 msgid ""
3831 " handlers {\n"
3832 " quorum-lost \"echo b > /proc/sysrq-trigger\";\n"
3833 " }\n"
3834 " ...\n"
3835 "}\n"
3836 msgstr ""
3837 " handlers {\n"
3838 " quorum-lost \"echo b > /proc/sysrq-trigger\";\n"
3839 " }\n"
3840 " ...\n"
3841 "}\n"
3842
3843 #. type: Title ====
3844 #, no-wrap
3845 msgid "Using a diskless node as a tiebreaker"
3846 msgstr "使用无盘节点作为分层断路器"
3847
3848 #. type: Plain text
3849 msgid "A diskless node with connections to all nodes in a cluster can be utilized to break ties in the quorum negotiation process."
3850 msgstr "在仲裁协商过程中,可以使用连接到群集中所有节点的无盘节点来断开连接。"
3851
3852 #. type: Plain text
3853 msgid "Consider the following two-node cluster, where node A is the primary and node B is a secondary:"
3854 msgstr "考虑以下两个节点群集,其中节点A是主节点,节点B是次节点:"
3855
3856 #. type: Target for macro image
3857 #, no-wrap
3858 msgid "images/quorum-tiebreaker-without.svg"
3859 msgstr "images/quorum-tiebreaker-without.svg"
3860
3861 #. type: Plain text
3862 msgid ""
3863 "As soon as the connection between the two nodes is interrupted, they lose quorum and the application on top of the cluster cannot "
3864 "write data anymore."
3865 msgstr "一旦两个节点之间的连接中断,它们就会失去仲裁,并且集群顶部的应用程序无法再写入数据。"
3866
3867 #. type: Target for macro image
3868 #, no-wrap
3869 msgid "images/quorum-tiebreaker-without-disconnect.svg"
3870 msgstr "images/quorum-tiebreaker-without-disconnect.svg"
3871
3872 #. type: Plain text
3873 msgid ""
3874 "Now if we add a third node, C, to the cluster and configure it as diskless, we can take advantage of the tiebreaker mechanism."
3875 msgstr "现在,如果我们将第三个节点C添加到集群并将其配置为无磁盘节点,我们就可以利用tiebraker机制。"
3876
3877 #. type: Target for macro image
3878 #, no-wrap
3879 msgid "images/quorum-tiebreaker.svg"
3880 msgstr "images/quorum-tiebreaker.svg"
3881
3882 #. type: Plain text
3883 msgid ""
3884 "In this case, when the primary and secondary nodes lose connection, they can still \"see\" the diskless tiebreaker. Because of "
3885 "this, the primary can continue working, while the secondary demotes its disk to Outdated and the service can therefore not be "
3886 "migrated there."
3887 msgstr ""
3888 "在这种情况下,当主节点和辅助节点失去连接时,它们仍然可以 \"看到\" 无盘分层断路器。因此,主磁盘可以继续工作,而次磁盘将其磁盘降级为过期"
3889 "磁盘,因此无法在那里迁移服务。"
3890
3891 #. type: Target for macro image
3892 #, no-wrap
3893 msgid "images/quorum-tiebreaker-disconnect.svg"
3894 msgstr "images/quorum-tiebreaker-disconnect.svg"
3895
3896 #. type: Plain text
3897 msgid "There are a few special cases in case two connections fail. Consider the following scenario:"
3898 msgstr "有一些特殊情况,以防两个连接失败。考虑以下场景:"
3899
3900 #. type: Target for macro image
3901 #, no-wrap
3902 msgid "images/quorum-tiebreaker-disconnect-case2.svg"
3903 msgstr "images/quorum-tiebreaker-disconnect-case2.svg"
3904
3905 #. type: Plain text
3906 msgid ""
3907 "In this case, the tiebreaker node forms a partition with the primary node. The primary therefore keeps quorum, while the "
3908 "secondary becomes outdated. Note that the secondarys disk state will be \"UpToDate\", but regardless it cannot be promoted to "
3909 "primary because it lacks quorum."
3910 msgstr ""
3911 "在这种情况下,tiebreaker节点与主节点形成一个分区。因此,主服务器保留仲裁,而次服务器过时。请注意,secondarys磁盘状态将为 \"UpToDate\",但"
3912 "无论如何都不能将其提升为primary,因为它缺少仲裁。"
3913
3914 #. type: Plain text
3915 msgid "Let's consider the possibility of the primary losing connection to the tiebreaker:"
3916 msgstr "让我们考虑一下主断路器断开连接的可能性:"
3917
3918 #. type: Target for macro image
3919 #, no-wrap
3920 msgid "images/quorum-tiebreaker-disconnect-case3.svg"
3921 msgstr "images/quorum-tiebreaker-disconnect-case3.svg"
3922
3923 #. type: Plain text
3924 msgid ""
3925 "In this case, the primary becomes unusable and goes into a \"quorum suspended\" state. This effectively results in the "
3926 "application on top of DRBD receiving I/O errors. A cluster manager could then promote node B to primary and keep the service "
3927 "running there instead."
3928 msgstr ""
3929 "在这种情况下,主服务器将变得不可用,并进入 \"quorum suspended\" 状态。这有效地导致应用程序在DRBD之上接收I/O错误。然后,集群管理器可以"
3930 "将节点B提升为主节点,并使服务在那里运行。"
3931
3932 #. type: Plain text
3933 msgid "In case the diskless tiebreaker \"switches sides\", we need to avoid data divergence. Consider this scenario:"
3934 msgstr "如果无盘分层断路器 \"切换侧\",则需要避免数据发散。考虑这个场景:"
3935
3936 #. type: Target for macro image
3937 #, no-wrap
3938 msgid "images/quorum-tiebreaker-disconnect-case1a.svg"
3939 msgstr "images/quorum-tiebreaker-disconnect-case1a.svg"
3940
3941 #. type: Plain text
3942 msgid ""
3943 "The connection between the primary and secondary has failed, and the application is continuing to run on the primary, when the "
3944 "primary suddenly loses its connection to the diskless node."
3945 msgstr "主节点和辅助节点之间的连接失败,应用程序继续在主节点上运行,此时主节点突然失去与无盘节点的连接。"
3946
3947 #. type: Plain text
3948 msgid "In this case, no node can be promoted to primary and the cluster cannot continue to operate."
3949 msgstr "在这种情况下,无法将任何节点升级到主节点,并且群集无法继续运行。"
3950
3951 #. type: delimited block =
3952 msgid "Protecting from data divergence always takes priority over ensuring service availability."
3953 msgstr "防止数据差异始终优先于确保服务可用性。"
3954
3955 #. type: Plain text
3956 msgid "Let's look at another scenario:"
3957 msgstr "让我们看看另一个场景:"
3958
3959 #. type: Target for macro image
3960 #, no-wrap
3961 msgid "images/quorum-tiebreaker-disconnect-case2a.svg"
3962 msgstr "images/quorum-tiebreaker-disconnect-case2a.svg"
3963
3964 #. type: Plain text
3965 msgid ""
3966 "Here, the application is running on the primary, while the secondary is unavailable. Then, the tiebreaker first loses connection "
3967 "to the primary, and then reconnects to the secondary. It is important to note here that *a node that has lost quorum cannot "
3968 "regain quorum by connecting to a diskless node*. Thus, in this case, no node has quorum and the cluster halts."
3969 msgstr ""
3970 "在这里,应用程序在主服务器上运行,而辅助服务器不可用。然后,tiebraker首先断开与主节点的连接,然后重新连接到辅助节点。这里需要注意"
3971 "的是, *失去仲裁的节点无法通过连接到无盘节点* 来重新获得仲裁。因此,在这种情况下,没有节点具有仲裁,集群将停止。"
3972
3973 #. type: Title ====
3974 #, no-wrap
3975 msgid "Last man standing"
3976 msgstr "最后站着的人"
3977
3978 #. type: Plain text
3979 msgid ""
3980 "It needs to be mentioned that nodes that leave a cluster gracefully are counted different than failed nodes. In this context "
3981 "_leaving gracefully_ means that the leaving node marked it's data as Outdated, and that it was able to tell the remaining nodes "
3982 "that it's data is Outdated."
3983 msgstr ""
3984 "需要指出的是,优雅地离开集群的节点与失败节点的计数不同。在此上下文中, _优雅地离开_ 意味着离开节点将其数据标记为过时,并且它能够告诉其"
3985 "余节点其数据已过时。"
3986
3987 #. type: Plain text
3988 msgid ""
3989 "In a group of nodes where all disks are Outdated no one in that group can promote to Primary footnote:[The exception is a manual "
3990 "promotion with the --force flag. We assume that one that uses the --force knows what he is doing.]."
3991 msgstr ""
3992 "在所有磁盘都已过期的节点组中,该组中的任何人都无法升级到主角色 footnote:[例外情况是使用--force标志进行手动升级。我们假设使用--force的人知道他"
3993 "在做什么]。"
3994
3995 #. type: Plain text
3996 msgid ""
3997 "An implication is that, if a cluster is left by all but one node, it can keep quorum as long as all the others left in a graceful "
3998 "way. If a single node leaves ungraceful, it has to assume that all away nodes form a patition and have access to up-to-date data. "
3999 "If the other partition might (potentially) be larger than my own partition it looses quorum."
4000 msgstr ""
4001 "这意味着,如果一个集群只剩下一个节点,那么只要其他所有节点都以优雅的方式离开,它就可以保留仲裁。如果一个节点没有运行,它必须假设所"
4002 "有离开的节点都形成一个patition并可以访问最新的数据。如果另一个分区可能(潜在地)比其自身的分区大,那么它将释放仲裁。"