Nicholas Lee via smartos-discuss wrote:
When using zonecfg add fs, what is the functional difference between
type=lofs and type=zfs?
I know that lofs mounts a directory from the GZ in one or more NGZs.
It was suggested [1] that this is actually the recommended method
over using NFS. NFS server and NFS client with the same kernel can
lead to kernel deadlocks - not sure if this is still an issue.
It is still preferred, that's how sparse zones (no longer supported in
Solaris but used for SmartOS zones) map shared filesystems.
The only detail I can find specifically about type=zfs is that: "You
can add a ZFS file system as a generic file system when the goal is
*solely to share space* with the global zone."
Can you also mount the type=zfs filesystem in the GZ? Or other NGZs?
If amount is specified as type=zfs, the zone "owns" the filesystem,
which has its "zoned" property set.
Is there a specific reason with smartos to use either option?
If you want a zfs dataset (such as a SmartOS delegated dataset) that can
be managed by a zone, use type=zfs. If you want to share directories
from the GZ, use type=lofs.
vmadm only allows a delegated dataset to be added at creation time.
--
Ian.
-------------------------------------------
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
