projects / mirror_zfs.git / blame
| Commit | Line | Data |
|---|---|---|
| 55d80e65 AR |
1 | .TH "ZFS\-MOUNT\-GENERATOR" "8" "ZFS" "zfs-mount-generator" "\"" |
| 2 | .SH "NAME" | |
| 3 | zfs\-mount\-generator \- generates systemd mount units for zfs | |
| 4 | .SH SYNOPSIS | |
| 5 | .B /lib/systemd/system-generators/zfs\-mount\-generator | |
| 6 | .sp | |
| 7 | .SH DESCRIPTION | |
| 8 | The zfs\-mount\-generator implements the \fBGenerators Specification\fP | |
| 9 | of | |
| 10 | .BR systemd (1), | |
| 11 | and is called during early boot to generate | |
| 12 | .BR systemd.mount (5) | |
| 13 | units for automatically mounted datasets. Mount ordering and dependencies | |
| 14 | are created for all tracked pools (see below). If a dataset has | |
| 15 | .BR canmount=on | |
| 16 | and | |
| 17 | .BR mountpoint | |
| 18 | set, the | |
| 19 | .BR auto | |
| 20 | mount option will be set, and a dependency for | |
| 21 | .BR local-fs.target | |
| 22 | on the mount will be created. | |
| 23 | ||
| 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 | |
| 26 | of the command | |
| 27 | .PP | |
| 28 | .RS 4 | |
| 29 | zfs list -H -oname,mountpoint,canmount | |
| 30 | .RE | |
| 31 | .PP | |
| 32 | for datasets that should be mounted by systemd, should be kept | |
| 33 | separate from the pool, at | |
| 34 | .PP | |
| 35 | .RS 4 | |
| 36 | .RI @sysconfdir@/zfs/zfs-list.cache/ POOLNAME | |
| 37 | . | |
| 38 | .RE | |
| 39 | .PP | |
| 40 | The cache file, if writeable, will be kept synchronized with the pool | |
| 41 | state by the ZEDLET | |
| 42 | .PP | |
| 43 | .RS 4 | |
| 44 | history_event-zfs-list-cacher.sh . | |
| 45 | .RE | |
| 46 | .PP | |
| 47 | .sp | |
| 48 | .SH SEE ALSO | |
| 49 | .BR zfs (5) | |
| 50 | .BR zfs-events (5) | |
| 51 | .BR zed (8) | |
| 52 | .BR zpool (5) | |
| 53 | .BR systemd (1) | |
| 54 | .BR systemd.target (5) | |
| 55 | .BR systemd.special (7) | |
| 56 | .BR systemd.mount (7) |