> On 5 Dec 2017, at 00:53, Brian Bennett <[email protected]> wrote: > > Chad, > > Welcome to SmartOS! > > First of all, I'd like to say that for the global zone especially, make sure > to use SmartOS documentation first, and foremost. If there's a SmartOS > specific command you should use it over anything else, if at all possible. > For example, don't use zoneadm or zonecfg when you can use vmadm. > > That being said, to add a shared filesystem to zones, add the following > property to your vm json before you create it. > > "filesystems": [ > { > "type": "lofs", > "source": "/zones/mailstore", > "target": "/local/mailstore" > } > ]
I found that I couldn’t serve SMB/CIFS shares from an lofs-mounted filesystem from a non-global zone (my “SMB zone”). My memory’s kind of vague at the moment, but you either couldn’t set the various share ZFS properties inside the zone, or smbd in the zone just refused to see the properties. I’m not sure what the best approach is in this case. There are only two options AFAICS: 1) run samba from pkgsrc instead of smbd 2) create the shared dataset in the SMB zone, and lofs it sideways into the other zones. Getting samba working “right” with ZFS and ACLs and Macs seems not well documented, so 1) is possible but undesirable. I also preferred the idea of using the kernel SMB/CIFS server. Unfortunately with 2) the source paths in the lofs mounts include the UUID of the SMB server zone (ie /zones/smb-zone-uuid/something), which is kind of tacky, and also means that if the SMB zone doesn’t start, nothing else using it can start as the path doesn’t exist. Any sort of best practices here would be appreciated. Chris ------------------------------------------- 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
