453bb4791e
When a system boots the zfs-mount.service and the zfs-share.service can start simultaneously. What may be unclear is that sharing a filesystem will first mount the filesystem if it's not already mounted. This means that both service can race to mount the same fileystem. This race can result in a SEGFAULT or EBUSY conditions. This change explicitly defines the start ordering between the two services such that the zfs-mount.service is solely responsible for mounting filesystems eliminating the race between "zfs mount -a" and "zfs share -a" commands. Reviewed-by: Sebastien Roy <sebastien.roy@delphix.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: George Wilson <george.wilson@delphix.com> Closes #9083 |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| 50-zfs.preset.in | ||
| Makefile.am | ||
| zfs-import-cache.service.in | ||
| zfs-import-scan.service.in | ||
| zfs-import.target.in | ||
| zfs-mount.service.in | ||
| zfs-share.service.in | ||
| zfs-volume-wait.service.in | ||
| zfs-volumes.target.in | ||
| zfs-zed.service.in | ||
| zfs.target.in | ||