Состояние перевода

551 Строки 1%
Навигация Перевести
19 883 Слова 1%

Состояние строк

551
Все строки — 19 883 слова Навигация Перевести Дзен
1
Переведённые строки — 2 слова Навигация Перевести Дзен
550
Незавершённые строки — 19 881 слово Навигация Перевести Дзен
550
Непереведённые строки — 19 881 слово Навигация Перевести Дзен
550
Незавершённые строки без предложений — 19 881 слово Навигация Перевести Дзен
551
Строки без меток — 19 883 слова Навигация Перевести Дзен

Другие компоненты

Компонент Переведено Незавершённые Незавершённые слова Незавершённые символы Без перевода Проверки Предложения Комментарии
books/handbook/basics/_index Этот компонент связан с репозиторием Documentation/articles/bsdl-gpl. BSD-2-Clause 0% 630 11 689 72 465 630 0 0 0
books/developers-handbook/_index Этот компонент связан с репозиторием Documentation/articles/bsdl-gpl. BSD-2-Clause 0% 6 115 764 6 0 0 0
books/arch-handbook/scsi/_index Этот компонент связан с репозиторием Documentation/articles/bsdl-gpl. BSD-2-Clause 0% 358 8 564 62 246 358 0 0 0
books/_index Этот компонент связан с репозиторием Documentation/articles/bsdl-gpl. BSD-2-Clause 0% 2 4 35 2 0 0 0
books/fdp-primer/working-copy/_index Этот компонент связан с репозиторием Documentation/articles/bsdl-gpl. BSD-2-Clause 0% 33 718 4 559 33 0 0 0
Словарь Doc Glossary BSD-2-Clause 0% 11 15 110 11 0 0 0
articles/cups/_index Этот компонент связан с репозиторием Documentation/articles/bsdl-gpl. BSD-2-Clause 0% 54 1 461 10 397 54 0 0 0
books/arch-handbook/_index Этот компонент связан с репозиторием Documentation/articles/bsdl-gpl. BSD-2-Clause 0% 6 114 776 6 0 0 0
articles/new-users/_index Этот компонент связан с репозиторием Documentation/articles/bsdl-gpl. BSD-2-Clause 0% 158 3 150 18 705 158 0 0 0
books/developers-handbook/x86/_index Этот компонент связан с репозиторием Documentation/articles/bsdl-gpl. BSD-2-Clause 0% 934 21 332 120 774 934 0 0 0
Навигация по всем компонентам

Общие сведения

Веб-сайт проекта docs.freebsd.org/en
Лицензия перевода BSD 2-Clause "Simplified" License
Процесс перевода
  • Можно переводить напрямую.
  • Можно делать предложения по переводу.
  • Только избранные пользователи могут участвовать.
  • Перевод использует двуязычные файлы.
