On Tue, Aug 26, 2003 at 07:13:00PM -0500, Lindsay Haisley
wrote:> Can someone please explain these smb.log entries???
>
> [2003/08/26 18:58:31, 0] smbd/service.c:make_connection(381)
> fmouse logged in as admin user (root privileges)
> [2003/08/26 18:58:35, 0] lib/util_sock.c:read_socket_with_timeout(298)
> read_socket_with_timeout: timeout read. read error = Connection reset by
peer.
> [2003/08/26 18:58:35, 0] smbd/oplock.c:oplock_break(758)
> oplock_break: receive_smb error (Connection reset by peer)
> oplock_break failed for file home/orthey/www_site/ml-mini.html (dev =
902, inode = 1097864, file_id = 17).
> [2003/08/26 18:58:35, 0] smbd/oplock.c:oplock_break(843)
> oplock_break: client failure in break - shutting down this smbd.
> [2003/08/26 18:59:07, 0] smbd/oplock.c:request_oplock_break(981)
> request_oplock_break: no response received to oplock break request to pid
17739 on port 41357 for dev = 902, inode = 1097864,
> file_id = 17
> [2003/08/26 18:59:52, 0] lib/util_sock.c:read_data(436)
> read_data: read failure for 9370. Error = Connection reset by peer
>
> What is "oplock_break"? Why might it be failing?
>
> This is a critical issue regarding my business and the way that I work with
> client website files. File saves via samba to my webserver are getting
> corrupted, resulting in serious data loss, and my wife's business has
lost
> the capacity to do backups and access of critical data via a file share,
> lest it also be corrupted.
>
> I thought it was a samba 3 issue, but back-versioned to v2.2.3a and have
the
> same problem. Something else is causing the problem, probably as a result
> of a change which was part of a general update on the server, which is
> tracking Debian testing. The Win box running the software having problems
> is running Windows 95. Nothing has changed there. The file save process
> which used to work properly is now hanging and returning an error box with
> "Stream I/O error" and a later notation that "some other
process" had
> modified the file. The Linux kernel is at 2.4.20 (hasn't changed in
several
> months).
>
> Please reply to fmouse-x98nof@fmp.com if you have any insight into this. I
> don't have time to research the tech detials of file locking and such,
but
> any pointers, suggestions or references anyone might be able to send will
be
> deeply appreciated.
You have bad networking hardware, probably a switch or hub, or
bad ethernet card.
Jeremy.