On Tue, Jul 11, 2006 at 10:36:40AM -0700, eric kustarz 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 this a newly created zfs filesystem after access via /net has already > been made? autofs isn't capable of recognizing new "triggers" (a newly > create filesystem) unless you manually unmount.
No, this is an old filesystem that worked a few hours ago and suddenly stopped. > >Is this a bug in Solaris? If not, is there some way to address the problem > >without rebooting? > > > >If there's any information I can provide that would help diagnose the > >problem, > >please let me know. > > snoop trace always helps, and any commands (if any) you ran on the server... I didn't run any commands on the server. What specific snoop invocation would you like to see and what operations should I perform while it's active? Is there a DTrace invocation which could give you some information? Adam -- Adam Leventhal, Solaris Kernel Development http://blogs.sun.com/ahl
