Robert Petkus wrote:
When using sharenfs, do I really need to NFS export the parent zfs filesystem *and* all of its children? For example, if I have /zfshome /zfshome/user1 /zfshome/user1+n it seems to me like I need to mount each of these exported filesystems individually on the NFS client. This scheme doesn't seem optimal. If I have tens of thousands of users, each with their own little ZFS filesystem (necessary because ZFS doesn't do user-based quotas), I don't want to NFS mount all of these filesystems on a single node.
Most people use an automounter to mount NFS filesystems on demand to solve an issue like this. Getting changes to maps distributed does get more painful with a lot more distinct filesystems, but being able to mount only what you need can be quite a good thing. An alternate way will be to use NFSv4. When an NFSv4 client crosses a mountpoint on the server, it can detect this and mount the filesystem. It can feel like a "lite" version of the automounter in practice, as you just have to mount the root and discover the filesystems as needed. The Solaris NFSv4 client can't do this yet. Rob T _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
