Mark Cullen wrote:
> 
> Now I am noticing that every so often, for no apparent reason, smbd is 
> panicing and dieing on me. The client machine pops up with a "Delayed 
> write failed" error when this happens, which is how I know it's 
> happened! The log shows the following:
> 
> [2007/11/13 19:17:31, 0] lib/fault.c:fault_report(41)
>   ===============================================================
> [2007/11/13 19:17:31, 0] lib/fault.c:fault_report(42)
>   INTERNAL ERROR: Signal 6 in pid 16705 (3.0.26a)
>   Please read the Trouble-Shooting section of the Samba3-HOWTO
> [2007/11/13 19:17:31, 0] lib/fault.c:fault_report(44)
> 
>   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
> [2007/11/13 19:17:31, 0] lib/fault.c:fault_report(45)
>   ===============================================================
> [2007/11/13 19:17:31, 0] lib/util.c:smb_panic(1632)
>   PANIC (pid 16705): internal error
> [2007/11/13 19:17:31, 0] lib/util.c:log_stack_trace(1786)
>   unable to produce a stack trace on this platform
> [2007/11/13 19:17:31, 0] lib/fault.c:dump_core(181)
>   dumping core in /var/log/cores/smbd
> 
> 

Since I wrote this, I checked the heatsink and it was rather dusty. I 
cleaned it up and since then I haven't seen this error since.

I guess it was just a heat issue, even though the temp sensor said it 
was only about 45C-50C under load on an old pre P4 Celeron. Weird. 
Probably an insanely inaccurate sensor.

Seems to be OK now :-)

-- 
Mark Cullen <mark.r.cullen@gmail.com>
BSc (Hons), Computer Science