On Thu, May 20, 2010 at 9:30 PM, Whit Blauvelt whit@transpect.com wrote:
On Thu, May 20, 2010 at 06:17:10PM -0700, Benjamin Franz wrote:
Have you looked in /var/log/messages for errors from smbd? I don't remember seeing that anywhere in your T/S list.
Yup. I've grepped all the logs. Nothing from smbd at all. I also enabled kern and daemon logs, just in case those would catch something messages wasn't. What they've caught isn't anything from smbd.
I'm leaning towards it being, as suggested by someone, somehow symptom of a hardware problem, since it seems we've run through everything else remotely possible. I should have memtest86 results from a colleague soon. That it's been such an isolated problem, so consistent in its behavior, has made me think it must be something in the OS configuration. But that hypothesis is about played out.
My gut tells me it's not hardware but willing to take it :)
Have you tried adding a "set -x" to the top of the the smb startup scripts? I didn't see any such output in your replies so far.