On Tue, Jul 11, 2006 at 10:21:11AM -0700, Adam Leventhal wrote:
> I'm exporting a ZFS filesystem via nfsv4. Occasionally and without any
> identifiable cause, that directory appears to be empty on a client machine
> mouting that file system through /net (autofs). When this happens, the client
> also can't create new files under that mount.
Is the directory a ZFS filesystem root? If yes...
Occasionally for the same client, or occasionally as you come across
clients?
If the latter, then if the /net/<host> mounts had been done before
cretion of the server-side filesystem in question, which means that the
client won't see the new filesystem until after the /net/<host> mounts
are auto-unmounted.
> Is this a bug in Solaris? If not, is there some way to address the problem
> without rebooting?
It's an irritating lack of a feature.
If using NFSv3 the missing feature is, I think, periodic probing of the
server's MOUNTs and updating of the client mounts accordingly. this
will never happen for v3.
If using NFSv4 the missing feature is client-side crossing of
server-side mount points ("mirror mounts"). Currently when using NFSv4
the -hosts automount map still uses the NFSv3 MOUNT protocol to figure
out what the server exports.
Nico
--
