Yes, version 3.0.28-apple which ships with 10.6.8.
Apple so far has been useless in trying to solve this. I have Redhat
machines with later versions and have not had the problem reported.
Best I can tell it has to do with our software accessing the registry
repeatedly and finally SMBD falls over. This only with a Windows 7 box
as I can run XP all day without issue doing the same access to the
registry. I'm almost sure it accessing the registry going by what I
see in packet traces.
(DCERPC Bind ...... is the packet that shows a fault and the daemon
terminates and another SMBD picks the session up like nothing happened.)
Pat.
On Apr 28, 2012, at 4:37 PM, Jeremy Allison wrote:
On Sun, Apr 22, 2012 at 02:29:29PM -0400, Patrick Flaherty wrote:
Our software utilizes an OS X Server (Snow Leopard 10.6.8) for file
read and writes. We gather files out of many directories, process
them, and then write files back to the server.
We had a long time end user who utilizes our software with an XP box
upgrade from XP to Windows 7.
Now with Windows 7 the SMBD is crashing routinely under heavy loads.
Whatever information it was working on at the time is corrupted.
EVEN WORSE the SMBD respawns silently under a new process and
reconnects, so we don't know that the smb server crashed or that the
data has become corrupt.
The problem is intermitant, but frequent. I'll throw 16 duplicates
of the same file at the system and it will fail on, say, files 11
and 16. This is the same file under a different name.
Here's a sample crash log (they're all about the same.)
Is this the 3.0.x-based smbd that Apple ships ? Or a more
modern smbd running somewhere else ?
Jeremy.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
