This happened when I delegated a dataset to a zone and then decided to
rename the dataset, but zfs complained that the dataset was in-use by a
non-global zone, even though I had used the zonecfg command to remove the
dataset; and the zone was stopped.
I could set the zoned=off property manually, then rename the dataset
Then using zonecfg to delegate the dataset back to the zone does not set
the zoned property because the property had been previously set manually
```
[root@smartos ~]# zonecfg -z 8c8f62e3-ed42-6267-c3b5-fd4bed084cf6
zonecfg:8c8f62e3-ed42-6267-c3b5-fd4bed084cf6> info dataset
name: zones/d-smb
zonecfg:8c8f62e3-ed42-6267-c3b5-fd4bed084cf6> add dataset
zonecfg:8c8f62e3-ed42-6267-c3b5-fd4bed084cf6:dataset> set
name=dump/smbpublic
zonecfg:8c8f62e3-ed42-6267-c3b5-fd4bed084cf6:dataset> end
zonecfg:8c8f62e3-ed42-6267-c3b5-fd4bed084cf6> exit
[root@smartos ~]# zfs get all dump/smbpublic | grep zone
dump/smbpublic zoned off local
```
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
