John reports:

"Short story, upping the 'status cache' setting from the default 1000 to
4000 fixed the problem on our test machine."

The directory contains 1777 files and MatLab appears to be performing
stat() requests on every file in the directory on a frequent basis.
The Status Cache which has a fixed size was thrashing. I should probably consider increasing the default in the next release to a higher
number.

Jeffrey Altman



Jeffrey Altman wrote:

Ok.  So the client has an additional bug.  At least the windows 1.3.73
client is no longer crashing your file server. ;)

the best would be for you to provide me remote access to the volume
so I can attempt to replicate the problem in a debugger.  The only
difference between the DEBUG and non-DEBUG builds are:

 * the DEBUG build is not optimized
 * the DEBUG build installs symbols by default

If you cannot provide remote access, you can increase the size of the
Trace Log buffers using the registry and use the "fs trace -dump"
command to dump the output after the problem starts to occur. This might or might not provide some clues.

The output of SysInternal's filemon.exe would also provide some insight
into what it is that MatLab is trying to do.

Jeffrey Altman


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to