[Sunhelp] Tracking down a bad application

[Nicholas Dronen]

On Mon, Oct 30, 2000 at 08:35:52AM -0500, Tim Longo wrote:
> 
> Greetings,
> 
> I support an environment where certain applications are automounted on a Sun
> server from a separate file server.  The application file system is mounted
> read-only.
> 
> It seems that a certain application is trying to write to the read only file
> system, and I get the following message in my syslog.  If anyone can offer
> suggestions on how I can figure out which files are being accessed, and in
> turn which application is misconfigured, I would be very grateful!
> 
> I have tried to truss several suspect applications, and use lsof, but have
> not been successful in figuring out which files the error messages are
> referencing.
> 
> Error in syslog:
> 
> Oct 20 11:18:55 boogie.research.bell-labs.com unix: NFS write error on host
> cannoli: Read-only file system.
> Oct 20 11:18:55 boogie.research.bell-labs.com unix: (file handle: 464f1500
> 2630a200 20000000 49e8a0 2730a200 f3360001 c0dc1700 1aa19e00)

You should be able to determine the inode number of the file
on the remote machine using the NFS file handle, which usually
contains the major and minor numbers of the device on which
the remove file resides and the indoe number.  Unfortunately
the exact format of the file handle is not specified in the NFS
V3 RFC and I haven't found any docs that cover how Solaris
constructs it's NFS file handles.

You might have better luck than I did on docs.sun.com.

Regards,

Nick Dronen