Unit Instance

HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "translation": "https://translate-dev.freebsd.org/api/translations/freebsd-doc/boooks_handbook/en/?format=api",
    "source": [
        "<emphasis><varname>vfs.zfs.resilver_delay</varname></emphasis> - Number of milliseconds of delay inserted between each I/O during a <link linkend=\"zfs-term-resilver\">resilver</link>. To ensure that a resilver does not interfere with the normal operation of the pool, if any other I/O is happening the resilver will delay between each command. This value controls the limit of total <acronym>IOPS</acronym> (I/Os Per Second) generated by the resilver. The granularity of the setting is determined by the value of <varname>kern.hz</varname> which defaults to 1000 ticks per second. This setting may be changed, resulting in a different effective <acronym>IOPS</acronym> limit. The default value is 2, resulting in a limit of: 1000 ticks/sec / 2 = 500 <acronym>IOPS</acronym>. Returning the pool to an <link linkend=\"zfs-term-online\">Online</link> state may be more important if another device failing could <link linkend=\"zfs-term-faulted\">Fault</link> the pool, causing data loss. A value of 0 will give the resilver operation the same priority as other operations, speeding the healing process. The speed of resilver is only limited when there has been other recent activity on the pool, as determined by <link linkend=\"zfs-advanced-tuning-scan_idle\"><varname>vfs.zfs.scan_idle</varname></link>. This value can be adjusted at any time with <citerefentry><refentrytitle>sysctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>."
    ],
    "previous_source": "",
    "target": [
        "<emphasis><varname>vfs.zfs.resilver_delay</varname></emphasis> - Number of milliseconds of delay inserted between each I/O during a <link linkend=\"zfs-term-resilver\">resilver</link>. To ensure that a resilver does not interfere with the normal operation of the pool, if any other I/O is happening the resilver will delay between each command. This value controls the limit of total <acronym>IOPS</acronym> (I/Os Per Second) generated by the resilver. The granularity of the setting is determined by the value of <varname>kern.hz</varname> which defaults to 1000 ticks per second. This setting may be changed, resulting in a different effective <acronym>IOPS</acronym> limit. The default value is 2, resulting in a limit of: 1000 ticks/sec / 2 = 500 <acronym>IOPS</acronym>. Returning the pool to an <link linkend=\"zfs-term-online\">Online</link> state may be more important if another device failing could <link linkend=\"zfs-term-faulted\">Fault</link> the pool, causing data loss. A value of 0 will give the resilver operation the same priority as other operations, speeding the healing process. The speed of resilver is only limited when there has been other recent activity on the pool, as determined by <link linkend=\"zfs-advanced-tuning-scan_idle\"><varname>vfs.zfs.scan_idle</varname></link>. This value can be adjusted at any time with <citerefentry><refentrytitle>sysctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>."
    ],
    "id_hash": 4867112643066994239,
    "content_hash": 4867112643066994239,
    "location": "book.translate.xml:42688",
    "context": "",
    "note": "(itstool) path: listitem/para\n(itstool) id: book.translate.xml#zfs-advanced-tuning-resilver_delay",
    "flags": "",
    "labels": [],
    "state": 100,
    "fuzzy": false,
    "translated": true,
    "approved": false,
    "position": 6988,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": false,
    "num_words": 181,
    "source_unit": "https://translate-dev.freebsd.org/api/units/157903/?format=api",
    "priority": 100,
    "id": 157903,
    "web_url": "https://translate-dev.freebsd.org/translate/freebsd-doc/boooks_handbook/en/?checksum=c38b75296bd21e3f",
    "url": "https://translate-dev.freebsd.org/api/units/157903/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2020-04-18T18:15:42.187430Z"
}