Hello, at our company we are using Samba 4.3.2 in conjunction with Windows 7. We use the Windows 7 machines for our nightly compiles. However, occasionally the schedules compiles stop with a Windows network error message, such as: . . . [ 16%] Generating ui/moc_versiondialog.cxx [ 16%] NMAKE : fatal error U1077: 'R:\usr\20091022\121890\release\win\bin\cmake.exe' : return code '0xc00000c3' Stop. This error code (STATUS_INVALID_NETWORK_RESPONSE) tells me that something appears to be wrong with the communication of the Windows 7 machine from/to the Samba server. Interestingly, this error only occurs if multiple compile jobs are being executed on a single machine. If only one compile job is allowed, everything works just fine. However, using Quad-Cores for a single compile job is not what we really want. Our compile jobs have the following structure: 1. Mount the samba share via net use <drive>: \\server\share 2. Execute compile 3. Unmount the sma share via net use <drive>: /DELETE (Note that removing 3. does not resolve this issue). Before migrating to Windows 7 we have been using Windows XP in our compile farm, not having these problems. Unfortunately, the migration to Win 7 was necessary to have 64bit compiles. Does anyone know what to do here? How to find the real issue for this problem? Many thanks in advance. Kind regards, Gernot Gebhard -- Dipl.-Inform. Gernot Gebhard AbsInt Angewandte Informatik GmbH Science Park 1 66123 Saarbr?cken GERMANY Mail: gernot.gebhard at absint.com Tel: +49-681-3836036 Fax: +49-681-3836020 WWW: http://absint.com -- Gesch?ftsf?hrung: Dr.-Ing. Christian Ferdinand Eingetragen im Handelsregister des Amtsgerichts Saarbr?cken, HRB 11234
On Thu, Oct 22, 2009 at 01:28:29PM +0200, Gernot Gebhard wrote:> at our company we are using Samba 4.3.2 in conjunction with Windows 7. > We use the Windows 7 machines for our nightly compiles. However, > occasionally the schedules compiles stop with a Windows network error > message, such as: > > . > . > . > [ 16%] Generating ui/moc_versiondialog.cxx > [ 16%] NMAKE : fatal error U1077: > 'R:\usr\20091022\121890\release\win\bin\cmake.exe' : return code > '0xc00000c3' > Stop.Can you do a network trace of such a failure? Information on how to create useful network traces can be found under http://wiki.samba.org/index.php/Capture_Packets Thanks, Volker -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20091022/8c5e95d2/attachment.pgp>
morgan at tuxedo.darktech.org
2009-Oct-22 13:16 UTC
[Samba] Reliability issues when using Windows 7
> Apparently Windows is unhappy with one of our network packets. We > need to see the packet which Windows 7 does not like, and the > natural source for that information is a packet trace. Are you > aware that tshark is able to split packet traces in chunks while > taking them? So you could run it arbitrarily long without filling > your disk if you delete old ones?As a long-time Wireshark, n?e Ethereal, fan, that is exactly what I was going to suggest. :) and tshark makes going through huge packet traces very, very easy. For someone who knows what they're looking at and knows how to effectively use tshark's filters, the bad packet can be spotted in minutes even for very, very large traces. Also, you can filter your packet capture so you're just getting CIFS packets and not everything else. Message sent via Atmail Open - http://atmail.org/