Hi, Everything appears to be working fine apart from this one problem: When verifying dump and tar archives both tar and restore hang at random points (anywhere between 5min to 40min into the verify). Characteristic of this problem is that the hard disk can be heard seeking at regular (about 1sec) intervals, but I suspect this is the syslog filling rapidly with errors (see below). Operational Environment: ------------------------ Iomega Ditto 3200 parallel port tape unit Redhat Linux 5.2 (kernel 2.0.36) ftape-4.03-pre-2 (compiled from ftape-4_x-1998_12_20.tar.gz sources) dump-0.3-17 tar-1.12-4 Commands that cause the problem: -------------------------------- tar df /dev/nqft0 restore Cbf 10 /dev/nqft0 Syslog messages that are generated when the problem occurs: ----------------------------------------------------------- Here a a few of the messages occuring in the space of less than one second (they are generated endlessly until the process is killed). As you can see these errors accumulate very rapidly and I suspect the disk seeking I observe is simply the syslogd daemon writing the log file. Feb 4 22:58:13 quark kernel: [084] 0 fdc-io.c (fdc_reset) - no drive polling interrupt!. Feb 4 22:58:13 quark kernel: [085] 0 fdc-io.c (__fdc_command) - fdc not ready. Feb 4 22:58:13 quark kernel: [086] 0 fdc-io.c (__fdc_issue_command) - __fdc_command(fdc, out_data, out_count) failed: -16. Feb 4 22:58:13 quark kernel: [087] 0 fdc-io.c (fdc_seek) - fdc_issue_command(fdc, out, 3, ((void *) 0), 0) failed: -16. Feb 4 22:58:13 quark kernel: [088] 0 ftape-io.c (ftape_report_operation) - ftape_command(ftape, command) failed: -16. Feb 4 22:58:13 quark kernel: [089] 0 ftape-io.c (ftape_report_raw_drive_status) - report_operation failed after 4 trials. Feb 4 22:58:13 quark kernel: [090] 0 ftape-io.c (ft_check_cmd_restrictions) - ftape_report_raw_drive_status(ftape, &status) failed: -5. Feb 4 22:58:13 quark kernel: [091] 0 ftape-io.c (ftape_command) - ft_check_cmd_restrictions(ftape, command) failed: -5. Feb 4 22:58:13 quark kernel: [092] 0 ftape-rw.c (ftape_stop_tape) - failed ! (fatal). Feb 4 22:58:13 quark kernel: [093] 0 fdc-io.c (__fdc_command) - fdc not ready. Feb 4 22:58:13 quark kernel: [094] 0 fdc-io.c (__fdc_issue_command) - __fdc_command(fdc, out_data, out_count) failed: -16. Feb 4 22:58:14 quark kernel: [095] 0 fdc-io.c (fdc_reset) - no drive polling interrupt!. Any ideas would be greatly appreciated. Stuart
