Translation Information

Project website docs.freebsd.org/en
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
Translation license BSD 2-Clause "Simplified" License
Filemask documentation/content/*/books/handbook/zfs/_index.po
Translation file Download documentation/content/zh_CN/books/handbook/zfs/_index.po
Performance: multiple caching mechanisms provide increased performance. <<zfs-term-arc,ARC>> is an advanced memory-based read cache. A second level of disk-based read cache can be added with <<zfs-term-l2arc,L2ARC>>, and disk-based synchronous write cache is available with <<zfs-term-zil,ZIL>>.
高性能:多级缓存机制提供更好的性能。<link linkend="zfs-term-arc">ARC</link> 是一种高级的基于内存的读取缓存。第二级基于磁盘的读取缓存可以与 <link linkend="zfs-term-l2arc">L2ARC</link> 一起添加,基于磁盘的同步写入缓存可用于 <link linkend="zfs-term-zil">ZIL</link>。
3 days ago
New contributor 3 days ago
ZFS is significantly different from any previous file system because it is more than just a file system. Combining the traditionally separate roles of volume manager and file system provides ZFS with unique advantages. The file system is now aware of the underlying structure of the disks. Traditional file systems could only be created on a single disk at a time. If there were two disks then two separate file systems would have to be created. In a traditional hardware RAID configuration, this problem was avoided by presenting the operating system with a single logical disk made up of the space provided by a number of physical disks, on top of which the operating system placed a file system. Even in the case of software RAID solutions like those provided by GEOM, the UFS file system living on top of the RAID transform believed that it was dealing with a single device. ZFS's combination of the volume manager and the file system solves this and allows the creation of many file systems all sharing a pool of available storage. One of the biggest advantages to ZFS's awareness of the physical layout of the disks is that existing file systems can be grown automatically when additional disks are added to the pool. This new space is then made available to all of the file systems. ZFS also has a number of different properties that can be applied to each file system, giving many advantages to creating a number of different file systems and datasets rather than a single monolithic file system.
<acronym>ZFS</acronym> 与以往任何的文件系统有显著的不同,因为它不只是一个文件系统,<acronym>ZFS</acronym> 的独特优点来自结合了以往被分开的磁盘区管理程序(Volume Manager)及文件系统两个角色,让文件系统也能够察觉磁盘底层结构的变动。传统在一个磁盘上只能建立一个文件系统,若有两个磁盘则会需要建立两个分开的文件系统,在传统要解决这个问题要使用硬 <acronym>RAID</acronym> 来制作一个空间实际上由数颗实体磁盘所组成的单一的逻辑磁盘给文件系统,文件系统便可在这个逻辑磁盘上放置文件系统,即使是在那些使用 <acronym>GEMO</acronym> 提供的软 <acronym>RAID</acronym> 解决方案也是一样,把 <acronym>UFS</acronym> 文件系统放在 <acronym>RAID</acronym> Transform上面当做是一个单一的设备。<acronym>ZFS</acronym> 结合了磁盘区管理程序(Volume Manager)与文件系统来解决这个问题并让建立多个文件系统可以共用一个存储池(Pool)。<acronym>ZFS</acronym> 最大的优点是可以察觉实体磁盘配置的变动,当有额外的磁盘加入到存储池时可以自动扩增现有的文件系统,所有的文件系统便可使用这个新的空间。<acronym>ZFS</acronym> 也有数个不同的属性可以套用到各别文件系统上,比起单一文件系统,对建立数个不同文件系统与数据集(Dataset)时有许多的好处。
3 days ago
New contributor 3 days ago
zfs_enable="YES"
zfs_enable="YES"
3 days ago
New contributor 3 days ago
Users data is now stored on the freshly-created [.filename]#/storage/home#. Test by adding a new user and logging in as that user.
现在用户的数据会储存在新建立的 <filename>/storage/home</filename>。 可以加入新用户并登入该使用者来测试。
3 days ago
New contributor 3 days ago
The `@` character is a delimiter between the file system name or the volume name. If an important directory has been accidentally deleted, the file system can be backed up, then rolled back to an earlier snapshot when the directory still existed:
<literal>@</literal> 字符用来区分文件系统(file system)或磁盘区(卷)名称,若有重要的目录意外被删除,文件系统系统可以备份然后还原到先前目录还存在时的快照:
3 days ago
New contributor 3 days ago
Browse all translation changes

Statistics

Percent Strings Words Chars
Total 513 21,136 141,792
Translated 17% 90 969 5,901
Needs editing 14% 74 5,198 31,155
Failing checks 1% 7 94 628

Last activity

Last change April 12, 2021, 8:45 a.m.
Last author Anonymous

Daily activity

Daily activity

Weekly activity

Weekly activity