1 .TH "ZFS\-MOUNT\-GENERATOR" "8" "ZFS" "zfs-mount-generator" "\""
3 zfs\-mount\-generator \- generates systemd mount units for ZFS
5 .B /lib/systemd/system-generators/zfs\-mount\-generator
8 zfs\-mount\-generator implements the \fBGenerators Specification\fP
11 and is called during early boot to generate
13 units for automatically mounted datasets. Mount ordering and dependencies
14 are created for all tracked pools (see below). If a dataset has
20 mount option will be set, and a dependency for
22 on the mount will be created.
24 Because zfs pools may not be available very early in the boot process,
25 information on ZFS mountpoints must be stored separately. The output
29 zfs list -H -o name,mountpoint,canmount,atime,relatime,devices,exec,readonly,setuid,nbmand,encroot,keylocation
32 for datasets that should be mounted by systemd, should be kept
33 separate from the pool, at
36 .RI @sysconfdir@/zfs/zfs-list.cache/ POOLNAME
40 The cache file, if writeable, will be kept synchronized with the pool
44 history_event-zfs-list-cacher.sh .
49 To begin, enable tracking for the pool:
53 .RI @sysconfdir@/zfs/zfs-list.cache/ POOLNAME
56 Then, enable the tracking ZEDLET:
59 ln -s "@zfsexecdir@/zed.d/history_event-zfs-list-cacher.sh" "@sysconfdir@/zfs/zed.d"
61 systemctl enable zed.service
63 systemctl restart zed.service
66 Force the running of the ZEDLET by setting canmount=on for at least one dataset in the pool:
73 This forces an update to the stale cache file.
81 .BR systemd.target (5)
82 .BR systemd.special (7)