Dear all, A while ago I posted a message regading the way Samba is behaving and some problems that I was facing with Windows "loosing" the connection with the server... Here is another sample of what my /var/log/messages still looks like: Sep 19 15:08:01 Srv smbd-classic[3499]: [2004/09/19 15:08:01, 0] lib/util_sock.c:read_data(436) Sep 19 15:08:01 Srv smbd-classic[3499]: read_data: read failure for 4. Error = Connection reset by peer Whenever Windows Clients report a "Network or Hard Disk failure" I get this message in the logs and the only thing that I can do is reboot the Windows client. This is a very big problem for me as the Windows machine that matters the most plays MP3's from the server on a 24 hour basis and its interuption means big problem from my boss.... I have tried everything. From reinstalling my Linux box from scratch, reinstalling Windows2000 from scratch (SP2) changing network cards, checking the wiring of my network, checking intensity of the network cables (yes even brought a technician to assist me with that because I had no idea how to check that), connected Srv with Win2000 via a cross-over cable (just in case the switcher was malfunctioning) and tons of other scenarios. Nothing! Zilch! Unfortunately I am faced with a very serious problem since this occurs every week (sometimes more than 3 times a day!!!). Looked in google for this. Another person who had the same problem had a solution published with op_locks etc, tried that...nothing! Can someone give me a good idea?? Thank you tons! Chris PS: Samba is running on SuSE Linux 9.1 Samba 3.0.2a-51
Johannes-Ulrich Menzebach
2004-Sep-24 07:38 UTC
[BULK] - [Samba] Arrggg Samba is not behaving
Chris, I suppose what you are experiencing is a timeout problem. We had that with a loaded samba server and a bunch of w2k clients hitting the server at the same time. CPU load spiked and single smbds stuck in a request for (not sure if I remember the value correctly) some minutes. These smbds where in D state, presumeably in a system call to disk related stuff. During that time interactive behaviour while logged on to the server was very sluggish also esp when touching something disk related. In the end upgradig to a faster machine (SMP) and better disks helped. We get that error extremely seldom now. Also I could imagine that trying the 2.6 kernel might help. Actually anything that keeps processes doing disk I/O from those long times in D state. Linux kernel mailing list ? Uli On Freitag, 24. September 2004 09:23 Chris Roubekas wrote: >Dear all, > > A while ago I posted a message regading the way Samba is behaving >and some problems that I was facing with Windows "loosing" >the connection with the server... >Here is another sample of what my /var/log/messages still looks like: > >Sep 19 15:08:01 Srv smbd-classic[3499]: [2004/09/19 15:08:01, 0] lib/util_sock.c:read_data(436) >Sep 19 15:08:01 Srv smbd-classic[3499]: read_data: read failure for 4. Error = Connection reset by peer > >Whenever Windows Clients report a "Network or Hard Disk failure" I get this >message in the logs and the only thing that I can do is reboot the Windows >client. This is a very big problem for me as the Windows machine that matters >the most plays MP3's from the server on a 24 hour basis and its interuption >means big problem from my boss.... > >I have tried everything. From reinstalling my Linux box from scratch, reinstalling >Windows2000 from scratch (SP2) changing network cards, checking the wiring of >my network, checking intensity of the network cables (yes even brought a technician >to assist me with that because I had no idea how to check that), connected >Srv with Win2000 via a cross-over cable (just in case the switcher was malfunctioning) >and tons of other scenarios. Nothing! Zilch! > >Unfortunately I am faced with a very serious problem since this occurs >every week (sometimes more than 3 times a day!!!). > >Looked in google for this. Another person who had the same problem >had a solution published with op_locks etc, tried that...nothing! > >Can someone give me a good idea?? > >Thank you tons! >Chris > >PS: Samba is running on SuSE Linux 9.1 Samba 3.0.2a-51 -- +----------------------------------------------------------------------+ | Dr. Johannes-Ulrich Menzebach menze@vitesse.com | | Vitesse Semiconductor GmbH & Co KG | | D-47057 Duisburg Pappenstr. 36 Tel. +49/203/306-1765 | | D-44149 Dortmund Borussiastr. 112 Tel. +49/231/6560-186 | | Key fingerprint = A36C 9660 6A1C 91E6 051E DF1A 573A 770B DD66 9D9F | +----------------------------------------------------------------------+
On Fri, Sep 24, 2004 at 10:23:11AM +0300, Chris Roubekas wrote:> > A while ago I posted a message regading the way Samba is behaving > and some problems that I was facing with Windows "loosing" > the connection with the server... > Here is another sample of what my /var/log/messages still looks like: > > Sep 19 15:08:01 Srv smbd-classic[3499]: [2004/09/19 15:08:01, 0] lib/util_sock.c:read_data(436) > Sep 19 15:08:01 Srv smbd-classic[3499]: read_data: read failure for 4. Error = Connection reset by peerThis is simply the client disconecting from the server. We have no idea who.> I have tried everything. From reinstalling my Linux box from scratch, reinstalling > Windows2000 from scratch (SP2) changing network cards, checking the wiring of > my network, checking intensity of the network cables (yes even brought a technician > to assist me with that because I had no idea how to check that), connected > Srv with Win2000 via a cross-over cable (just in case the switcher was malfunctioning) > and tons of other scenarios. Nothing! Zilch! > > Unfortunately I am faced with a very serious problem since this occurs > every week (sometimes more than 3 times a day!!!).You need to run a sniffer on the wire to see what is happening to the tcp connection. The client is dropping it. Samba doesn't know why. I'd look at your hubs/switches if I were you. Jeremy.
I have exactly the same problem. And tried more or less the same solutions I tried passing the shared folders through nfs on anonther samba server to the windows clients also. I reckon it is a faulty hard disk problem, but the fsck reports nothing. I tried reiser and e3, but the problem persists. Indeed, it does not happen on a regular basis, only about once every three/four days and than sometimes 3 times a day. So maybe it is a time-out problem? How could I fix that? I have two servers one Samba PDC and one NFS fileserver. PDC gets files from NFSserver through imported nfs Windows machines get to the files on NFSserv through Samba on PDC Would it be better to install samba on NFS server as well, as a BDC? Maybe it would take the load of samba server? If someone knows a solution I'd very much like to hear it as well, thanks jeroen jeroen@jota.nl -----Original Message----- From: samba-bounces+jeroen=jota.nl@lists.samba.org [mailto:samba-bounces+jeroen=jota.nl@lists.samba.org]On Behalf Of Chris Roubekas Sent: vrijdag 24 september 2004 9:23 To: samba@lists.samba.org Subject: [Samba] Arrggg Samba is not behaving Dear all, A while ago I posted a message regading the way Samba is behaving and some problems that I was facing with Windows "loosing" the connection with the server... Here is another sample of what my /var/log/messages still looks like: Sep 19 15:08:01 Srv smbd-classic[3499]: [2004/09/19 15:08:01, 0] lib/util_sock.c:read_data(436) Sep 19 15:08:01 Srv smbd-classic[3499]: read_data: read failure for 4. Error = Connection reset by peer Whenever Windows Clients report a "Network or Hard Disk failure" I get this message in the logs and the only thing that I can do is reboot the Windows client. This is a very big problem for me as the Windows machine that matters the most plays MP3's from the server on a 24 hour basis and its interuption means big problem from my boss.... I have tried everything. From reinstalling my Linux box from scratch, reinstalling Windows2000 from scratch (SP2) changing network cards, checking the wiring of my network, checking intensity of the network cables (yes even brought a technician to assist me with that because I had no idea how to check that), connected Srv with Win2000 via a cross-over cable (just in case the switcher was malfunctioning) and tons of other scenarios. Nothing! Zilch! Unfortunately I am faced with a very serious problem since this occurs every week (sometimes more than 3 times a day!!!). Looked in google for this. Another person who had the same problem had a solution published with op_locks etc, tried that...nothing! Can someone give me a good idea?? Thank you tons! Chris PS: Samba is running on SuSE Linux 9.1 Samba 3.0.2a-51 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba