jacobpascual/openzfs-docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added note about boot pool size consideration; fixes #296

Browse Source 
Signed-off-by: Matt Bentley <mbentley@mbentley.net>
This commit is contained in:
Matt Bentley
2022-04-23 08:00:31 -04:00
committed by Richard Laager
parent 33b846f3e6
commit 4007f89319
5 changed files with 25 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/Getting Started/Debian/Debian Bullseye Root on ZFS.rst
View File

@@ -159,6 +159,11 @@ Step 2: Disk Formatting
virtio; otherwise, read the `troubleshooting <#troubleshooting>`__ virtio; otherwise, read the `troubleshooting <#troubleshooting>`__
section. section.
- For a mirror or raidz topology, use ``DISK1``, ``DISK2``, etc. - For a mirror or raidz topology, use ``DISK1``, ``DISK2``, etc.
- When choosing a boot pool size, consider how you will use the space. A
kernel and initrd may consume around 100M. If you have multiple kernels
and take snapshots, you may find yourself low on boot pool space,
especially if you need to regenerate your initramfs images, which may be
around 85M each. Size your boot pool appropriately for your needs.
#. If you are re-using a disk, clear it as necessary: #. If you are re-using a disk, clear it as necessary:

5
docs/Getting Started/Debian/Debian Buster Root on ZFS.rst
View File

@@ -178,6 +178,11 @@ Step 2: Disk Formatting
virtio; otherwise, read the `troubleshooting <#troubleshooting>`__ virtio; otherwise, read the `troubleshooting <#troubleshooting>`__
section. section.
- For a mirror or raidz topology, use ``DISK1``, ``DISK2``, etc. - For a mirror or raidz topology, use ``DISK1``, ``DISK2``, etc.
- When choosing a boot pool size, consider how you will use the space. A
kernel and initrd may consume around 100M. If you have multiple kernels
and take snapshots, you may find yourself low on boot pool space,
especially if you need to regenerate your initramfs images, which may be
around 85M each. Size your boot pool appropriately for your needs.
#. If you are re-using a disk, clear it as necessary: #. If you are re-using a disk, clear it as necessary:

5
docs/Getting Started/Ubuntu/Ubuntu 18.04 Root on ZFS.rst
View File

@@ -142,6 +142,11 @@ especially on systems that have more than one storage pool.
KVM with virtio; otherwise, read the KVM with virtio; otherwise, read the
`troubleshooting <#troubleshooting>`__ section. `troubleshooting <#troubleshooting>`__ section.
- For a mirror or raidz topology, use ``DISK1``, ``DISK2``, etc. - For a mirror or raidz topology, use ``DISK1``, ``DISK2``, etc.
- When choosing a boot pool size, consider how you will use the space. A kernel
and initrd may consume around 100M. If you have multiple kernels and take
snapshots, you may find yourself low on boot pool space, especially if you
need to regenerate your initramfs images, which may be around 85M each. Size
your boot pool appropriately for your needs.
2.2 If you are re-using a disk, clear it as necessary: 2.2 If you are re-using a disk, clear it as necessary:

5
docs/Getting Started/Ubuntu/Ubuntu 20.04 Root on ZFS.rst
View File

@@ -292,6 +292,11 @@ Step 2: Disk Formatting
virtio; otherwise, read the `troubleshooting <#troubleshooting>`__ virtio; otherwise, read the `troubleshooting <#troubleshooting>`__
section. section.
- For a mirror or raidz topology, use ``DISK1``, ``DISK2``, etc. - For a mirror or raidz topology, use ``DISK1``, ``DISK2``, etc.
- When choosing a boot pool size, consider how you will use the space. A
kernel and initrd may consume around 100M. If you have multiple kernels
and take snapshots, you may find yourself low on boot pool space,
especially if you need to regenerate your initramfs images, which may be
around 85M each. Size your boot pool appropriately for your needs.
#. If you are re-using a disk, clear it as necessary: #. If you are re-using a disk, clear it as necessary:

5
docs/Getting Started/Ubuntu/Ubuntu 22.04 Root on ZFS.rst
View File

@@ -206,6 +206,11 @@ Step 2: Disk Formatting
virtio; otherwise, read the `troubleshooting <#troubleshooting>`__ virtio; otherwise, read the `troubleshooting <#troubleshooting>`__
section. section.
- For a mirror or raidz topology, use ``DISK1``, ``DISK2``, etc. - For a mirror or raidz topology, use ``DISK1``, ``DISK2``, etc.
- When choosing a boot pool size, consider how you will use the space. A
kernel and initrd may consume around 100M. If you have multiple kernels
and take snapshots, you may find yourself low on boot pool space,
especially if you need to regenerate your initramfs images, which may be
around 85M each. Size your boot pool appropriately for your needs.
#. If you are re-using a disk, clear it as necessary: #. If you are re-using a disk, clear it as necessary: