svn commit: r40378 - head/en_US.ISO8859-1/books/faq
Eitan Adler
eadler at FreeBSD.org
Thu Dec 13 13:07:13 UTC 2012
Author: eadler
Date: Thu Dec 13 13:07:12 2012
New Revision: 40378
URL: http://svnweb.freebsd.org/changeset/doc/40378
Log:
Minor wording fixes for the recently committed ZFS section.
Reviewed by: bjk
Approved by: bcr (mentor)
Modified:
head/en_US.ISO8859-1/books/faq/book.xml
Modified: head/en_US.ISO8859-1/books/faq/book.xml
==============================================================================
--- head/en_US.ISO8859-1/books/faq/book.xml Thu Dec 13 12:04:49 2012 (r40377)
+++ head/en_US.ISO8859-1/books/faq/book.xml Thu Dec 13 13:07:12 2012 (r40378)
@@ -4833,7 +4833,8 @@ C:\="DOS"</programlisting>
are bundled up into transaction groups
and written to disk when filled (<quote>Transaction Group
Commit</quote>). However syscalls like &man.fsync.2;
- require a commitment to stable storage before returning.
+ require a commitment that the data is written to stable
+ storage before returning.
The ZIL is needed for writes that have been acknowledged
as written but which are not yet on disk as part of a
transaction. The transaction groups are timestamped.
@@ -4893,10 +4894,10 @@ C:\="DOS"</programlisting>
very heavily duplicated (such as virtual machine images,
or user backups) it is possible that deduplication will
do more harm than good. Another consideration is the
- inability to revert deduplication status. If
- deduplication is enabled, data written, and then dedup
- is disabled, those blocks which were deduplicated will
- not be duplicated until they are next modified.</para>
+ inability to revert deduplication status. If data is
+ written when deduplication is enabled, disabling dedup
+ will not cause those blocks which were deduplicated to
+ be replicated until they are next modified.</para>
<para>Deduplication can also lead to some unexpected
situations. In particular deleting files may become much
More information about the svn-doc-head
mailing list