Skip to content
Skip to this exploration
All explorations

Practical self-hosting · intermediate

16 · The upgrade boundary you cannot click backward through

Separate software upgrades from storage-format compatibility.

10 min 5 sectionsv1

What you can take away

  • Identify rollback gates before enabling pool features.
  • Make a decision worksheet with current software, proposed software, current features, proposed features, rescue environment, backup verification date, and stop condition

Your trail through this idea

Checking saved progress…

Ian’s historical Ubuntu-upgrade question was motivated by ZFS capabilities. That makes an important distinction visible: installing newer software and changing what a storage pool requires are separate decisions.

Prerequisite: complete the preceding lesson or bring its worksheet.

Mark sections complete when you choose. Reading alone does not mark them.

Understand the system

OpenZFS documents zpool upgrade as management of pool versions and feature flags. Enabling features can affect which systems can access a pool. A successful OS rollback therefore does not guarantee that the older environment can use a pool changed by the newer one. Compatibility must include the recovery environment, not just the current host.

There are at least three review gates: host software compatibility, pool feature compatibility, and verified data recovery. A snapshot on the same pool does not by itself solve loss of pool accessibility. Record what would be recoverable from independent backups before crossing a storage-format boundary.

Checking saved progress…

Work through the case

Original tabletop: a new host can import a practice pool, but an older rescue image lacks support for a newly enabled feature. The application package versions are irrelevant to that immediate problem. The proposed rollback must specify both the operating environment and how the data becomes accessible again.

Checking saved progress…

Make something useful

Try this

Original exercise

Make a decision worksheet with current software, proposed software, current features, proposed features, rescue environment, backup verification date, and stop condition. Use fictional version labels if you do not have a test system. The lesson deliberately performs no pool upgrade. Review the exact installed-version manual before any real storage action.

Checking saved progress…

Check your reasoning

A quick check · for your own learning

Why can an OS rollback fail to restore ZFS access?

Choose one answer

A self-study prompt. You can retry; this is not an exam.

Checking saved progress…

Keep the result and follow the sources

Success is the ability to point at the irreversible or compatibility-changing step before taking it. If the recovery path depends on the old environment reading the new pool, prove that compatibility rather than assuming it.

Sources and scope

  • Primary documentation or archival source, reviewed 14 November 2026. Additional direct links appear beside the claims they support.
  • Editorial basis: Ian's historical self-hosting questions and current repository inspection informed the case selection. Historical requests do not establish current deployment. Private chat records, credentials and host details are excluded.
  • Examples and exercises are original educational synthesis. External sources support the stated technical or historical context, not every hypothetical scenario.
Checking saved progress…

These checks are for reflection and practice. Your answers and reflection notes are not sent anywhere.

Back to all explorations