Overview

Project website docs.freebsd.org/en
Translation license BSD 2-Clause "Simplified" License
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
File mask documentation/content/*/books/handbook/zfs/_index.po
Translation file Download documentation/content/nl_NL/books/handbook/zfs/_index.po
Last change June 29, 2025, 2:49 p.m.
Last author Tammo-Jan Kamminga

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 551 19,883 137,474
Translated 1% 1 1% 4 1% 31
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 99% 550 99% 19,879 99% 137,443
Last 12 months Previous

Activity in last 12 months

4 changes 0 changes 0 changes 0 changes 3 changes 64 changes 0 changes 0 changes 0 changes 0 changes 0 changes 3 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 6 changes 0 changes 6 changes
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun

Quick numbers

19,883
Hosted words
551
Hosted strings
1%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
+1%
Translated
—
+50%
Contributors
+100%
User avatar None

New string to translate

Documentation / books/handbook/zfs/_index — Dutch (nl_NL)

1 new string to translate appeared in the translation. 3 weeks ago
User avatar None

Resource update

Documentation / books/handbook/zfs/_index — Dutch (nl_NL)

The "documentation/content/nl_NL/books/handbook/zfs/_index.po" file was changed. 3 weeks ago
User avatar None

String updated in the repository

Documentation / books/handbook/zfs/_index — Dutch (nl_NL)

# gpart bootcode -p /boot/boot1.efi -i 1 ada1
 
3 weeks ago
User avatar None

Committed changes

Documentation / books/handbook/zfs/_index — Dutch (nl_NL)

Committed changes 3 weeks ago
User avatar tj

New translation

Documentation / books/handbook/zfs/_index — Dutch (nl_NL)

Part III. System Administration
Deel III. Systeembeheer
3 weeks ago
User avatar tj

New contributor

Documentation / books/handbook/zfs/_index — Dutch (nl_NL)

New contributor 3 weeks ago
User avatar None

New strings to translate

Documentation / books/handbook/zfs/_index — Dutch (nl_NL)

4 new strings to translate appeared to the translation. 2 months ago
User avatar None

Resource update

Documentation / books/handbook/zfs/_index — Dutch (nl_NL)

The "documentation/content/nl_NL/books/handbook/zfs/_index.po" file was changed. 2 months ago
User avatar None

String updated in the repository

Documentation / books/handbook/zfs/_index — Dutch (nl_NL)

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.
 
2 months ago
User avatar None

String updated in the repository

Documentation / books/handbook/zfs/_index — Dutch (nl_NL)

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.
 
2 months ago
Browse all translation changes