@pitti, the ID_FS_TYPE is zfs_member, not zfs. The service is, as you
listed, zed.service. Modifying your rule then is:
ACTION!="remove", SUBSYSTEM=="block", ENV{ID_FS_TYPE}=="zfs_member",
ENV{SYSTEMD_WANTS}+="zed.service"
However, if zed.service is going to exit if there is no pool imported,
this udev rule may not help. The udev event is going to fire before the
pool is imported.
@stgraber, running zed is less important for loopback devices. So
between that and catching it on reboot, we might be "close enough".
--
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 : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
