Hi all,

It's been a long time since I last posted with any troubles :-)

I recently upgraded from Samba 3.0.24 to 3.0.26a. 3.0.24 has been 
working for about a year just fine now (after patches for a couple of 
NetBSD memory leaks affecting Samba). Immediately after the upgrade, 
however, things seem to have gone down hill a bit.

First off I had some sort of weird DFS error, which I eventually found a 
solution to. All was needed is adding 'msdfs root = no' to smb.conf, 
restarting Samba and, the most important part, restarting all client 
machines to recognize the change.

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


I was basically just wondering if I am the only one seeing this? As I 
said, previously all was fine. I have also looked in 
/var/log/cores/smbd/ to try and find a core dump, but the directory is 
empty :-(

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