> I believe the zed systemd unit should at the very least be modified
not to start inside containers
That can be done with ConditionVirtualization=!container
> (b) there were an /etc/default/zed which enabled one to disable zed
altogether.
Please don't do that. /etc/default files should never have been mis-used
for enabling/disabling services -- there already is update-rc.d
enable/disable for that (or the more direct systemctl enable/disable
now).
> we could have a unit list "RequiresFilesystem" with "zfs" and so have
zfs-zed kick in as soon as any zfs mount occurs
There is no direct way to express this; but IMHO a sufficient
approximation is to start it if a zfs file system exists? That can be
done with an udev rule like
ACTION!="remove", SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="zfs",
ENV{SYSTEMD_WANTS}+="zed.service"
Note that I don't know the precise value of ID_FS_TYPE for zpools, and
the precise name of the service you want to start.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1624540
Title:
please have lxd recommend zfs
Status in lxd package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
Confirmed
Bug description:
Since ZFS is now in Main (Bug #1532198), LXD should recommend the ZFS
userspace package, such that 'sudo lxd init' just works.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1624540/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
