Translation

(itstool) path: chapter/para
A complete list of features and terminology is shown in <xref linkend="zfs-term"/>.
0/830
Context English Turkish (tr_TR) State
A <acronym>UFS</acronym> file system may now be created on the journaled device, then mounted on an existing mount point: Günlüklü aygıtta bir <acronym> UFS </acronym> dosya sistemi oluşturulabilir, ardından mevcut bir bağlama noktasına monte edilebilir:
<prompt>#</prompt> <userinput>newfs -O 2 -J /dev/<replaceable>da4</replaceable>.journal</userinput>
<prompt>#</prompt> <userinput>mount /dev/<replaceable>da4</replaceable>.journal <replaceable>/mnt</replaceable></userinput>
<prompt>#</prompt> <userinput>newfs -O 2 -J /dev/<replaceable>da4</replaceable>.journal</userinput>
<prompt>#</prompt> <userinput>mount /dev/<replaceable>da4</replaceable>.journal <replaceable>/mnt</replaceable></userinput>
In the case of several slices, a journal will be created for each individual slice. For instance, if <filename>ad4s1</filename> and <filename>ad4s2</filename> are both slices, then <command>gjournal</command> will create <filename>ad4s1.journal</filename> and <filename>ad4s2.journal</filename>. Birkaç dilim durumunda, her bir dilim için bir günlük oluşturulacaktır. Örneğin, <filename> ad4s1 </filename> ve <filename> ad4s2 </filename> her iki dilimse <command> gjournal </command> <filename> ad4s1.journal </filename> ve <filename> öğelerini oluşturur ad4s2.journal </ filename>.
Journaling may also be enabled on current file systems by using <command>tunefs</command>. However, <emphasis>always</emphasis> make a backup before attempting to alter an existing file system. In most cases, <command>gjournal</command> will fail if it is unable to create the journal, but this does not protect against data loss incurred as a result of misusing <command>tunefs</command>. Refer to <citerefentry><refentrytitle>gjournal</refentrytitle><manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>tunefs</refentrytitle><manvolnum>8</manvolnum></citerefentry> for more information about these commands. Günlük kaydı, <command> tunefs </command> kullanılarak mevcut dosya sistemlerinde de etkinleştirilebilir. Ancak, <emphasis> her zaman </emphasis> mevcut bir dosya sistemini değiştirmeye çalışmadan önce bir yedek oluşturur. Çoğu durumda, günlük oluşturamazsa <command> gjournal </command> başarısız olur, ancak bu, <command> tunefs </command> 'in yanlış kullanımı sonucu oluşan veri kaybına karşı koruma sağlamaz. <citerefentry><refentrytitle>gjournal</refentrytitle><manvolnum>8</manvolnum> </citerefentry><manvolnum>it<verenum>8</olfentrytitle><manvolnum> 8</olfentrytitle><manvolnum> bu komutlar hakkında daha fazla bilgi.
It is possible to journal the boot disk of a FreeBSD system. Refer to the article <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/gjournal-desktop">Implementing UFS Journaling on a Desktop PC</link> for detailed instructions. FreeBSD sisteminin önyükleme diskini günlüğe kaydetmek mümkündür. Ayrıntılı talimatlar için <link xlink: href = "@@ URL_RELPREFIX @@ / doc / en_US.ISO8859-1 / article / gjournal-desktop"> UFS Günlük Kaydını Masaüstü PC </link> makalesine bakın.
The Z File System (<acronym>ZFS</acronym>) Z Dosya Sistemi (<acronym>ZFS</acronym>)
<personname> <firstname>Allan</firstname> <surname>Jude</surname> </personname> <contrib>Written by </contrib> <personname> <firstname>Allan</firstname> <surname>Jude</surname> </personname> <contrib>Yazan</contrib>
<personname> <firstname>Benedict</firstname> <surname>Reuschling</surname> </personname> <contrib>Written by </contrib> <personname> <firstname>Benedict</firstname> <surname>Reuschling</surname> </personname> <contrib>Yazan </contrib>
<personname> <firstname>Warren</firstname> <surname>Block</surname> </personname> <contrib>Written by </contrib>
The <emphasis>Z File System</emphasis>, or <acronym>ZFS</acronym>, is an advanced file system designed to overcome many of the major problems found in previous designs.
Originally developed at <trademark>Sun</trademark>, ongoing open source <acronym>ZFS</acronym> development has moved to the <link xlink:href="http://open-zfs.org">OpenZFS Project</link>.
<acronym>ZFS</acronym> has three major design goals:
Data integrity: All data includes a <link linkend="zfs-term-checksum">checksum</link> of the data. When data is written, the checksum is calculated and written along with it. When that data is later read back, the checksum is calculated again. If the checksums do not match, a data error has been detected. <acronym>ZFS</acronym> will attempt to automatically correct errors when data redundancy is available.
Pooled storage: physical storage devices are added to a pool, and storage space is allocated from that shared pool. Space is available to all file systems, and can be increased by adding new storage devices to the pool.
Performance: multiple caching mechanisms provide increased performance. <link linkend="zfs-term-arc">ARC</link> is an advanced memory-based read cache. A second level of disk-based read cache can be added with <link linkend="zfs-term-l2arc">L2ARC</link>, and disk-based synchronous write cache is available with <link linkend="zfs-term-zil">ZIL</link>.
A complete list of features and terminology is shown in <xref linkend="zfs-term"/>.
What Makes <acronym>ZFS</acronym> Different
<acronym>ZFS</acronym> 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 <acronym>ZFS</acronym> 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 <acronym>RAID</acronym> 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 <acronym>RAID</acronym> solutions like those provided by <acronym>GEOM</acronym>, the <acronym>UFS</acronym> file system living on top of the <acronym>RAID</acronym> transform believed that it was dealing with a single device. <acronym>ZFS</acronym>'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 <acronym>ZFS</acronym>'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. <acronym>ZFS</acronym> 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.
Quick Start Guide
There is a startup mechanism that allows FreeBSD to mount <acronym>ZFS</acronym> pools during system initialization. To enable it, add this line to <filename>/etc/rc.conf</filename>:
zfs_enable="YES"
Then start the service:
<prompt>#</prompt> <userinput>service zfs start</userinput>
The examples in this section assume three <acronym>SCSI</acronym> disks with the device names <filename><replaceable>da0</replaceable></filename>, <filename><replaceable>da1</replaceable></filename>, and <filename><replaceable>da2</replaceable></filename>. Users of <acronym>SATA</acronym> hardware should instead use <filename><replaceable>ada</replaceable></filename> device names.
Single Disk Pool
To create a simple, non-redundant pool using a single disk device:
<prompt>#</prompt> <userinput>zpool create <replaceable>example</replaceable> <replaceable>/dev/da0</replaceable></userinput>
To view the new pool, review the output of <command>df</command>:
<prompt>#</prompt> <userinput>df</userinput>
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/ad0s1a 2026030 235230 1628718 13% /
devfs 1 1 0 100% /dev
/dev/ad0s1d 54098308 1032846 48737598 2% /usr
example 17547136 0 17547136 0% /example
This output shows that the <literal>example</literal> pool has been created and mounted. It is now accessible as a file system. Files can be created on it and users can browse it:
<prompt>#</prompt> <userinput>cd /example</userinput>
<prompt>#</prompt> <userinput>ls</userinput>
<prompt>#</prompt> <userinput>touch testfile</userinput>
<prompt>#</prompt> <userinput>ls -al</userinput>
total 4
drwxr-xr-x 2 root wheel 3 Aug 29 23:15 .
drwxr-xr-x 21 root wheel 512 Aug 29 23:12 ..
-rw-r--r-- 1 root wheel 0 Aug 29 23:15 testfile

Loading…

No matching activity found.

Browse all component changes

Glossary

English Turkish (tr_TR)
complete jail tam hapis FreeBSD Doc

Source information

Source string comment
(itstool) path: chapter/para
Source string location
book.translate.xml:37583
String age
6 months ago
Source string age
a year ago
Translation file
books/tr_TR/handbook.po, string 6267