Hi, I have a pool /zfs01 with two sub file systems /zfs01/rep1 and /zfs01/rep2. I used [i]zfs share[/i] to make all of these mountable over NFS, but clients have to mount either rep1 or rep2 individually. If I try to mount /zfs01 it shows directories for rep1 and rep2, but none of their contents. On a linux machine I think I''d have to set the [i]no_sub_tree_check[/i] flag in /etc/exports to let an NFS mount move through the different exports, but I''m just beginning with solaris, so I''m not sure what to do here. I found this post in the forum: http://opensolaris.org/jive/thread.jspa?messageID=169354𩖊 but that makes it sound like this issue was resolved by changing the NFS client behavior in solaris. Since my NFS client machines are going to be linux machines that doesn''t help me any. thanks for any suggestions! This message posted from opensolaris.org
On Tue, 29 Apr 2008, Tim Wood wrote:> but that makes it sound like this issue was resolved by changing the > NFS client behavior in solaris. Since my NFS client machines are > going to be linux machines that doesn''t help me any.Yes, Solaris 10 does nice helpful things that other OSs don''t do. I use per-user ZFS filesystems so I encountered the same problem. It is necessary to force the automounter to request the full mount path. On Solaris and OS-X Leopard client systems I use an /etc/auto_home like # Home directory map for automounter # * freddy:/home/& which also works for Solaris 9 without depending on the Solaris 10 "feature". For FreeBSD (which uses the am-utils automounter) I figured out this horrific looking map incantation: * type:=nfs;rhost:=freddy;rfs:=/home/${key};fs:=${autodir}/${rhost}${rfs};opts:=rw,grpid,resvport,vers=3,proto=tcp,nosuid,nodev So for Linux, I think that you will also need to figure out an indirect-map incantation which works for its own broken automounter. Make sure that you read all available documentation for the Linux automounter so you know which parts don''t actually work. Bob =====================================Bob Friesenhahn bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Bob Friesenhahn wrote:> So for Linux, I think that you will also need to figure out an > indirect-map incantation which works for its own broken automounter. > Make sure that you read all available documentation for the Linux > automounter so you know which parts don''t actually work. > >Oh contraire Bob. I''m not going to boost Linux, but in this department, they''ve tried to do it right. If you use Linux autofs V4 or higher, you can use Sun style maps (except there''s no direct maps in V4. Need V5 for direct maps). For our home directories, which use an indirect map, we just use the Solaris map, thus: auto_home: * zfs-server:/home/& Sorry to be so off (ZFS) topic. Jon -- - _____/ _____/ / - Jonathan Loran - - - / / / IT Manager - - _____ / _____ / / Space Sciences Laboratory, UC Berkeley - / / / (510) 643-5146 jloran at ssl.berkeley.edu - ______/ ______/ ______/ AST:7731^29u18e3
On Apr 29, 2008, at 9:35 PM, Tim Wood wrote:> Hi, > I have a pool /zfs01 with two sub file systems /zfs01/rep1 and / > zfs01/rep2. I used [i]zfs share[/i] to make all of these mountable > over NFS, but clients have to mount either rep1 or rep2 > individually. If I try to mount /zfs01 it shows directories for > rep1 and rep2, but none of their contents. > > On a linux machine I think I''d have to set the [i]no_sub_tree_check > [/i] flag in /etc/exports to let an NFS mount move through the > different exports, but I''m just beginning with solaris, so I''m not > sure what to do here. > > I found this post in the forum: http://opensolaris.org/jive/ > thread.jspa?messageID=169354𩖊 > > but that makes it sound like this issue was resolved by changing > the NFS client behavior in solaris. Since my NFS client machines > are going to be linux machines that doesn''t help me any.My understanding is that the linux client has the same capabilities of the Solaris client in that it can traverse server side mount points dynamically. Spencer
On Tue, 29 Apr 2008, Jonathan Loran wrote:>> > Oh contraire Bob. I''m not going to boost Linux, but in this department, > they''ve tried to do it right. If you use Linux autofs V4 or higher, you > can use Sun style maps (except there''s no direct maps in V4. Need V5 > for direct maps). For our home directories, which use an indirect map, > we just use the Solaris map, thus: > > auto_home: > * zfs-server:/home/& > > Sorry to be so off (ZFS) topic.I am glad to hear that the Linux automounter has moved forward since my experience with it a couple of years ago and indirect maps were documented but also documented not to actually work. :-) I don''t think that this discussion is off-topic. Filesystems are so easy to create with ZFS that it has become popular to create per-user filesystems. It would be useful if the various automounter incantations to make everything work would appear in a ZFS-related Wiki somewhere. This can be an embarrassing situtation for the system administrator who thinks that everything is working fine due to testing with Solaris 10 clients. So he swiches all the home directories to ZFS per-user filesystems overnight. Imagine the frustration and embarrassment when that poor system administrator returns the next day and finds that many users can not access their home directories! Bob =====================================Bob Friesenhahn bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/