arb wrote: > I've got nested ZFS filesystems exported via NFS. > > They are mounted on the clients using automount (from a NIS map). > > But: only the root exported filesystem shows any contents on the clients. > Any sub-directories it has are fine, but any sub-filesystems are empty. > > ie. NIS map auto.stuff contains "stuff server:/stuff/images" > server% zfs get sharenfs > stuff/images sharenfs rw=netgroup > stuff/images/small sharenfs inherited from stuff/images > stuff/images/large sharenfs rw=netgroup > > client% ls /data/stuff/images > large/ small/ other files... > > But /data/stuff/images/large is empty, as is small/ > > If I move the files out of the ZFS sub-filesystems into plain directories > then it is fine. > > And on the client /net/server/stuff/images/large works just fine too. > > I'm not sure if this is a NFS automount problem or a Nested-ZFS problem!
Currently, for the automounter to help you with any version of NFS, you would need to list all of the separate filesystems in your automounter maps. However your map let you mount /data/stuff/images, you'd also need to add an entry to mount /data/stuff/images/small and /data/stuff/images/large. This is because the filesystems are separate. With NFSv4 only, this should not be necessary; the client should be able to discover and mount the subsidiary filesystems. As Tom said, we're working on that with the "mirror mounts" work, coming soon. Rob T
