2. FreeBSD Doc
  3. books_handbook
  4. Turkish (tr_TR)
  5. Translate

Translation

(itstool) path: note/para

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>.
286/2950
Context English Turkish (tr_TR) State
Any partitions with <literal>ufsid</literal> labels can be mounted in this way, eliminating the need to manually create permanent labels, while still enjoying the benefits of device name independent mounting. <literal> ufsid </literal> etiketli tüm bölümler bu şekilde monte edilebilir, böylece cihaz adından bağımsız montajın avantajlarından yararlanırken kalıcı etiketler manuel olarak oluşturulma gereği ortadan kalkar.
UFS Journaling Through <acronym>GEOM</acronym> <acronym> GEOM </acronym> Aracılığıyla UFS Günlük Kaydı
<primary>Journaling</primary> <primary>Günlük Kaydı</primary>
Support for journals on <acronym>UFS</acronym> file systems is available on FreeBSD. The implementation is provided through the <acronym>GEOM</acronym> subsystem and is configured using <command>gjournal</command>. Unlike other file system journaling implementations, the <command>gjournal</command> method is block based and not implemented as part of the file system. It is a <acronym>GEOM</acronym> extension. <acronym> UFS </acronym> dosya sistemlerindeki dergiler için destek FreeBSD'de bulunmaktadır. Uygulama <acronym> GEOM </acronym> alt sistemi üzerinden sağlanır ve <command> gjournal </command> kullanılarak yapılandırılır. Diğer dosya sistemi günlük kaydı uygulamalarının aksine, <command> gjournal </command> yöntemi blok tabanlıdır ve dosya sisteminin bir parçası olarak uygulanmaz. Bir <acronym> GEOM </acronym> uzantısıdır.
Journaling stores a log of file system transactions, such as changes that make up a complete disk write operation, before meta-data and file writes are committed to the disk. This transaction log can later be replayed to redo file system transactions, preventing file system inconsistencies. Günlük kaydı, meta veri ve dosya yazma işlemleri diske bağlanmadan önce, tam bir disk yazma işlemini oluşturan değişiklikler gibi dosya sistemi işlemlerinin bir günlüğünü depolar. Bu işlem günlüğü dosya sistemi tutarsızlıklarını önleyerek dosya sistemi işlemlerini yeniden yapmak için daha sonra yeniden yürütülebilir.
This method provides another mechanism to protect against data loss and inconsistencies of the file system. Unlike Soft Updates, which tracks and enforces meta-data updates, and snapshots, which create an image of the file system, a log is stored in disk space specifically for this task. For better performance, the journal may be stored on another disk. In this configuration, the journal provider or storage device should be listed after the device to enable journaling on. Bu yöntem, veri kaybına ve dosya sisteminin tutarsızlıklarına karşı korunmak için başka bir mekanizma sağlar. Dosya sistemi görüntüsünü oluşturan meta veri güncellemelerini ve anlık görüntüleri izleyen ve uygulayan Yazılım Güncelleştirmelerinden farklı olarak, bir günlük, özellikle bu görev için disk alanında depolanır. Daha iyi performans için günlük başka bir diskte saklanabilir. Bu yapılandırmada günlük kaydını etkinleştirmek için günlük sağlayıcısı veya depolama aygıtı aygıttan sonra listelenmelidir.
The <filename>GENERIC</filename> kernel provides support for <command>gjournal</command>. To automatically load the <filename>geom_journal.ko</filename> kernel module at boot time, add the following line to <filename>/boot/loader.conf</filename>: <filename> GENERIC </filename> çekirdeği <command> gjournal </command> için destek sağlar. <filename> geom_journal.ko </filename> çekirdek modülünü önyükleme sırasında otomatik olarak yüklemek için <filename> /boot/loader.conf </filename> dosyasına aşağıdaki satırı ekleyin:
geom_journal_load="YES" geom_journal_load="EVET"
If a custom kernel is used, ensure the following line is in the kernel configuration file: Özel bir çekirdek kullanılıyorsa, çekirdek yapılandırma dosyasında aşağıdaki satırın bulunduğundan emin olun:
options GEOM_JOURNAL options GEOM_JOURNAL
Once the module is loaded, a journal can be created on a new file system using the following steps. In this example, <filename>da4</filename> is a new <acronym>SCSI</acronym> disk: Modül yüklendikten sonra, aşağıdaki adımlar kullanılarak yeni bir dosya sisteminde bir günlük oluşturulabilir. Bu örnekte, <filename> da4 </filename> yeni bir <acronym> SCSI </acronym> diskidir:
<prompt>#</prompt> <userinput>gjournal load</userinput>
<prompt>#</prompt> <userinput>gjournal label /dev/<replaceable>da4</replaceable></userinput> 		<prompt>#</prompt> <userinput>gjournal load</userinput>
<prompt>#</prompt> <userinput>gjournal label /dev/<replaceable>da4</replaceable></userinput>
This will load the module and create a <filename>/dev/da4.journal</filename> device node on <filename>/dev/da4</filename>. Bu, modülü yükler ve <filename> / dev / da4 </filename> üzerinde bir <filename> /dev/da4.journal </filename> aygıt düğümü oluşturur.
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.

Loading…

User avatar ibrahimkarapolat

Marked for edit

FreeBSD Doc / books_handbook — Turkish (tr_TR)

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>.
3 months ago
Browse all component changes

Things to check

Has been translated

Last translation was "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>.".

Fix string

Reset

XML syntax

The translation is not valid XML

Reset

Glossary

English Turkish (tr_TR)
individual drivers bireysel sürücüler FreeBSD Doc

Source information

Source string comment

(itstool) path: note/para

Source string location
book.translate.xml:37475
String age
5 months ago
Source string age
a year ago
Translation file
books/tr_TR/handbook.po, string 6254