all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Dylan Whyte <d.whyte@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: Re: [pve-devel] [PATCH docs] zfs: add section on zpool-features
Date: Wed, 31 Mar 2021 11:19:36 +0200	[thread overview]
Message-ID: <76b8d8ae-4d1a-d62a-fd52-7efc3800d987@proxmox.com> (raw)
In-Reply-To: <20210330182604.15292-1-s.ivanov@proxmox.com>

Hi,

I've just made some small corrections and wording changes that sounded 
right.


Reviewed-by: Dylan Whyte<d.whyte@proxmox.com>

On 3/30/21 8:26 PM, Stoiko Ivanov wrote:
> primarily in order to warn users booting from ZFS with grub.
>
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
>   local-zfs.adoc | 36 ++++++++++++++++++++++++++++++++++++
>   1 file changed, 36 insertions(+)
>
> diff --git a/local-zfs.adoc b/local-zfs.adoc
> index 4819678..a003a7c 100644
> --- a/local-zfs.adoc
> +++ b/local-zfs.adoc
> @@ -699,3 +699,39 @@ in the pool will opt in for small file blocks).
>   ----
>   # zfs set special_small_blocks=0 <pool>/<filesystem>
>   ----
> +
> +[[sysadmin_zfs_features]]
> +ZFS Pool Features
> +~~~~~~~~~~~~~~~~~
> +
> +Changes to the on-disk format in ZFS are only done between major version changes
s/done/made/
> +and are specified through *features*. All features and the general mechanism
s/features and the general/features, as well as the general/
> +are well documented in the `zpool-features(5)` manpage.
> +
> +Since enabling new features can render a pool not importable by an older version
> +of ZFS, this needs to be actively done by the administrator by running
s/actively done/done actively/

s/administrator by/administrator, by/
> +`zpool upgrade` on the pool (see the `zpool-upgrade(8)` manpage).
> +
> +Unless you need to use one of the new features there is no upside to enabling
s/features there/features, there/
> +the new features.
s/the new features/them/
> +
> +On the other hand there are a few downsides on enabling new features:
s/On the other hand/In fact,/

s/a few/some/

s/downsides on/downsides to/
> +
> +* A system, with root on ZFS, still booting with `grub` will become unbootable
s/A system, with/A system with/

s/still booting with `grub`/that still boots using `grub`/
> +  if a new feature is active on the rpool, due to the incompatible
> +  implementation of ZFS in grub.
> +* The system will not be able to boot with an older kernel, which is still
> +  shipping the old ZFS modules
s/which is still shipping/which still ships with/

*Add full stop
> +* Booting an older {pve} ISO to do repair a non-booting system likewise will not
s/likewise will/will likewise/
s/to do repair/to repair/
> +  work
*Add full stop
> +
> +IMPORTANT: Do not upgrade your rpool if your system is still booted with `grub`.
> +Systems installed before PVE 5.4, and systems booting with legacy boot (see
> +xref:sysboot_determine_bootloader_used[how to determine the bootloader]), as
> +this will render your system unbootable.
I would change/rearrange to:

IMPORTANT: Do not upgrade your rpool, if your system is still booted 
with `grub`,

as this will render your system unbootable. This includes systems 
installed before

{pve} 5.4 and systems that boot using legacy boot (see

xref:sysboot_determine_bootloader_used[how to determine the bootloader]).
> +
> +.Enable new features for a pool:
> +----
> +# zpool upgrade <pool>
> +----
> +




      parent reply	other threads:[~2021-03-31  9:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30 18:26 Stoiko Ivanov
2021-03-31  7:04 ` Aaron Lauterer
2021-03-31  9:19 ` Dylan Whyte [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=76b8d8ae-4d1a-d62a-fd52-7efc3800d987@proxmox.com \
    --to=d.whyte@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.ivanov@proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal