yast2-drbd is not part of openSUSE Leap 15. It exists only in openSUSE Tumbleweed and enterprise products.

Component Approved Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
master GPL-2.0 1% 40% 5,376 73,900 511,044 3,643 584 49 0
Glossary yast-drbd GPL-2.0 50% 0 0 0 0 0 0 0

Overview

Project website github.com/yast/yast-drbd
Project maintainers User avatar ancorgonzalezsosa
12 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 9,011 110,651 774,174
Source 118 1,438 10,062
Approved 1% 8 1% 1,092 1% 7,256
Waiting for review 38% 3,509 31% 34,221 31% 245,812
Translated 40% 3,635 33% 36,751 33% 263,130
Needs editing 19% 1,733 7% 8,733 9% 69,952
Read-only 1% 118 1% 1,438 1% 10,062
Failing checks 6% 584 4% 4,991 4% 36,784
Strings with suggestions 1% 49 1% 1,165 1% 7,953
Untranslated strings 40% 3,643 58% 65,167 56% 441,092
Last 12 months Previous

Activity in last 12 months

5 changes 7 changes 62 changes 0 changes 0 changes 0 changes 0 changes 6 changes 166 changes 0 changes 3 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 114 changes 0 changes 0 changes 7 changes 0 changes
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov

Quick numbers

110 k
Hosted words
9,011
Hosted strings
40%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+40%
—
Contributors
—
Language Approved Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English 0 0 0 0 66 0 0
Afrikaans 0% 13% 101 1,339 9,207 39 11 0 0
Albanian 0% 70% 35 1,056 6,967 35 3 0 0
Amharic 0% 0% 117 1,437 10,054 117 0 0 0
Arabic 0% 99% 1 14 95 1 4 0 0
Asturian 0% 5% 110 1,424 9,968 86 8 0 0
Basque 0% 0% 117 1,437 10,054 117 0 0 0
Belarusian 0% 3% 113 1,429 9,998 79 13 0 0
Bengali 0% 13% 101 1,339 9,207 38 18 0 0
Bosnian 0% 1% 116 1,436 10,046 59 17 0 0
Bulgarian 0% 10% 105 1,385 9,620 38 19 0 0
Burmese 0% 0% 117 1,437 10,054 117 0 0 0
Catalan 0% 0 0 0 0 0 0 0
Chinese (China) (zh_CN) 1% 0 0 0 0 0 0 0
Chinese (Taiwan) (zh_TW) 1% 0 0 0 0 0 0 0
Croatian 0% 39% 71 1,194 8,087 37 10 0 0
Czech 0% 0 0 0 0 4 0 0
Danish 0% 81% 22 915 6,065 22 0 0 0
Dutch 0% 0 0 0 0 0 0 0
English (United Kingdom) 0% 22% 91 1,313 8,994 35 11 0 0
Esperanto 0% 0% 117 1,437 10,054 117 0 0 0
Estonian 0% 20% 93 1,321 9,051 37 13 0 0
Finnish 0% 81% 22 612 4,057 22 2 0 0
French 2% 0 0 0 0 2 0 0
Galician 0% 41% 68 1,177 7,973 49 11 48 0
Georgian 0% 73% 31 1,154 7,964 31 0 0 0
German 1% 0 0 0 0 2 0 0
German (Low) 0% 1% 116 1,436 10,046 99 2 0 0
Greek 0% 44% 65 1,167 7,907 58 7 0 0
Gujarati 0% 13% 101 1,339 9,207 39 27 0 0
Hebrew 0% 2% 114 1,434 10,023 53 24 0 0
Hindi 0% 22% 91 1,313 8,994 37 23 0 0
Hungarian 0% 98% 2 168 1,156 1 8 0 0
Indonesian 0% 0 0 0 0 1 0 0
Italian 0% 0 0 0 0 2 0 0
Japanese 0% 0 0 0 0 0 0 0
Javanese 0% 0% 117 1,437 10,054 117 0 0 0
Kannada 0% 0% 117 1,437 10,054 104 3 0 0
Khmer (Central) 0% 41% 68 1,177 7,973 30 13 0 0
Korean 0% 98% 2 168 1,156 1 1 0 0
Kurdish 0% 5% 111 1,426 9,968 86 8 0 0
Lao 0% 0% 117 1,437 10,054 117 0 0 0
Latvian 0% 0% 117 1,437 10,054 117 0 0 0
Lithuanian 0% 61% 45 1,103 7,229 33 10 0 0
Macedonian 0% 15% 99 1,321 9,075 48 3 0 0
Malay 0% 0% 117 1,437 10,054 116 0 0 0
Marathi 0% 13% 101 1,339 9,207 39 12 0 0
Nepali 0% 0% 117 1,437 10,054 117 0 0 0
Norwegian Bokmål (nb) 0% 43% 66 1,172 7,934 30 14 0 0
Norwegian Nynorsk 0% 0% 117 1,437 10,054 38 6 0 0
Pashto 0% 0% 117 1,437 10,054 117 0 0 0
Persian 0% 2% 114 1,430 10,006 93 5 0 0
Polish 0% 98% 2 168 1,156 1 2 0 0
Portuguese 0% 22% 91 1,313 8,994 56 10 0 0
Portuguese (Brazil) 0% 0 0 0 0 2 0 0
Punjabi 0% 20% 93 1,321 9,051 55 7 0 0
Romanian 0% 41% 68 1,177 7,973 31 13 0 0
Russian 0% 99% 1 14 95 1 4 0 0
Serbian 0% 2% 114 1,430 10,006 62 16 0 0
Serbian (latin) (sr@latin) 0% 0% 117 1,437 10,054 117 0 0 0
Sinhala 0% 0% 117 1,437 10,054 115 2 0 0
Slovak 0% 0 0 0 0 0 0 0
Slovenian 0% 7% 108 1,393 9,684 38 21 0 0
Spanish 0% 0 0 0 0 2 0 0
Swahili 0% 0% 117 1,437 10,054 117 0 0 0
Swedish 0% 0 0 0 0 1 1 0
Tajik 0% 2% 114 1,434 10,023 72 12 0 0
Tamil 0% 13% 101 1,339 9,207 39 24 0 0
Thai 0% 11% 104 1,347 9,274 38 10 0 0
Turkish 0% 0 0 0 0 0 0 0
Turkmen 0% 0% 117 1,437 10,054 117 0 0 0
Ukrainian 0% 99% 1 14 95 1 0 0 0
Vietnamese 0% 9% 106 1,349 9,286 42 14 0 0
Walloon 0% 6% 109 1,395 9,704 44 18 0 0
Welsh 0% 1% 115 1,435 10,038 53 21 0 0
Xhosa 0% 13% 101 1,339 9,207 39 11 0 0
Zulu 0% 13% 101 1,339 9,207 39 11 0 0
User avatar None

Changes committed
Changes committed 3 months ago
User avatar Yok

Translation changed

<p>"Name" is mandatory and must match the Linux host name (uname -n) of one of the nodes. Should not include "." in hostname.</p>
<p>"Address:Port": A resource needs one IP address per device, which is used to wait for incoming connections from the partner device to reach the device. Each DRBD resource needs a TCP port which is used to connect to the node's partner device. For IPv6, the actual address that follows the ipv6 keyword must be placed inside brackets: ipv6 [2001:1945:fc03:abcd::1]:7788</p>
<p>"Device": The name of the block device node of the resource being described. You must use this device with your application (file system) and you must not use the low level block device which is specified with the disk parameter,following its minor number. Otherwise, you may omit the name, or the word minor and its number. If you omit the name a default of /dev/drbd'minor number' will be used.
Like: '/dev/drbd{service} minor {minor drbd number [0...255]}' or '/dev/drbd{minor drbd number [0...255]}'</p>
<p>"Disk": DRBD uses this block device to actually store and retrieve the data. Never access such a device while DRBD is running on top of it.</p>
<p>"Meta-disk": internal. Internal means that the last part of the backing device is used to store the meta-data.</p>
<p>"Node-id": Node id is an internal value for drbd, will be generated by yast automatically. A host can have different "node-id" in different resources.</p>

<p>"Ad" zorunludur ve düğümlerden birinin Linux ana bilgisayar adıyla (uname -n) eşleşmelidir. Ana bilgisayar adına "." dahil edilmemelidir.</p>
<p>"Adres:Port": Bir kaynağın, ortak cihazdan gelen bağlantıların cihaza ulaşmasını beklemek için kullanılan cihaz başına bir IP adresine ihtiyacı vardır. Her DRBD kaynağının, düğümün ortak cihazına bağlanmak için kullanılan bir TCP portuna ihtiyacı vardır. IPv6 için, ipv6 anahtar kelimesini izleyen gerçek adres parantez içine yerleştirilmelidir: ipv6 [2001:1945:fc03:abcd::1]:7788</p>
<p>"Cihaz": Tanımlanan kaynağın blok cihaz düğümünün adı. Bu cihazı uygulamanız (dosya sistemi) ile birlikte kullanmalı ve disk parametresi ile küçük numarasından sonra belirtilen düşük seviyeli blok cihazını kullanmamalısınız. Aksi takdirde, adı veya minör kelimesini ve numarasını atlayabilirsiniz. Adı atlarsanız, varsayılan olarak /dev/drbd'minor number' kullanılacaktır.
Şöyle: '/dev/drbd{service} minor {minor drbd number [0...255]}' veya '/dev/drbd{minor drbd number [0...255]}'</p>
<p>"Disk": DRBD, verileri gerçekten depolamak ve almak için bu blok cihazını kullanır. DRBD üzerinde çalışırken böyle bir cihaza asla erişmeyin.</p>
<p>"Meta-disk": Dahili. Dahili, yedekleme aygıtının son kısmının meta verileri depolamak için kullanıldığı anlamına gelir.</p>
<p>"Node-id": Node id drbd için dahili bir değerdir, yast tarafından otomatik olarak üretilecektir. Bir ana bilgisayarın farklı kaynaklarda farklı "node-id"leri olabilir.</p>
3 months ago
User avatar Yok

Translation changed

<p><b>Protocol</b></p>
<p>Protocol A: write IO is reported as completed, if it has reached local disk and local TCP send buffer.</p>
<p>Protocol B: write IO is reported as completed, if it has reached local disk and remote buffer cache.</p>
<p>Protocol C: write IO is reported as completed, if it has reached both local and remote disk.</p>

<p><b>wfc-timeout</b>: Wait for connection timeout</p>
<p><b>degr-wfc-timeout</b>: Wait for connection timeout, if this node was a degraded cluster</p>

<p><b>on-io-error</b>: What to do when the lower level device reports io-error to the upper layers</p>
<p><b>sndbuf-size</b>: The size of the TCP socket send buffer</p>
<p><b>max-buffers</b>: Maximum number of requests to be allocated by DRBD</p>

<p><b>timeout</b>: If the partner node fails to send an expected response packet within time 10ths of a second, the partner node is considered dead and therefore the TCP/IP connection is abandoned. This must be lower than connect-int and ping-int. The default value is 60 = 6 seconds, the unit 0.1 seconds.</p>
<p><b>connect-int</b>: The time the peer has time to answer to a keep-alive packet. In case the peer's reply is not received within this time period, it is considered as dead. The default value is 500ms, the default unit is 100ms</p>
<p><b>ping-int</b>: The time the peer has time to answer to a keep-alive packet</p>

<p><b>max-epoch-size</b>: The highest number of data blocks between two write barriers</p>
<p><b>ko-count</b>: the secondary node fails to complete a single write request for count times the timeout, it is expelled from the cluster. The default value is 0, which disables this feature.</p>
<p><b>rate</b>: To ensure a smooth operation of the application on top of DRBD, it is possible to limit the bandwidth which may be used by background synchronizations. The default is 250 KB/sec, the default unit is KB/sec.</p>
<p><b>al-extents</b>: parameter you control how big the hot area (= active set) can get. The default number of extents is 127. (Minimum: 7, Maximum: 3843)</p>

<p><b>Protokol</b></p>
<p>Protokol A: Yazma G/Ç'si yerel diske ve yerel TCP gönderme tamponuna ulaştığında tamamlanmış olarak raporlanır.</p>
<p>Protokol B: Yazma G/Ç'si yerel diske ve uzak arabellek önbelleğine ulaştığında tamamlanmış olarak raporlanır.</p>
<p>Protocol C: write IO is reported as completed, if it has reached both local and remote disk.</p>

<p><b>wfc-timeout</b>: Wait for connection timeout</p>
<p><b>degr-wfc-timeout</b>: Wait for connection timeout, if this node was a degraded cluster</p>

<p><b>on-io-error</b>: What to do when the lower level device reports io-error to the upper layers</p>
<p><b>sndbuf-size</b>: The size of the TCP socket send buffer</p>
<p><b>max-buffers</b>: Maximum number of requests to be allocated by DRBD</p>

<p><b>timeout</b>: If the partner node fails to send an expected response packet within time 10ths of a second, the partner node is considered dead and therefore the TCP/IP connection is abandoned. This must be lower than connect-int and ping-int. The default value is 60 = 6 seconds, the unit 0.1 seconds.</p>
<p><b>connect-int</b>: The time the peer has time to answer to a keep-alive packet. In case the peer's reply is not received within this time period, it is considered as dead. The default value is 500ms, the default unit is 100ms</p>
<p><b>ping-int</b>: The time the peer has time to answer to a keep-alive packet</p>

<p><b>max-epoch-size</b>: The highest number of data blocks between two write barriers</p>
<p><b>ko-count</b>: the secondary node fails to complete a single write request for count times the timeout, it is expelled from the cluster. The default value is 0, which disables this feature.</p>
<p><b>rate</b>: To ensure a smooth operation of the application on top of DRBD, it is possible to limit the bandwidth which may be used by background synchronizations. The default is 250 KB/sec, the default unit is KB/sec.</p>
<p><b>al-extents</b>: parameter you control how big the hot area (= active set) can get. The default number of extents is 127. (Minimum: 7, Maxkol C: yazma G/Ç'si hem yerel hem de uzak diske ulaştığında tamamlanmış olarak raporlanır.</p>

<p><b>wfc-timeout</b>: Bağlantı zaman aşımını bekleyin</p>
<p><b>degr-wfc-timeout</b>: Bu düğüm bozulmuş bir kümeyse, bağlantı zaman aşımını bekleyin</p>

<p><b>on-io-error</b>: Alt düzey aygıt üst katmanlara io-error bildirdiğinde ne yapılmalı</p>
<p><b>sndbuf-size</b>: TCP soket gönderme tamponunun boyutu</p>
<p><b>max-buffers</b>: DRBD tarafından tahsis edilecek maksimum istek sayısı</p>

<p><b>timeout</b>: Ortak düğüm beklenen yanıt paketini saniyenin onda biri kadar bir sürede gönderemezse, ortak düğüm ölü olarak kabul edilir ve bu nedenle TCP/IP bağlantısı terk edilir. Bu, connect-int ve ping-int'ten düşük olmalıdır. Varsayılan değer 60 = 6 saniyedir, birim 0,1 saniyedir.</p>
<p><b>connect-int</b>: Eşin bir canlı tutma paketine cevap vermek için sahip olduğu zaman. Eşin cevabı bu zaman periyodu içinde alınmazsa, ölü olarak kabul edilir. Varsayılan değer 500ms'dir, varsayılan birim 100ms'dir</p>
<p><b>ping-int</b>: Eşin canlı tutma paketine cevap vermek için sahip olduğu zaman</p>

<p><b>max-epoch-size</b>: İki yazma bariyeri arasındaki en yüksek veri bloğu sayısı</p>
<p><b>ko-count</b>: ikincil düğüm, zaman aşımının sayısı kadar tek bir yazma isteğini tamamlayamazsa, kümeden atılır. Varsayılan değer 0'dır ve bu özelliği devre dışı bırakır.</p>
<p><b>rate</b>: DRBD'nin üstünde uygulamanın düzgün çalışmasını sağlamak için, arka plan senkronizasyonları tarafından kullanılabilecek bant genişliğini sınırlamak mümkündür. Varsayılan 250 KB/sn'dir, varsayılan birim KB/sn'dir.</p>
<p><b>al-extents</b>: parametre sıcak alanın (= aktif set) ne kadar büyük olabileceğini kontrol edersiniz. Varsayılan uzantı sayısı 127'dir. (Minimum: 7, Maksimum: 3843)</p>
3 months ago
User avatar Yok

Translation completed
Translation completed 3 months ago
User avatar Yok

Translation added

<p><b>Protocol</b></p>
<p>Protocol A: write IO is reported as completed, if it has reached local disk and local TCP send buffer.</p>
<p>Protocol B: write IO is reported as completed, if it has reached local disk and remote buffer cache.</p>
<p>Protocol C: write IO is reported as completed, if it has reached both local and remote disk.</p>

<p><b>wfc-timeout</b>: Wait for connection timeout</p>
<p><b>degr-wfc-timeout</b>: Wait for connection timeout, if this node was a degraded cluster</p>

<p><b>on-io-error</b>: What to do when the lower level device reports io-error to the upper layers</p>
<p><b>sndbuf-size</b>: The size of the TCP socket send buffer</p>
<p><b>max-buffers</b>: Maximum number of requests to be allocated by DRBD</p>

<p><b>timeout</b>: If the partner node fails to send an expected response packet within time 10ths of a second, the partner node is considered dead and therefore the TCP/IP connection is abandoned. This must be lower than connect-int and ping-int. The default value is 60 = 6 seconds, the unit 0.1 seconds.</p>
<p><b>connect-int</b>: The time the peer has time to answer to a keep-alive packet. In case the peer's reply is not received within this time period, it is considered as dead. The default value is 500ms, the default unit is 100ms</p>
<p><b>ping-int</b>: The time the peer has time to answer to a keep-alive packet</p>

<p><b>max-epoch-size</b>: The highest number of data blocks between two write barriers</p>
<p><b>ko-count</b>: the secondary node fails to complete a single write request for count times the timeout, it is expelled from the cluster. The default value is 0, which disables this feature.</p>
<p><b>rate</b>: To ensure a smooth operation of the application on top of DRBD, it is possible to limit the bandwidth which may be used by background synchronizations. The default is 250 KB/sec, the default unit is KB/sec.</p>
<p><b>al-extents</b>: parameter you control how big the hot area (= active set) can get. The default number of extents is 127. (Minimum: 7, Maximum: 3843)</p>

<p><b>Protokol</b></p>
<p>Protokol A: Yazma G/Ç'si yerel diske ve yerel TCP gönderme tamponuna ulaştığında tamamlanmış olarak raporlanır.</p>
<p>Protokol B: Yazma G/Ç'si yerel diske ve uzak arabellek önbelleğine ulaştığında tamamlanmış olarak raporlanır.</p>
<p>Protocol C: write IO is reported as completed, if it has reached both local and remote disk.</p>

<p><b>wfc-timeout</b>: Wait for connection timeout</p>
<p><b>degr-wfc-timeout</b>: Wait for connection timeout, if this node was a degraded cluster</p>

<p><b>on-io-error</b>: What to do when the lower level device reports io-error to the upper layers</p>
<p><b>sndbuf-size</b>: The size of the TCP socket send buffer</p>
<p><b>max-buffers</b>: Maximum number of requests to be allocated by DRBD</p>

<p><b>timeout</b>: If the partner node fails to send an expected response packet within time 10ths of a second, the partner node is considered dead and therefore the TCP/IP connection is abandoned. This must be lower than connect-int and ping-int. The default value is 60 = 6 seconds, the unit 0.1 seconds.</p>
<p><b>connect-int</b>: The time the peer has time to answer to a keep-alive packet. In case the peer's reply is not received within this time period, it is considered as dead. The default value is 500ms, the default unit is 100ms</p>
<p><b>ping-int</b>: The time the peer has time to answer to a keep-alive packet</p>

<p><b>max-epoch-size</b>: The highest number of data blocks between two write barriers</p>
<p><b>ko-count</b>: the secondary node fails to complete a single write request for count times the timeout, it is expelled from the cluster. The default value is 0, which disables this feature.</p>
<p><b>rate</b>: To ensure a smooth operation of the application on top of DRBD, it is possible to limit the bandwidth which may be used by background synchronizations. The default is 250 KB/sec, the default unit is KB/sec.</p>
<p><b>al-extents</b>: parameter you control how big the hot area (= active set) can get. The default number of extents is 127. (Minimum: 7, Maximum: 3843)</p>
3 months ago
User avatar None

Changes committed
Changes committed 3 months ago
User avatar Yok

Translation added

<p><b>LVM configuration file /etc/lvm/lvm.conf</b></p>
<p>To use LVM with DRBD, it is necessary to change some options in the LVM configuration file and to remove stale cache entries on the nodes.</p> <p>Refer to 'man lvm.conf' for further information including the file layout.</p>

<p><b>Device Filter</b>: This masks the underlying block device from the list of devices LVM scans for Physical Volume signatures. This way, LVM is instructed to read Physical Volume signatures from DRBD devices, rather than from the underlying backing block devices.</p> <p><b>LVM Filter</b>: A filter that tells LVM2 to only use a restricted set of devices.</p>
<p>The filter consists of an array of regular expressions. These expressions can be delimited by a character of your choice, and prefixed with either an 'a' (for accept) or 'r' (for reject).</p> <p>For example, setting filter as ["r|/dev/sda.*|"]</p>

<p><b>LVM cache</b>: Enable/turn on writing the LVM cache is default. Should disable the LVM cache when combined drbd with LVM.</p>


<p><b>LVM yapılandırma dosyası /etc/lvm/lvm.conf</b></p>
<p>LVM'yi DRBD ile kullanmak için LVM yapılandırma dosyasındaki bazı seçenekleri değiştirmek ve düğümlerdeki eski önbellek girişlerini kaldırmak gerekir.</p> <p>Dosya düzeni dahil daha fazla bilgi için 'man lvm.conf'a bakın.</p>

<p><b>Cihaz Filtresi</b>:Bu, LVM'nin Fiziksel Birim imzaları için taradığı aygıtlar listesinden altta yatan blok aygıtını maskeler. Bu şekilde, LVM'ye altta yatan destek blok aygıtlarından ziyade DRBD aygıtlarından Fiziksel Birim imzalarını okuması talimatı verilir.</p> <p><b>LVM Filtresi</b>: LVM2'ye yalnızca sınırlı sayıda cihazı kullanmasını söyleyen bir filtre.</p>
<p>Filtre, düzenli ifadelerden oluşan bir diziden oluşur. Bu ifadeler, seçtiğiniz bir karakterle sınırlandırılabilir ve 'a' (kabul etmek için) veya 'r' (reddetmek için) öneki eklenebilir.</p> <p>Örneğin, filtreyi ["r|/dev/sda.*|"] olarak ayarlamak</p>

<p><b>LVM önbelleği</b>:LVM önbelleğini yazmayı etkinleştirme/açma varsayılandır. drbd ile LVM birleştirildiğinde LVM önbelleğini devre dışı bırakmalıdır.</p>

3 months ago
User avatar Yok

Translation added
<p><b><big>LVM Configuration</big></b></p>
<p><b><big>LVM Yapılandırması</big></b></p>
3 months ago
User avatar Yok

Translation changed
<p><b><big>Global Configuration of DRBD</big></b></p>
<p><b><big>Bağlantı yDRBD'nin Küresel Yapılandırması</big></b></p>
3 months ago
User avatar Yok

Translation added
<p>Check <b>"Udev Always Use VNR"</b> treat implicit define volume number the same as explicit volumes. When udev asks drbdadm for a list of device related symlinks, drbdadm would suggest symlinks with differing naming conventions, depending on whether the resource has explicit volume VNR { } definitions or only one single volume with the implicit volume number 0.This is enable by default, should be off for legacy backward compatibility.</p>
<p><b>"Udev Her Zaman VNR Kullanır"</b> seçeneğini işaretleyin, örtük tanımlı birim numarasını açık birimlerle aynı şekilde ele alın. Udev, drbdadm'den cihazla ilgili sembolik bağlantıların bir listesini istediğinde, drbdadm, kaynağın açık birim VNR { } tanımları olup olmadığına veya örtük birim numarası 0 olan yalnızca tek bir birime bağlı olarak farklı adlandırma kurallarına sahip sembolik bağlantılar önerecektir. Bu varsayılan olarak etkindir, eski geriye dönük uyumluluk için kapalı olmalıdır.</p>
3 months ago
Browse all project changes