Up until last week, SAMBA was running fine, now when we attempt to map a
drive, the SAMBA call in JINETD gives us an error....

 Received call for: smbp tcp
  **** NATIVE STACK OVERFLOW ABORT: SMBD.SAMBA.SYS        PC=a.00aa0240
dbg_stac
k_overflow_trace+$2c
 NM* 0) SP=4188fff8 RP=a.0104bd20 trap_handler.handle_setdump+$a8
 NM  1) SP=4188ff78 RP=a.0104d260 trap_handler+$3fc
 NM  2) SP=4188fef8 RP=a.00e91138 FWRITE+$fe0
 NM  3) SP=4188f878 RP=a.00e90124 ?FWRITE+$8
          export stub: 211.0055bffc _px_write+$200
 NM  4) SP=4188f4f8 RP=211.0055bde8 ?_px_write+$8
          export stub: 1728.00070038 write+$20
 NM  5) SP=4188f438 RP=1728.00065564 _xflsbuf+$a4


After watching the process in Glance, and if I understand STACKS
correctly, it appears to be swaping out to disc space which we are very
low on (currently working on adding more). Is this the case? Is there a
way around this?

Thanks in advance.

Rick Clark
Senior Analyst
WW&R
Cleveland, Ohio