Documentation/books/handbook/zfs/_index — Portuguese (Brazil) @ Weblate

Translation status

551	Strings		11%	Browse Translate
19,883	Words		1%	Browse Translate

Strings status

551	All strings — 19,883 words	Browse Translate Zen
61	Translated strings — 275 words	Browse Translate Zen
490	Unfinished strings — 19,608 words	Browse Translate Zen
394	Untranslated strings — 14,375 words	Browse Translate Zen
96	Strings marked for edit — 5,233 words	Browse Translate Zen
7	Strings with suggestions — 39 words	Browse Translate Zen
483	Unfinished strings without suggestions — 19,569 words	Browse Translate Zen
9	Strings with any failing checks — 237 words	Browse Translate Zen
4	Failing check: Unchanged translation — 8 words	Browse Translate Zen
1	Failing check: Mismatched full stop — 20 words	Browse Translate Zen
1	Failing check: Mismatched colon — 20 words	Browse Translate Zen
1	Failing check: Inconsistent — 1 word	Browse Translate Zen
7	Failing check: Has been translated — 39 words	Browse Translate Zen
1	Failing check: Consecutive duplicated words — 178 words	Browse Translate Zen
551	Strings without a label — 19,883 words	Browse Translate Zen

Other components

Component	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
books/handbook/colophon BSD-2-Clause	0%	3	25	166	3	0	0	0

books/developers-handbook/testing/_index BSD-2-Clause	0%	87	1,758	11,224	86	1	0	0

books/arch-handbook/vm/_index BSD-2-Clause	0%	37	1,766	10,736	36	1	0	0

books/developers-handbook/partiv BSD-2-Clause	0%	2	4	35	2	0	0	0

books/developers-handbook/bibliography/_index BSD-2-Clause	0%	8	135	998	8	1	0	0

books/porters-handbook/porting-samplem/_index BSD-2-Clause	0%	21	450	3,180	20	0	0	0

books/porters-handbook/versions/_index BSD-2-Clause	1%	5,535	20,489	232,945	5,532	0	0	0

books/developers-handbook/sockets/_index BSD-2-Clause	1%	271	6,805	40,785	262	9	0	0

books/developers-handbook/kerneldebug/_index BSD-2-Clause	1%	209	5,084	33,595	201	8	0	0

books/arch-handbook/scsi/_index BSD-2-Clause	1%	356	8,562	62,236	339	12	0	0

Browse all components

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/pt_BR/books/handbook/zfs/_index.po`
Last change	Jan. 8, 2022, 8:29 p.m.
Last author	None

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		551		19,883		137,477
Translated	11%	61	1%	275	1%	1,797
Needs editing	17%	96	26%	5,233	23%	32,560
Read-only	0%	0	0%	0	0%	0
Failing checks	1%	9	1%	237	1%	1,637
Strings with suggestions	1%	7	1%	39	1%	339
Untranslated strings	71%	394	72%	14,375	75%	103,120

Last 12 months Previous

Activity in last 12 months


Jun	Jul	Aug	Sep	Oct	Nov	Dec	Jan	Feb	Mar	Apr	May

Quick numbers

19,883

Hosted words

551

Hosted strings

11%

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

+100%

—

Hosted strings

+100%

—

Translated

+11%

—

Contributors

—

None New strings to translate Documentation / books/handbook/zfs/_index — Portuguese (Brazil)	4 new strings to translate appeared to the translation. a month ago
None Resource update Documentation / books/handbook/zfs/_index — Portuguese (Brazil)	The "`documentation/content/pt_BR/books/handbook/zfs/_index.po`" file was changed. a month ago
None String updated in the repository Documentation / books/handbook/zfs/_index — Portuguese (Brazil)	English 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. Portuguese (Brazil) 0 characters edited Current translation a month ago
None String updated in the repository Documentation / books/handbook/zfs/_index — Portuguese (Brazil)	English 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. Portuguese (Brazil) 0 characters edited Current translation a month ago
None String updated in the repository Documentation / books/handbook/zfs/_index — Portuguese (Brazil)	English 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. Portuguese (Brazil) 0 characters edited Current translation a month ago
None String updated in the repository Documentation / books/handbook/zfs/_index — Portuguese (Brazil)	English # 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 ----------------------- ----- ----- ----- ----- ----- ----- Portuguese (Brazil) 0 characters edited Current translation a month ago
None New string to translate Documentation / books/handbook/zfs/_index — Portuguese (Brazil)	1 new string to translate appeared in the translation. 5 months ago
None Resource update Documentation / books/handbook/zfs/_index — Portuguese (Brazil)	The "`documentation/content/pt_BR/books/handbook/zfs/_index.po`" file was changed. 5 months ago
None String updated in the repository Documentation / books/handbook/zfs/_index — Portuguese (Brazil)	English A complete list of features and terminology is in crossref:zfs[zfs-term, ZFS Features and Terminology]. Portuguese (Brazil) 0 characters edited Current translation 5 months ago
None New strings to translate Documentation / books/handbook/zfs/_index — Portuguese (Brazil)	62 new strings to translate appeared to the translation. 9 months ago

Browse all translation changes

Quick downloads

551	File in original format as translated in the repository	gettext PO file
551	All strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX
490	Unfinished strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX

Customize download

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2025-05-16 AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>=2025-05-16 AND state:<=needs-editing`	Add