From owner-svn-doc-head@freebsd.org Sun Aug 19 11:51:31 2018 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D5D0C108A90D; Sun, 19 Aug 2018 11:51:30 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 851ED72DB5; Sun, 19 Aug 2018 11:51:30 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 677D925DE0; Sun, 19 Aug 2018 11:51:30 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w7JBpUBt074280; Sun, 19 Aug 2018 11:51:30 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w7JBpUL2074279; Sun, 19 Aug 2018 11:51:30 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201808191151.w7JBpUL2074279@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Sun, 19 Aug 2018 11:51:30 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52156 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/faq X-SVN-Commit-Revision: 52156 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Aug 2018 11:51:31 -0000 Author: bcr Date: Sun Aug 19 11:51:30 2018 New Revision: 52156 URL: https://svnweb.freebsd.org/changeset/doc/52156 Log: Wrap long lines, put some content on the same line as the opening tags, and properly intent nested tags to make textproc/igor happy. 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 Sun Aug 19 07:19:18 2018 (r52155) +++ head/en_US.ISO8859-1/books/faq/book.xml Sun Aug 19 11:51:30 2018 (r52156) @@ -15,7 +15,9 @@ stable/10/"> ]> - + Frequently Asked Questions for &os; &rel2.relx; and &rel.relx; @@ -546,7 +548,7 @@ Every significant release of &os; is available via anonymous FTP from the &os; + xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/">&os; FTP site: @@ -878,7 +880,7 @@ Where the format is html-split, the files are bundled up using &man.tar.1;. The resulting - .tar file is then compressed + .tar is then compressed using the compression schemes detailed in the next point. @@ -2411,19 +2413,19 @@ kern.timecounter.hardware: TSC -> i8254 - If the installed &os; version lags - significantly behind -CURRENT or - -STABLE, update the - Ports Collection using the instructions in If the installed &os; version lags significantly + behind -CURRENT or + -STABLE, update the Ports Collection + using the instructions in Using the Ports Collection. If the system is up-to-date, someone might have committed a change to the port which works for -CURRENT but which broke the port for -STABLE. - Submit + Submit a bug report, since the Ports Collection is supposed to - work - for both the -CURRENT and + work for both the -CURRENT and -STABLE branches. @@ -2696,9 +2698,8 @@ kern.timecounter.hardware: TSC -> i8254 - The make - buildkernel command did not complete - successfully. The make + The make buildkernel did not + complete successfully. The make buildkernel target relies on files generated by the make buildworld target to complete its job correctly. @@ -3356,8 +3357,8 @@ kern.sched.name: ULE This section of the Handbook - describes how to do this. + xlink:href="&url.books.handbook;/adding-swap-space.html">of + the Handbook describes how to do this. @@ -3407,156 +3408,154 @@ kern.sched.name: ULE - ZFS + ZFS - - - - What is the minimum amount of RAM one should have to - run ZFS? - + + + + What is the minimum amount of RAM one should have to + run ZFS? + - - A minimum of 4GB of RAM is required for comfortable - usage, but individual workloads can vary widely. - - + + A minimum of 4GB of RAM is required for comfortable + usage, but individual workloads can vary widely. + + - - - What is the ZIL and when does it get used? - + + + What is the ZIL and when does it get used? + - - The ZIL (ZFS - intent log) is a write log used to implement posix write - commitment semantics across crashes. Normally writes - are bundled up into transaction groups and written to - disk when filled (Transaction Group - Commit). However syscalls like &man.fsync.2; - 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. In the event of a crash the - last valid timestamp is found and missing data is merged - in from the ZIL. - - + + The ZIL (ZFS + intent log) is a write log used to implement posix write + commitment semantics across crashes. Normally writes are + bundled up into transaction groups and written to disk + when filled (Transaction Group Commit). + However syscalls like &man.fsync.2; 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. In the event of a crash the last valid + timestamp is found and missing data is merged in from the + ZIL. + + - - - Do I need a SSD for ZIL? - + + + Do I need a SSD for ZIL? + - - By default, ZFS stores the ZIL in the pool with all - the data. If an application has a heavy write load, - storing the ZIL in a separate device that has very fast - synchronous, sequential write performance can improve - overall system. For other workloads, a SSD is unlikely - to make much of an improvement. - - + + By default, ZFS stores the ZIL in the pool with all + the data. If an application has a heavy write load, + storing the ZIL in a separate device that has very fast + synchronous, sequential write performance can improve + overall system. For other workloads, a SSD is unlikely to + make much of an improvement. + + - - - What is the L2ARC? - + + + What is the L2ARC? + - - The L2ARC is a read cache stored - on a fast device such as an SSD. - This cache is not persistent across reboots. Note that - RAM is used as the first layer of cache and the L2ARC is - only needed if there is insufficient RAM. + + The L2ARC is a read cache stored on + a fast device such as an SSD. This + cache is not persistent across reboots. Note that RAM is + used as the first layer of cache and the L2ARC is only + needed if there is insufficient RAM. - L2ARC needs space in the ARC to index it. So, - perversely, a working set that fits perfectly in the - ARC will not fit perfectly any more if a L2ARC is used - because part of the ARC is holding the L2ARC index, - pushing part of the working set into the L2ARC which is - slower than RAM. - - + L2ARC needs space in the ARC to index it. So, + perversely, a working set that fits perfectly in the ARC + will not fit perfectly any more if a L2ARC is used because + part of the ARC is holding the L2ARC index, pushing part + of the working set into the L2ARC which is slower than + RAM. + + - - - Is enabling deduplication advisable? - + + + Is enabling deduplication advisable? + - - Generally speaking, no. + + Generally speaking, no. - Deduplication takes up a significant amount of RAM - and may slow down read and write disk access times. - Unless one is storing data that is 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 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. + Deduplication takes up a significant amount of RAM and + may slow down read and write disk access times. Unless + one is storing data that is 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 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. - Deduplication can also lead to some unexpected - situations. In particular, deleting files may become - much slower. - - + Deduplication can also lead to some unexpected + situations. In particular, deleting files may become much + slower. + + - - - I cannot delete or create files on my ZFS pool. - How can I fix this? - + + + I cannot delete or create files on my ZFS pool. How + can I fix this? + - - This could happen because the pool is 100% full. - ZFS requires space on the disk to write transaction - metadata. To restore the pool to a usable state, - truncate the file to delete: + + This could happen because the pool is 100% full. ZFS + requires space on the disk to write transaction metadata. + To restore the pool to a usable state, truncate the file + to delete: - &prompt.user; truncate -s 0 unimportant-file + &prompt.user; truncate -s 0 unimportant-file - File truncation works because a new transaction is - not started, new spare blocks are created - instead. + File truncation works because a new transaction is not + started, new spare blocks are created instead. - - On systems with additional ZFS dataset tuning, - such as deduplication, the space may not be - immediately available - - - + + On systems with additional ZFS dataset tuning, such + as deduplication, the space may not be immediately + available + + + - - - Does ZFS support TRIM for Solid State Drives? - + + + Does ZFS support TRIM for Solid State Drives? + - - ZFS TRIM support was added to &os; 10-CURRENT - with revision r240868. ZFS TRIM - support was added to all &os;-STABLE branches in - r252162 and - r251419, respectively. + + ZFS TRIM support was added to &os; 10-CURRENT + with revision r240868. ZFS TRIM + support was added to all &os;-STABLE branches in + r252162 and + r251419, respectively. - ZFS TRIM is enabled by default, and can be turned - off by adding this line to - /etc/sysctl.conf: + ZFS TRIM is enabled by default, and can be turned off + by adding this line to + /etc/sysctl.conf: - vfs.zfs.trim_disable=1 + vfs.zfs.trim_disable=1 - - ZFS TRIM may not work with all configurations, - such as a ZFS filesystem on a GELI-backed - device. - - - - + + ZFS TRIM may not work with all configurations, such + as a ZFS filesystem on a GELI-backed device. + + + + @@ -3675,15 +3674,15 @@ kern.sched.name: ULE Restart the system using boot -s at the loader prompt to enter single-user mode. When prompted for a shell pathname, press - Enter and run mount - -urw / to re-mount the root file system in + Enter and run mount -urw + / to re-mount the root file system in read/write mode. You may also need to run mount -a -t ufs to mount the file system where your - favorite editor is defined. If that editor is on - a network file system, either configure - the network manually before mounting the network file - systems, or use an editor which resides on a local file - system, such as &man.ed.1;. + favorite editor is defined. If that editor is on a + network file system, either configure the network manually + before mounting the network file systems, or use an editor + which resides on a local file system, such as + &man.ed.1;. In order to use a full screen editor such as &man.vi.1; or &man.emacs.1;, run @@ -3709,7 +3708,7 @@ kern.sched.name: ULE See the Handbook entry on printing for troubleshooting - tips. + tips. @@ -4112,10 +4111,10 @@ options SYSVMSG # enable for messaging The system is running at securelevel greater than 0. - Lower the securelevel and try again. For - more information, see the FAQ - entry on securelevel and the &man.init.8; manual - page. + Lower the securelevel and try again. For more + information, see the + FAQ entry on securelevel and + the &man.init.8; manual page. @@ -4416,7 +4415,7 @@ options SYSVMSG # enable for messaging/etc/X11/xorg.conf, as seen in this example: - Section "InputDevice" + Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "auto" @@ -5262,16 +5261,13 @@ Key F15 A A Menu Workplace Nop

- - Configure your kernel with these settings: - -include GENERIC + Configure your kernel with these settings: + + include GENERIC ident GENERIC-IPV6ONLY makeoptions MKMODULESENV+="WITHOUT_INET_SUPPORT=" nooptions INET -nodevice gre - - +nodevice gre @@ -6625,8 +6621,8 @@ hint.sio.7.irq="12" See the Translation - FAQ in the &os; Documentation Project - Primer. + FAQ in the &os; Documentation + Project Primer. @@ -6640,11 +6636,10 @@ hint.sio.7.irq="12" The FreeBSD.org mail - system implements some - Postfix checks on incoming mail - and rejects mail that is either from misconfigured relays - or otherwise appears likely to be spam. Some of the - specific requirements are: + system implements some Postfix + checks on incoming mail and rejects mail that is either + from misconfigured relays or otherwise appears likely to + be spam. Some of the specific requirements are: