Hello, I am getting a lot of these errors when backing up to an external SCSI tape drive. This server was running well with RH 7.3 without any errors. Recently upgraded to Suse 9.3 and now the server is getting all of these errors. What could be happening? Also noticing "tons" of smbd errors. <dmesg output with st0 errors> st0: Error on write filemark. smb_add_request: request [c0b7eee0, mid=490] timed out! SMB connection re-established (-5) smb_add_request: request [c0b1a0a0, mid=56632] timed out! st0: Error with sense data: <6>st0: <<DEFERRED>>: sense key: Medium Error <<vendor>> ASC=0x80 ASCQ=0x1ASC=0x80 ASCQ=0x1 Info fld=0x0 st0: Error with sense data: <6>st0: <<DEFERRED>>: sense key: Aborted Command ASC=0x44 <<vendor>> ASCQ=0x89 Info fld=0x0 st0: Error on write filemark. st0: Failed to read 131072 byte block with 65536 byte transfer. st0: Failed to read 131072 byte block with 65536 byte transfer. st0: Error with sense data: <6>st0: <<DEFERRED>>: sense key: Medium Error <<vendor>> ASC=0x80 ASCQ=0x1ASC=0x80 ASCQ=0x1 Info fld=0x0 st0: Error with sense data: <6>st0: <<DEFERRED>>: sense key: Aborted Command ASC=0x44 <<vendor>> ASCQ=0x89 Info fld=0x0 st0: Error on write filemark. Oct 15 09:50:01 samba smbd[18114]: write_socket: Error writing 4 bytes to socket 5: ERRNO = Connection reset by peer Oct 15 09:50:01 samba smbd[18114]: [2005/10/15 09:50:01, 0] lib/util_sock.c:send_smb(647) Oct 15 09:50:01 samba smbd[18114]: Error writing 4 bytes to client. -1. (Connection reset by peer) Oct 15 10:50:01 samba syslog-ng[3162]: STATS: dropped 0 Oct 15 11:26:32 samba smbd[18287]: [2005/10/15 11:26:32, 0] lib/util_sock.c:get_peer_addr(1150) Oct 15 11:26:32 samba smbd[18287]: getpeername failed. Error was Transport endpoint is not connected Oct 15 11:26:32 samba smbd[18287]: [2005/10/15 11:26:32, 0] lib/util_sock.c:write_socket_data(430) Oct 15 11:26:32 samba smbd[18287]: write_socket_data: write failure. Error = Connection reset by peer Oct 15 11:26:32 samba smbd[18287]: [2005/10/15 11:26:32, 0] lib/util_sock.c:write_socket(455) Oct 15 11:26:32 samba smbd[18287]: write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer Oct 15 11:26:32 samba smbd[18287]: [2005/10/15 11:26:32, 0] lib/util_sock.c:send_smb(647) Oct 15 11:26:32 samba smbd[18287]: Error writing 4 bytes to client. -1. (Connection reset by peer) Oct 15 11:42:34 samba swat[18391]: [2005/10/15 11:42:28, 0] printing/print_cups.c:cups_cache_reload(122) Oct 15 11:42:37 samba swat[18391]: Unable to get printer list - client-error-bad-request Oct 15 11:44:17 samba swat[18409]: [2005/10/15 11:44:17, 0] lib/util_sock.c:get_peer_addr(1150) Oct 15 11:44:17 samba swat[18409]: getpeername failed. Error was Socket operation on non-socket Oct 15 11:44:17 samba swat[18409]: [2005/10/15 11:44:17, 0] lib/util_sock.c:get_peer_addr(1150) Oct 15 11:44:17 samba swat[18409]: getpeername failed. Error was Socket operation on non-socket Thank you, James
On 10/15/05, James D. Parra
Hello,
I am getting a lot of these errors when backing up to an external SCSI tape drive. This server was running well with RH 7.3 without any errors. Recently upgraded to Suse 9.3 and now the server is getting all of these errors. What could be happening? Also noticing "tons" of smbd errors.
James, A sense key medium error usually indicates a problem with the medium. Try running 'mt -f /dev/nst0 setblk 0' and see what happens. You can also try to change the medium (had a similar error and it helped). The Samba issue: Try setting the following options in your samba config: // less effective but quite safe use sendfile = no large readwrite = no max xmit = 8192 A 'connection reset by peer' is sometimes caused by windows clients that access both samba ports and then reset one is closed (RST) as soon as possible if one of them is working. Is the samba server performing well? Are there any anomalies while clients are served? Don't know where to begin. \Steve
participants (2)
-
James D. Parra
-
Steve Graegert