Package: uucp
Version: 1.07-17

Hi,
when having i/o errors on the filesystem uucp will get stuck on the
file getting the error. It will drop the connection and retry calling
to transfer the file instead of continuing other files. First guess on
how to actually work around this is to dequeue the file on i/o error as
it will definitly not make sense to retry.

uucico destination.rfc822.org - (2006-04-18 10:50:02.94 1979) Calling system 
destination.rfc822.org (port TCP)
uucico destination.rfc822.org - (2006-04-18 10:50:03.47 1979) Login successful
uucico destination.rfc822.org - (2006-04-18 10:50:03.76 1979) Handshake 
successful (protocol 'i' sending packet/window 1400/9 receiving 1400/9)
uucico destination.rfc822.org flo (2006-04-18 10:50:03.76 1979) Sending 
/opt/home/flo/queued/file1 (731944960 bytes)
uucico destination.rfc822.org flo (2006-04-18 10:50:26.70 1979) ERROR: read: 
Input/output error
uucico destination.rfc822.org - (2006-04-18 10:50:26.71 1979) Protocol 'i' 
packets: sent 13, resent 0, received 8
uucico destination.rfc822.org - (2006-04-18 10:50:26.84 1979) Call complete (23 
seconds 8400 bytes 365 bps)
uucico destination.rfc822.org - (2006-04-18 11:00:02.51 2034) Retry time not 
reached
uucico destination.rfc822.org - (2006-04-18 11:10:01.34 2108) Calling system 
destination.rfc822.org (port TCP)
uucico destination.rfc822.org - (2006-04-18 11:10:01.98 2108) Login successful
uucico destination.rfc822.org - (2006-04-18 11:10:02.21 2108) Handshake 
successful (protocol 'i' sending packet/window 1400/9 receiving 1400/9)
uucico destination.rfc822.org flo (2006-04-18 11:10:02.21 2108) Sending 
/opt/home/flo/queued/file1 (731944960 bytes)
uucico destination.rfc822.org flo (2006-04-18 11:10:48.57 2108) ERROR: read: 
Input/output error
uucico destination.rfc822.org - (2006-04-18 11:10:48.57 2108) Protocol 'i' 
packets: sent 13, resent 0, received 8
uucico destination.rfc822.org - (2006-04-18 11:10:48.69 2108) Call complete (47 
seconds 8400 bytes 178 bps)
uucico destination.rfc822.org - (2006-04-18 11:20:02.48 2170) Retry time not 
reached

The cause for the i/o error was an IDE disk failure:

Apr 18 11:10:49 host kernel: ide0: reset: success
Apr 18 11:10:49 host kernel: hda: task_in_intr: status=0x59 { DriveReady 
SeekComplete DataRequest Error } 
Apr 18 11:10:49 host kernel: hda: task_in_intr: error=0x01 { AddrMarkNotFound 
}, LBAsect=146014750, sector=146014750
Apr 18 11:10:49 host kernel: ide: failed opcode was: unknown
Apr 18 11:10:49 host kernel: end_request: I/O error, dev hda, sector 146014750

Flo
-- 
Florian Lohoff                  [EMAIL PROTECTED]             +49-171-2280134
                        Heisenberg may have been here.

Attachment: signature.asc
Description: Digital signature

Reply via email to