On January 30, 2007 9:59:45 AM -0800 Neal Pollack <[EMAIL PROTECTED]>
wrote:
I've got my first server deployment with ZFS.
Consolidating a pair of other file servers that used to have
a dozen or so NFS exports in /etc/dfs/dfstab similar to;
/export/solaris/images
/export/tools
/export/ws
..... and so on....
For the new server, I have one large zfs pool;
-bash-3.00# df -hl
bigpool 16T 1.5T 15T 10% /export
that I am starting to populate. Should I simply share /export,
or should I separately share the individual dirs in /export
like the old dfstab did?
Just share /export.
I am assuming that one single command;
# zfs set sharenfs=ro bigpool
would share /export as a read-only NFS point?
Opinions/comments/tutoring?
Unless you have different share option requirements for different
dirs (say rw vs ro or different network access rules), just sharing
the top level is probably better (easier to manage). Clients can
still mount subdirs and not the entire pool.
Now, if you create each dir under /export as a zfs filesystem, the
clients will HAVE to mount the individual filesystems. If they just
mount /export they will not traverse the fs mount on the server when
they descend /export. (today)
-frank
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
