Attachment #233342 for bug #263332

Lines 132-137 A 32-bit kernel can only use the first 2 GB of RAM. Link Here

(-)b/documentation/content/en/books/handbook/bsdinstall/_index.adoc (-1 / +2 lines)
132	== Pre-Installation Tasks	132	== Pre-Installation Tasks
133		133
134	Once it has been determined that the system meets the minimum hardware requirements for installing FreeBSD, the installation file should be downloaded and the installation media prepared.	134	Once it has been determined that the system meets the minimum hardware requirements for installing FreeBSD, the installation file should be downloaded and the installation media prepared.
		135	An alternative is to use virtualization (crossref:virtualization[virtualization,Virtualization]) which allows multiple operating systems to run at the same time without modifying any disk partitions.
135	Before doing this, check that the system is ready for an installation by verifying the items in this checklist:	136	Before doing this, check that the system is ready for an installation by verifying the items in this checklist:
136		137
137	[.procedure]	138	[.procedure]
Lines 169-175 Since the possibility of selecting the wrong partition exists, always backup any Link Here
169	====	170	====
170	+	171	+
171	Disk partitions containing different operating systems make it possible to install multiple operating systems on one computer.	172	Disk partitions containing different operating systems make it possible to install multiple operating systems on one computer.
172	An alternative is to use virtualization (crossref:virtualization[virtualization,Virtualization]) which allows multiple operating systems to run at the same time without modifying any disk partitions.	173	Virtualization (crossref:virtualization[virtualization,Virtualization]) allows multiple operating systems to run at the same time without modifying any disk partitions.
173	. Collect Network Information	174	. Collect Network Information
174	+	175	+
175	Some FreeBSD installation methods require a network connection in order to download the installation files.	176	Some FreeBSD installation methods require a network connection in order to download the installation files.

Lines 324-330 The Linux system call vector contains, among other things, a list of `sysent[]` Link Here

(-)b/documentation/content/en/books/handbook/linuxemu/_index.adoc (-1 / +1 lines)
324	When a system call is called by the Linux binary, the trap code dereferences the system call function pointer off the `proc` structure, and gets the Linux, not the FreeBSD, system call entry points.	324	When a system call is called by the Linux binary, the trap code dereferences the system call function pointer off the `proc` structure, and gets the Linux, not the FreeBSD, system call entry points.
325		325
326	Linux mode dynamically _reroots_ lookups.	326	Linux mode dynamically _reroots_ lookups.
327	This is, in effect, equivalent to `union` to file system mounts.	327	This is, in effect, equivalent to `union` file system mounts.
328	First, an attempt is made to look up the file in [.filename]#/compat/linux/original-path#.	328	First, an attempt is made to look up the file in [.filename]#/compat/linux/original-path#.
329	If that fails, the lookup is done in [.filename]#/original-path#.	329	If that fails, the lookup is done in [.filename]#/original-path#.
330	This makes sure that binaries that require other binaries can run.	330	This makes sure that binaries that require other binaries can run.





ZFS is an advanced file system designed to solve major problems found in previous storage subsystem software.

Originally developed at Sun(TM), ongoing open source ZFS development has moved to the http://openzfs.org[OpenZFS Project].

ZFS has three major design goals:


[[zfs-zpool-create]]
=== Creating and Destroying Storage Pools

Creating a ZFS storage pool requires permanent decisions, as the pool structure cannot change after creation.
The most important decision is which types of vdevs to group the physical disks into. 
See the list of <<zfs-term-vdev,vdev types>> for details about the possible options.
After creating the pool, most vdev types do not allow adding disks to the vdev.

[[zfs-zpool-attach]]
=== Adding and Removing Devices

Two ways exist for adding disks to a pool: attaching a disk to an existing vdev with `zpool attach`, or adding vdevs to the pool with `zpool add`.
Some <<zfs-term-vdev,vdev types>> allow adding disks to the vdev after creation.

A pool created with a single disk lacks redundancy.

[[zfs-links]]
== Further Resources

* http://openzfs.org[OpenZFS]
* https://wiki.freebsd.org/ZFSTuningGuide[FreeBSD Wiki - ZFS Tuning]
* http://docs.oracle.com/cd/E19253-01/819-5461/index.html[Oracle Solaris ZFS Administration Guide]
* https://calomel.org/zfs_raid_speed_capacity.html[Calomel Blog - ZFS Raidz Performance, Capacity and Integrity]

[[zfs-term]]

====
Using an entire disk as part of a bootable pool is strongly discouraged, as this may render the pool unbootable.
Likewise, you should not use an entire disk as part of a mirror or RAID-Z vdev.
Reliably determining the size of an unpartitioned disk at boot time is impossible and there's no place to put in boot code.
====

* [[zfs-term-vdev-file]] _File_ - Regular files may make up ZFS pools, which is useful for testing and experimentation. Use the full path to the file as the device path in `zpool create`.

