aboutsummaryrefslogtreecommitdiffstats
path: root/cmd/mount_zfs
diff options
context:
space:
mode:
authorTim Chase <[email protected]>2013-11-06 23:55:18 -0600
committerBrian Behlendorf <[email protected]>2013-11-08 10:45:14 -0800
commitfd4f76160cb34539f875781fe7f2dea4b937ace5 (patch)
tree8fa4db23f72a58b049f53973f839a28793e2828e /cmd/mount_zfs
parentb1d13a60d12a7df0f2e1bed6405529790213a6cb (diff)
Handle concurrent snapshot automounts failing due to EBUSY.
In the current snapshot automount implementation, it is possible for multiple mounts to attempted concurrently. Only one of the mounts will succeed and the other will fail. The failed mounts will cause an EREMOTE to be propagated back to the application. This commit works around the problem by adding a new exit status, MOUNT_BUSY to the mount.zfs program which is used when the underlying mount(2) call returns EBUSY. The zfs code detects this condition and treats it as if the mount had succeeded. Signed-off-by: Brian Behlendorf <[email protected]> Closes #1819
Diffstat (limited to 'cmd/mount_zfs')
-rw-r--r--cmd/mount_zfs/mount_zfs.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/cmd/mount_zfs/mount_zfs.c b/cmd/mount_zfs/mount_zfs.c
index 4db33ed69..83b57f4e9 100644
--- a/cmd/mount_zfs/mount_zfs.c
+++ b/cmd/mount_zfs/mount_zfs.c
@@ -528,7 +528,7 @@ main(int argc, char **argv)
case EBUSY:
(void) fprintf(stderr, gettext("filesystem "
"'%s' is already mounted\n"), dataset);
- return (MOUNT_SYSERR);
+ return (MOUNT_BUSY);
default:
(void) fprintf(stderr, gettext("filesystem "
"'%s' can not be mounted due to error "