Really Funky Samba Errors (smbd/nttrans.c:call_nt_transact_ioctl)
William R. Lorenz
wrl at express.org
Wed Jun 2 19:54:49 GMT 2004
Hi All,
I'm experiencing some really funky Samba errors, and I'm hoping that some
of you might have some ideas. This only happens sporadically, and when it
does, I loose Samba connectivity for a while. Here are my Samba logs:
Jun 2 13:29:01 nasone smbd[20289]: [2004/06/02 13:29:01, 0]
smbd/nttrans.c:call_nt_transact_ioctl(2076)
Jun 2 13:29:01 nasone smbd[20289]: call_nt_transact_ioctl(0x9009c):
Currently not implemented.
Jun 2 13:45:22 nasone smbd[20289]: [2004/06/02 13:45:22, 0]
lib/util_sock.c:read_socket_with_timeout(304)
Jun 2 13:45:22 nasone smbd[20289]: read_socket_with_timeout: timeout
read. read error = Connection reset by peer.
Jun 2 13:45:22 nasone smbd[20289]: [2004/06/02 13:45:22, 0]
smbd/oplock.c:oplock_break(801)
Jun 2 13:45:22 nasone smbd[20289]: oplock_break: receive_smb error
(Connection reset by peer)
Jun 2 13:45:22 nasone smbd[20289]: oplock_break failed for file
GENSRVNT/Bin/Mercury.exe (dev = fd03, inode = 786527, file_id = 475).
Jun 2 13:45:22 nasone smbd[20289]: [2004/06/02 13:45:22, 0]
smbd/oplock.c:oplock_break(891)
I did some poking around in the code, but I don't know enough about the
underlying NT IOCTL functionality to really make heads or tails of it.
The machine hitting the Samba server is a Windows 2000 Server box with
Service Pack 4 installed. I would assume this should be well and
supported in all of its funky NT IOCTL calls. Does anyone have ideas?
-- _
__ __ ___ _| | William R. Lorenz <wrl at express.org>
\ V V / '_| | http://www.clevelandlug.net/ ; "Every revolution was
\./\./|_| |_| first a thought in one man's mind." - Ralph Waldo Emerson
More information about the samba-technical
mailing list