On Tue, eric kustarz wrote: > > >>>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? > > > > > > > > I imagine its something like a simple 'ls' that's showing the directory > is empty... if so, running a snoop while that 'ls' returns the wrong > data would be the first place to start. > > Then we can determine which NFS op (probably readdir) and whether the > server or client is to blame - in which case then we know what to dtrace.
It is possible that the autofs trigger node did not mount the filesystem because of some other error up the stack. As Eric asked, knowing the build level would be good given the recent changes in the autofs world. Spencer
