Race between zfs-share and zfs-mount services
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
This commit is contained in:
parent
693c1fc478
commit
453bb4791e
|
@ -5,6 +5,7 @@ After=nfs-server.service nfs-kernel-server.service
|
||||||
After=smb.service
|
After=smb.service
|
||||||
Before=rpc-statd-notify.service
|
Before=rpc-statd-notify.service
|
||||||
Wants=zfs-mount.service
|
Wants=zfs-mount.service
|
||||||
|
After=zfs-mount.service
|
||||||
PartOf=nfs-server.service nfs-kernel-server.service
|
PartOf=nfs-server.service nfs-kernel-server.service
|
||||||
PartOf=smb.service
|
PartOf=smb.service
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue