[Bug 253364] FreeBSD can not boot where a non-boot OpenZFS pool includes a filesystem that uses ztsd compression
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Feb 9 02:25:42 UTC 2021
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253364
Bug ID: 253364
Summary: FreeBSD can not boot where a non-boot OpenZFS pool
includes a filesystem that uses ztsd compression
Product: Documentation
Version: Latest
Hardware: Any
URL: https://cgit.freebsd.org/src/tree/UPDATING
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Documentation
Assignee: doc at FreeBSD.org
Reporter: grahamperrin at gmail.com
CC: freqlabs at FreeBSD.org, mmacy at FreeBSD.org
Created attachment 222286
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=222286&action=edit
Information about the mobile hard disk drive and its OpenZFS pool
<https://cgit.freebsd.org/src/commit/UPDATING?id=5db7b015e9aa18e129d73992583491702e4a5206>
(2020-08-25) offered relatively strong advice in the context of
updating/upgrading FreeBSD:
> … Do not upgrade root pools until
> the loader is updated to support zstd. …
In addition, I find it impossible to boot where an available non-boot pool uses
zstd:
* first observed with 13.0-CURRENT
* also observed with 14.0-CURRENT.
I assume that the issue will also be observable with 12.2-RELEASE-p3 (I do not
yet have the hardware resources to test), if this is true then it's not
_solely_ an UPDATING issue.
Hardware probe at <https://bsd-hardware.info/?probe=72137c63f8> (with the drive
connected after boot), and the attached text file includes pool-related
information. This pool used OpenZFS from the outset, it was not upgraded.
In my case: not a showstopper. With the drive for the non-boot pool external,
on USB, it's easy enough to disconnect before attempting to boot the computer.
External versus internal
========================
If a zstd-compressed filesystem is on a non-boot pool on an _internal_ drive: I
imagine that things will be less easy …
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-doc
mailing list