Missing zfs-list.cache folder causes zfs list cacher to fail

[Jules Blok]

The zfs-zed package sets up the history_event-zfs-list-cacher.sh script, but does not create the /etc/zfs/zfs-list.cache folder. This causes the script to fail to save the caching info that's required for the ZFS automount functionality to work in systemd.

More information on this can be found in: https://manpages.ubuntu.com/manpages/focal/en/man8/zfs-mount-generator.8.html

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: zfs-zed 2.1.9-2ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
Uname: Linux 6.2.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sat Apr 1 03:54:34 2023
InstallationDate: Installed on 2023-03-31 (0 days ago)
InstallationMedia: Ubuntu-Server 23.04 "Lunar Lobster" - Beta amd64 (20230329)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=linux
 XDG_RUNTIME_DIR=<set>
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)

[lo (piuh)]

Hi,

isn't that by design (intended) Because zfs-zed package is installed (e .g. default installation) but zfs-mount-generator should not be active in every case. So if I want to finally use zfs-mount-generator I have to manually create the /etc/zfs/zfs-list.cache folder? If it gets "corrected" man has to set package dependencies in a way that zfs-zed is not installed automatically.

Or am I wrong?

lopiuh

[lo (piuh)]

To be more clear:

https://manpages.debian.org/testing/zfsutils-linux/zfs-mount-generator.8.en.html
states: "To begin, enable tracking for the pool:
# touch /etc/zfs/zfs-list.cache/poolname "

So I am right. The missing directory in a default state is a feature, no bug.

Yours lopiuh

[Jules Blok (armada)]

The touch command would fail in that case, because the zfs-list.cache directory does not exist and touch will not automatically create the parent directory. So even if it's empty the folder should at least exist, even that manpage assumes it already exists.

[lo (piuh)]

I reported upstream

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075941

Yours

lopiuh