From 4007f89319dfa124942e6d3952d3271a7d7a0bdb Mon Sep 17 00:00:00 2001 From: Matt Bentley Date: Sat, 23 Apr 2022 08:00:31 -0400 Subject: [PATCH] Added note about boot pool size consideration; fixes #296 Signed-off-by: Matt Bentley --- docs/Getting Started/Debian/Debian Bullseye Root on ZFS.rst | 5 +++++ docs/Getting Started/Debian/Debian Buster Root on ZFS.rst | 5 +++++ docs/Getting Started/Ubuntu/Ubuntu 18.04 Root on ZFS.rst | 5 +++++ docs/Getting Started/Ubuntu/Ubuntu 20.04 Root on ZFS.rst | 5 +++++ docs/Getting Started/Ubuntu/Ubuntu 22.04 Root on ZFS.rst | 5 +++++ 5 files changed, 25 insertions(+) diff --git a/docs/Getting Started/Debian/Debian Bullseye Root on ZFS.rst b/docs/Getting Started/Debian/Debian Bullseye Root on ZFS.rst index 91bf661..b33bbdb 100644 --- a/docs/Getting Started/Debian/Debian Bullseye Root on ZFS.rst +++ b/docs/Getting Started/Debian/Debian Bullseye Root on ZFS.rst @@ -159,6 +159,11 @@ Step 2: Disk Formatting virtio; otherwise, read the `troubleshooting <#troubleshooting>`__ section. - 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: diff --git a/docs/Getting Started/Debian/Debian Buster Root on ZFS.rst b/docs/Getting Started/Debian/Debian Buster Root on ZFS.rst index bd87edc..80b220b 100644 --- a/docs/Getting Started/Debian/Debian Buster Root on ZFS.rst +++ b/docs/Getting Started/Debian/Debian Buster Root on ZFS.rst @@ -178,6 +178,11 @@ Step 2: Disk Formatting virtio; otherwise, read the `troubleshooting <#troubleshooting>`__ section. - 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: diff --git a/docs/Getting Started/Ubuntu/Ubuntu 18.04 Root on ZFS.rst b/docs/Getting Started/Ubuntu/Ubuntu 18.04 Root on ZFS.rst index f51af94..86923ca 100644 --- a/docs/Getting Started/Ubuntu/Ubuntu 18.04 Root on ZFS.rst +++ b/docs/Getting Started/Ubuntu/Ubuntu 18.04 Root on ZFS.rst @@ -142,6 +142,11 @@ especially on systems that have more than one storage pool. KVM with virtio; otherwise, read the `troubleshooting <#troubleshooting>`__ section. - 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: diff --git a/docs/Getting Started/Ubuntu/Ubuntu 20.04 Root on ZFS.rst b/docs/Getting Started/Ubuntu/Ubuntu 20.04 Root on ZFS.rst index e6ee25d..92ed675 100644 --- a/docs/Getting Started/Ubuntu/Ubuntu 20.04 Root on ZFS.rst +++ b/docs/Getting Started/Ubuntu/Ubuntu 20.04 Root on ZFS.rst @@ -292,6 +292,11 @@ Step 2: Disk Formatting virtio; otherwise, read the `troubleshooting <#troubleshooting>`__ section. - 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: diff --git a/docs/Getting Started/Ubuntu/Ubuntu 22.04 Root on ZFS.rst b/docs/Getting Started/Ubuntu/Ubuntu 22.04 Root on ZFS.rst index 48b6d76..baefe25 100644 --- a/docs/Getting Started/Ubuntu/Ubuntu 22.04 Root on ZFS.rst +++ b/docs/Getting Started/Ubuntu/Ubuntu 22.04 Root on ZFS.rst @@ -206,6 +206,11 @@ Step 2: Disk Formatting virtio; otherwise, read the `troubleshooting <#troubleshooting>`__ section. - 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: