On Fri 12/01/2024 at 06:49, Jan Ingvoldstad <frett...@gmail.com> wrote:
> ...
> It is far more concerning that one cannot trust that cp actually copies a
> file, and this is a blocker for installing the ZFS packages in Debian.
The update in bookworm-backports to 2.2.2-3 allegedly fixes this issue.
I have installed it and at least rebooted :)
I have had ZFS on root since Buster, and have upgraded to each new stable
release since then.
I had wondered recently if the Debian wiki's recommendation [1] of installing
from "stable-backports", and the statement that
"Upstream stable patches will be tracked and compatibility is always maintained"
was to suggest use of the actual "stable-backports" repo, and that the
compatibility guarantee meant that they cater for any potential ZFS issues
arising for non-upgraded systems after new release time. On closer inspection,
the line the wiki provides to add this to sources.list actually adds the
codename-backports repo (currently "bookworm-backports"). "stable-backports"
also appears to be an alias that apt understands as referring to
{codename}-backports for whatever current stable is, and use of the actual
"stable-backports" repo is not recommended or implied.
Is the Debian wiki advice re installing ZFS from backports applicable in all
circumstances? What would be the suggested approach for installing with ZFS on
root or re-pointing apt at backports for ZFS immediately after [upgrading to] a
new stable release? Do backports even exist at that point? If so, after a
release upgrade, can you install the same version of eg. zfs-dkms from
backports as a sort of special case for the purposes of changing the repo? Or
do you just have to watch and wait for new ZFS backports?
OpenZFS instructions [2] for root on ZFS suggest using bookworm not
bookworm-backports, so I wondered if an initial lack of backports might be the
reason.
Thanks,
Gareth
[1] https://wiki.debian.org/ZFS#Status
[2]
https://openzfs.github.io/openzfs-docs/Getting%20Started/Debian/Debian%20Bookworm%20Root%20on%20ZFS.html#step-1-prepare-the-install-environment