Return to bug 263332

Lines 50-56 endif::[] Link Here

(-)b/documentation/content/en/books/handbook/zfs/_index.adoc (-6 / +5 lines)
50		50
51	ZFS is an advanced file system designed to solve major problems found in previous storage subsystem software.	51	ZFS is an advanced file system designed to solve major problems found in previous storage subsystem software.
52		52
53	Originally developed at Sun(TM), ongoing open source ZFS development has moved to the http://open-zfs.org[OpenZFS Project].	53	Originally developed at Sun(TM), ongoing open source ZFS development has moved to the http://openzfs.org[OpenZFS Project].
54		54
55	ZFS has three major design goals:	55	ZFS has three major design goals:
56		56
Lines 488-494 The <<zfs-zfs,`zfs`>> utility allows creating, destroying, and managing datasets Link Here
488	[[zfs-zpool-create]]	488	[[zfs-zpool-create]]
489	=== Creating and Destroying Storage Pools	489	=== Creating and Destroying Storage Pools
490		490
491	Creating a ZFS storage pool (_zpool_) requires permanent decisions, as the pool structure cannot change after creation.	491	Creating a ZFS storage pool requires permanent decisions, as the pool structure cannot change after creation.
492	The most important decision is which types of vdevs to group the physical disks into.	492	The most important decision is which types of vdevs to group the physical disks into.
493	See the list of <<zfs-term-vdev,vdev types>> for details about the possible options.	493	See the list of <<zfs-term-vdev,vdev types>> for details about the possible options.
494	After creating the pool, most vdev types do not allow adding disks to the vdev.	494	After creating the pool, most vdev types do not allow adding disks to the vdev.
Lines 580-586 This can cause undefined behavior in applications which had open files on those Link Here
580	[[zfs-zpool-attach]]	580	[[zfs-zpool-attach]]
581	=== Adding and Removing Devices	581	=== Adding and Removing Devices
582		582
583	Two ways exist for adding disks to a zpool: attaching a disk to an existing vdev with `zpool attach`, or adding vdevs to the pool with `zpool add`.	583	Two ways exist for adding disks to a pool: attaching a disk to an existing vdev with `zpool attach`, or adding vdevs to the pool with `zpool add`.
584	Some <<zfs-term-vdev,vdev types>> allow adding disks to the vdev after creation.	584	Some <<zfs-term-vdev,vdev types>> allow adding disks to the vdev after creation.
585		585
586	A pool created with a single disk lacks redundancy.	586	A pool created with a single disk lacks redundancy.
Lines 2692-2700 For a more detailed list of recommendations for ZFS-related tuning, see https:// Link Here
2692	[[zfs-links]]	2692	[[zfs-links]]
2693	== Further Resources	2693	== Further Resources
2694		2694
2695	* http://open-zfs.org[OpenZFS]	2695	* http://openzfs.org[OpenZFS]
2696	* https://wiki.freebsd.org/ZFSTuningGuide[FreeBSD Wiki - ZFS Tuning]	2696	* https://wiki.freebsd.org/ZFSTuningGuide[FreeBSD Wiki - ZFS Tuning]
2697	* http://docs.oracle.com/cd/E19253-01/819-5461/index.html[Oracle Solaris ZFS Administration Guide]
2698	* https://calomel.org/zfs_raid_speed_capacity.html[Calomel Blog - ZFS Raidz Performance, Capacity and Integrity]	2697	* https://calomel.org/zfs_raid_speed_capacity.html[Calomel Blog - ZFS Raidz Performance, Capacity and Integrity]
2699		2698
2700	[[zfs-term]]	2699	[[zfs-term]]
Lines 2725-2731 a\|A pool consists of one or more vdevs, which themselves are a single disk or a Link Here
2725	====	2724	====
2726	Using an entire disk as part of a bootable pool is strongly discouraged, as this may render the pool unbootable.	2725	Using an entire disk as part of a bootable pool is strongly discouraged, as this may render the pool unbootable.
2727	Likewise, you should not use an entire disk as part of a mirror or RAID-Z vdev.	2726	Likewise, you should not use an entire disk as part of a mirror or RAID-Z vdev.
2728	Reliably determining the size of an unpartitioned disk at boot time is impossible and because there's no place to put in boot code.	2727	Reliably determining the size of an unpartitioned disk at boot time is impossible and there's no place to put in boot code.
2729	====	2728	====
2730		2729
2731	* [[zfs-term-vdev-file]] _File_ - Regular files may make up ZFS pools, which is useful for testing and experimentation. Use the full path to the file as the device path in `zpool create`.	2730	* [[zfs-term-vdev-file]] _File_ - Regular files may make up ZFS pools, which is useful for testing and experimentation. Use the full path to the file as the device path in `zpool create`.