Minor wording fixes for the recently committed ZFS section.
Reviewed by: bjk Approved by: bcr (mentor)
This commit is contained in:
parent
e22c3b2753
commit
3ab6e86ad7
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=40378
1 changed files with 6 additions and 5 deletions
|
@ -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
|
||||
|
|
Loading…
Reference in a new issue