Enabling ZFS SMB Shares May Fail With "error modifying '<share>': share name exists"
(Doc ID 2205564.1)
Last updated on FEBRUARY 05, 2019
Applies to:Solaris Operating System - Version 10 3/05 to 11.3 [Release 10.0 to 11.0]
Information in this document applies to any platform.
Create a clone of a smb shared filesystem/dataset and have it shared as clone_datasetname without disturbing the original online shared filesystem/dataset.
Should the issue described in this document be encountered, when SMB Shares on ZFS Datasets are enabled, the following error will be seen on the terminal
This issue is being addressed via 'Bug 19607345 - libshare2 can't transmogrify duplicate share names from v5 clones'
One or more of the following situations may lead to this situation
- Update Solaris by applying a later SRU
- Upgrading ZFS using the 'zfs upgrade' command
- Upgrading the ZFS Pool Version using the 'zpool upgrade' command. Specifically upgrading from v32 to v33 or later. v33 delivered 'Improved share support'. See 'ZFS Filesystem and Zpool Version Matrix (Doc ID 1359758.1)'
- Cloning a ZFS Dataset
- Receiving a ZFS snapshot to a zpool that includes SMB shares
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document