Маска файла documentation/content/*/books/handbook/zfs/_index.po
Файл перевода Скачать documentation/content/nb_NO/books/handbook/zfs/_index.po
Последнее изменение 5 апреля 2021 г. 23:32
Последний автор Anonymous

Статистика строк

Процент строк Хранимые строки Процент слов Хранимые слова Процент символов Хранимые символы
Всего 551 19 883 137 474
Переведено 1% 1 1% 2 1% 20
На правку 0% 0 0% 0 0% 0
Только чтение 0% 0 0% 0 0% 0
Неудачные проверки 0% 0 0% 0 0% 0
Строки с предложениями 0% 0 0% 0 0% 0
Строки без перевода 99% 550 99% 19 881 99% 137 454
Последние 12 месяцев Предыдущие

Деятельность за последние 12 месяцев

4 изменения 0 изменений 0 изменений 0 изменений 3 изменения 64 изменения 0 изменений 0 изменений 0 изменений 0 изменений 0 изменений 3 изменения 0 изменений 0 изменений 0 изменений 0 изменений 0 изменений 0 изменений 0 изменений 0 изменений 0 изменений 6 изменений 0 изменений 3 изменения
Июл Авг Сен Окт Ноя Дек Янв Фев Мар Апр Май Июн

Быстрые числа

19 883
Хранимые слова
551
Хранимые строки
1%
Переведено
0
Участники
и предыдущие 30 дней

Тенденции последних 30-ти дней

—
Хранимые слова
+100%
—
Хранимые строки
+100%
—
Переведено
+1%
—
Участники
+100%
Аватар пользователя Без имени

Новая строка для перевода

Documentation / books/handbook/zfs/_index — Норвежский (букмол)

1 новая строка теперь доступна для перевода. месяц назад
Аватар пользователя Без имени

Обновление ресурсов

Documentation / books/handbook/zfs/_index — Норвежский (букмол)

Файл "documentation/content/nb_NO/books/handbook/zfs/_index.po" был изменён. месяц назад
Аватар пользователя Без имени

Строка обновлена в репозитории

Documentation / books/handbook/zfs/_index — Норвежский (букмол)

# gpart bootcode -p /boot/boot1.efi -i 1 ada1
 
месяц назад
Аватар пользователя Без имени

Новые строки для перевода

Documentation / books/handbook/zfs/_index — Норвежский (букмол)

4 новые строки теперь доступны для перевода. 3 месяца назад
Аватар пользователя Без имени

Обновление ресурсов

Documentation / books/handbook/zfs/_index — Норвежский (букмол)

Файл "documentation/content/nb_NO/books/handbook/zfs/_index.po" был изменён. 3 месяца назад
Аватар пользователя Без имени

Строка обновлена в репозитории

Documentation / books/handbook/zfs/_index — Норвежский (букмол)

Each dataset has a compression property, which defaults to off. Set this property to an available compression algorithm. This causes compression of all new data written to the dataset. Beyond a reduction in space used, read and write throughput often increases because fewer blocks need reading or writing.

[[zfs-term-compression-lz4]]
* _LZ4_ - Added in ZFS pool version 5000 (feature flags), LZ4 is now the recommended compression algorithm. LZ4 works about 50% faster than LZJB when operating on compressible data, and is over three times faster when operating on uncompressible data. LZ4 also decompresses about 80% faster than LZJB. On modern CPUs, LZ4 can often compress at over 500 MB/s, and decompress at over 1.5 GB/s (per single CPU core).

[[zfs-term-compression-lzjb]]
* _LZJB_ - The default compression algorithm. Created by Jeff Bonwick (one of the original creators of ZFS). LZJB offers good compression with less CPU overhead compared to GZIP. In the future, the default compression algorithm will change to LZ4.

[[zfs-term-compression-gzip]]
* _GZIP_ - A popular stream compression algorithm available in ZFS. One of the main advantages of using GZIP is its configurable level of compression. When setting the `compress` property, the administrator can choose the level of compression, ranging from `gzip1`, the lowest level of compression, to `gzip9`, the highest level of compression. This gives the administrator control over how much CPU time to trade for saved disk space.

[[zfs-term-compression-zle]]
* _ZLE_ - Zero Length Encoding is a special compression algorithm that compresses continuous runs of zeros alone. This compression algorithm is useful when the dataset contains large blocks of zeros.
 
3 месяца назад
Аватар пользователя Без имени

Строка обновлена в репозитории

Documentation / books/handbook/zfs/_index — Норвежский (букмол)

Transaction Groups are the way ZFS groups blocks changes together and writes them to the pool. Transaction groups are the atomic unit that ZFS uses to ensure consistency. ZFS assigns each transaction group a unique 64-bit consecutive identifier. There can be up to three active transaction groups at a time, one in each of these three states:

* _Open_ - A new transaction group begins in the open state and accepts new
writes. There is always a transaction group in the open state, but the
transaction group may refuse new writes if it has reached a limit. Once the
open transaction group has reached a limit, or reaching the
crossref:zfs[zfs-advanced-tuning-txg-timeout,`vfs.zfs.txg.timeout`], the transaction group advances to the next state.
* _Quiescing_ - A short state that allows any pending operations to finish without blocking the creation of a new open transaction group. Once all the transactions in the group have completed, the transaction group advances to the final state.
* _Syncing_ - Write all the data in the transaction group to stable storage.
This process will in turn change other data, such as metadata and space maps,
that ZFS will also write to stable storage. The process of syncing involves
several passes. On the first and biggest, all the changed data blocks; next
come the metadata, which may take several passes to complete. Since allocating
space for the data blocks generates new metadata, the syncing state cannot
finish until a pass completes that does not use any new space. The syncing
state is also where _synctasks_ complete. Synctasks are administrative
operations such as creating or destroying snapshots and datasets that complete
the uberblock change. Once the sync state completes the transaction group in
the quiescing state advances to the syncing state. All administrative
functions, such as crossref:zfs[zfs-term-snapshot,`snapshot`] write as part of the transaction group. ZFS adds a created synctask to the open transaction group, and that group advances as fast as possible to the syncing state to reduce the latency of administrative commands.
 
3 месяца назад
Аватар пользователя Без имени

Строка обновлена в репозитории

Documentation / books/handbook/zfs/_index — Норвежский (букмол)

A pool consists of one or more vdevs, which themselves are a single disk or a group of disks, transformed to a RAID. When using a lot of vdevs, ZFS spreads data across the vdevs to increase performance and maximize usable space. All vdevs must be at least 128 MB in size.

* [[zfs-term-vdev-disk]] _Disk_ - The most basic vdev type is a standard block device. This can be an entire disk (such as [.filename]#/dev/ada0# or [.filename]#/dev/da0#) or a partition ([.filename]#/dev/ada0p3#). On FreeBSD, there is no performance penalty for using a partition rather than the entire disk. This differs from recommendations made by the Solaris documentation.
+
[CAUTION]
====
Using an entire disk as part of a bootable pool is strongly discouraged, as this may render the pool unbootable.
Likewise, you should not use an entire disk as part of a mirror or RAID-Z vdev.
Reliably determining the size of an unpartitioned disk at boot time is impossible and there's no place to put in boot code.
====

* [[zfs-term-vdev-file]] _File_ - Regular files may make up ZFS pools, which is useful for testing and experimentation. Use the full path to the file as the device path in `zpool create`.
* [[zfs-term-vdev-mirror]] _Mirror_ - When creating a mirror, specify the `mirror` keyword followed by the list of member devices for the mirror. A mirror consists of two or more devices, writing all data to all member devices. A mirror vdev will hold as much data as its smallest member. A mirror vdev can withstand the failure of all but one of its members without losing any data.
+
[NOTE]
====
To upgrade a regular single disk vdev to a mirror vdev at any time, use `zpool
crossref:zfs[zfs-zpool-attach,attach]`.
====

* [[zfs-term-vdev-raidz]] _RAID-Z_ - ZFS uses RAID-Z, a variation on standard RAID-5 that offers better distribution of parity and eliminates the "RAID-5 write hole" in which the data and parity information become inconsistent after an unexpected restart. ZFS supports three levels of RAID-Z which provide varying levels of redundancy in exchange for decreasing levels of usable storage. ZFS uses RAID-Z1 through RAID-Z3 based on the number of parity devices in the array and the number of disks which can fail before the pool stops being operational.
+
In a RAID-Z1 configuration with four disks, each 1 TB, usable storage is 3 TB and the pool will still be able to operate in degraded mode with one faulted disk. If another disk goes offline before replacing and resilvering the faulted disk would result in losing all pool data.
+
In a RAID-Z3 configuration with eight disks of 1 TB, the volume will provide 5 TB of usable space and still be able to operate with three faulted disks. Sun(TM) recommends no more than nine disks in a single vdev. If more disks make up the configuration, the recommendation is to divide them into separate vdevs and stripe the pool data across them.
+
A configuration of two RAID-Z2 vdevs consisting of 8 disks each would create something like a RAID-60 array. A RAID-Z group's storage capacity is about the size of the smallest disk multiplied by the number of non-parity disks. Four 1 TB disks in RAID-Z1 has an effective size of about 3 TB, and an array of eight 1 TB disks in RAID-Z3 will yield 5 TB of usable space.
* [[zfs-term-vdev-spare]] _Spare_ - ZFS has a special pseudo-vdev type for keeping track of available hot spares. Note that installed hot spares are not deployed automatically; manually configure them to replace the failed device using `zfs replace`.
* [[zfs-term-vdev-log]] _Log_ - ZFS Log Devices, also known as ZFS Intent Log
(crossref:zfs[zfs-term-zil,ZIL]) move the intent log from the regular pool devices to a dedicated device, typically an SSD. Having a dedicated log device improves the performance of applications with a high volume of synchronous writes like databases. Mirroring of log devices is possible, but RAID-Z is not supported. If using a lot of log devices, writes will be load-balanced across them.
* [[zfs-term-vdev-cache]] _Cache_ - Adding a cache vdev to a pool will add the
storage of the cache to the crossref:zfs[zfs-term-l2arc,L2ARC]. Mirroring cache devices is impossible. Since a cache device stores only new copies of existing data, there is no risk of data loss.
 
3 месяца назад
Аватар пользователя Без имени

Строка обновлена в репозитории

Documentation / books/handbook/zfs/_index — Норвежский (букмол)

# zpool iostat -v
capacity operations bandwidth
pool alloc free read write read write
----------------------- ----- ----- ----- ----- ----- -----
data 288G 1.53T 2 12 9.23K 61.5K
mirror 288G 1.53T 2 12 9.23K 61.5K
ada1 - - 0 4 5.61K 61.7K
ada2 - - 1 4 5.04K 61.7K
----------------------- ----- ----- ----- ----- ----- -----
 
3 месяца назад
Аватар пользователя Без имени

Новая строка для перевода

Documentation / books/handbook/zfs/_index — Норвежский (букмол)

1 новая строка теперь доступна для перевода. 7 месяцев назад
Навигация по всем изменениям перевода

Быстрое скачивание

551 Файл в оригинальном формате, в том виде, в котором он хранится в репозитории PO-файл gettext
551 Все строки, преобразованные файлы, дополненные комментариями; подходит для офлайн-перевода CSV gettext MO gettext (PO) TBX TMX XLIFF 1.1 с расширениями gettext XLIFF 1.1 XLSX
550 Незавершённые строки, преобразованные файлы, дополненные комментариями; подходит для офлайн-перевода CSV gettext MO gettext (PO) TBX TMX XLIFF 1.1 с расширениями gettext XLIFF 1.1 XLSX

Настроить скачивание