Wolfgang Weisselberg wrote:
>
> Hi, Jim!
>
> Trying to kill the keyboard, Jim Rankin ([EMAIL PROTECTED])
> produced 1,8K in 47 lines:
>
> > without cc'ing him. I have Red Hat 6.1, kernel 2.2.12-20, ftape 3.04, and
> > although I thought I'd solved his problem using mt -f /dev/rft0 setblk 0,
> > it turns out that if the tape file is large enough, ftape does lose the
> > location of beginning of tape still.
>
> Hmmm ... BOT (begin of tape) is hardware-detected by a (series
> of) holes in the tape. So that is probably not the reason ...
>
> > Because of that, it says it cannot
> > update the header, which is probably what he is seeing(??) ... I was using
> > dd, not tar, in the case I have, and I may yet retry with straight tar, but
> > I suspect he's seeing a general problem.
>
> Unless you show us the complete error message and the output
> in the syslog-files (e.g. /var/log/messages), we can but watch
> the crystal ball ...
Here goes:
I'm executing
gunzip -c disktarfile.tgz | dd of=/dev/ftape obs=10k
where I have used mt to setblk 0 on rft0 first. Yes, ftape points to
rft0.
It starts like this when the file is basically all written (I think):
Dec 5 04:33:10 jrankin kernel: [053] ftape-io.c
(ftape_report_operation_Rf5ac4591) - Acknowledge after 41 msec. (13
iter).
Dec 5 04:33:10 jrankin kernel: [054] ftape-io.c
(ftape_report_error_R999edffd) - errorcode: 39.
Dec 5 04:33:10 jrankin kernel: [055] ftape-io.c
(ftape_report_drive_status) - warning: error status set!.
Dec 5 04:33:10 jrankin kernel: [056] ftape-io.c
(ftape_report_error_R999edffd) - errorcode: 20.
Dec 5 04:33:10 jrankin kernel: [057] ftape-rw.c
(ftape_wait_segment) - Unknown error.
Dec 5 04:33:11 jrankin kernel: [058] ftape-io.c
(ftape_report_error_R999edffd) - errorcode: 20.
Dec 5 04:33:11 jrankin kernel: [059] ftape-io.c
(ftape_report_drive_status) - warning: error status set!.
Dec 5 04:33:11 jrankin kernel: [060] ftape-io.c
(ftape_report_drive_status) - warning: error status set!.
Dec 5 04:33:11 jrankin kernel: [061] ftape-rw.c
(determine_position) - ftape_report_drive_status: 0x27.
Dec 5 04:33:11 jrankin kernel: [062] ftape-rw.c
(ftape_start_tape) - panic: location not known.
Dec 5 04:33:12 jrankin kernel: [063] ftape-io.c
(ftape_report_error_R999edffd) - errorcode: 20.
Dec 5 04:33:12 jrankin kernel: [064] ftape-io.c
(ftape_report_drive_status) - warning: error status set!.
Dec 5 04:33:12 jrankin kernel: [065] ftape-io.c
(ftape_report_drive_status) - warning: error status set!.
Dec 5 04:33:12 jrankin kernel: [066] ftape-rw.c
(determine_position) - ftape_report_drive_status: 0x27.
Dec 5 04:33:12 jrankin kernel: [067] ftape-rw.c
(ftape_start_tape) - panic: location not known.
and goes on like this:
Dec 5 04:33:16 jrankin kernel: [088] ftape-rw.c
(ftape_start_tape) - failed to reposition.
Dec 5 04:33:16 jrankin kernel: [089] ftape-read.c
(ftape_read_segment_fraction_Rc87f4ed7) - Error: segment 0 unreachable.
Dec 5 04:33:16 jrankin kernel: [090] zftape-rw.c
(zft_verify_write_segments) - result =
ftape_read_segment_fraction_Rc87f4ed7(seg_pos, buffer, single ?
FT_RD_SINGLE : FT_RD_AHEAD, 0, ((32 - 3) * 1024)) failed: -5.
Dec 5 04:33:16 jrankin kernel: [091] ftape-io.c
(ftape_report_error_R999edffd) - errorcode: 20.
Dec 5 04:33:17 jrankin kernel: [092] ftape-io.c
(ftape_report_error_R999edffd) - errorcode: 20.
Dec 5 04:33:18 jrankin kernel: [093] ftape-io.c
(ftape_report_drive_status) - warning: error status set!.
Dec 5 04:33:18 jrankin kernel: [094] ftape-io.c
(ftape_report_drive_status) - warning: error status set!.
Dec 5 04:33:18 jrankin kernel: [095] ftape-rw.c
(determine_position) - ftape_report_drive_status: 0x27.
Dec 5 04:33:18 jrankin kernel: [096] ftape-rw.c
(ftape_start_tape) - panic: location not known.
and ends like this:
Dec 5 04:33:22 jrankin kernel: [122] ftape-rw.c
(ftape_start_tape) - failed to reposition.
Dec 5 04:33:22 jrankin kernel: [123] ftape-write.c
(ftape_start_writing_Ra99d81e3) -
ftape_start_tape(segment_id,head->sector_offset) failed: -5.
Dec 5 04:33:22 jrankin kernel: [124] ftape-write.c
(write_segment) - ftape_start_writing_Ra99d81e3(write_mode) failed: -5.
Dec 5 04:33:22 jrankin kernel: [125] ftape-write.c
(ftape_write_segment_R8a09c846) - write_segment failed, error: -5.
Dec 5 04:33:22 jrankin kernel: [126] zftape-rw.c
(zft_verify_write_segments) - Error: Couldn't write segment 1.
Dec 5 04:33:22 jrankin kernel: [127] zftape-write.c
(zft_write_header_segments) - Warning: update of first header segment
failed.
Dec 5 04:33:22 jrankin kernel: [128] zftape-write.c
(zft_write_header_segments) - Warning: update of second header segment
failed.
Dec 5 04:33:22 jrankin kernel: [129] zftape-write.c
(zft_write_header_segments) - Error: update of both header segments
failed..
Dec 5 04:33:22 jrankin kernel: [130] zftape-write.c
(zft_update_header_segments) - zft_write_header_segments(zft_hseg_buf)
failed: -5.
Dec 5 04:33:22 jrankin kernel: [131] ftape-ctl.c
(ftape_disable_R7b52f04b) - == Non-fatal errors this run: ==.
Dec 5 04:33:22 jrankin kernel: [132] ftape-ctl.c
(ftape_disable_R7b52f04b) - fdc isr statistics:
Dec 5 04:33:22 jrankin kernel: id_am_errors : 2
Dec 5 04:33:22 jrankin kernel: id_crc_errors : 7
Dec 5 04:33:22 jrankin kernel: data_am_errors : 0
Dec 5 04:33:22 jrankin kernel: data_crc_errors : 0
Dec 5 04:33:22 jrankin kernel: overrun_errors : 0
Dec 5 04:33:22 jrankin kernel: no_data_errors : 0
Dec 5 04:33:22 jrankin kernel: retries : 8.
Dec 5 04:33:22 jrankin kernel: [133] ftape-ctl.c
(ftape_disable_R7b52f04b) - ecc statistics:
Dec 5 04:33:22 jrankin kernel: crc_errors : 0
Dec 5 04:33:22 jrankin kernel: crc_failures : 0
Dec 5 04:33:22 jrankin kernel: ecc_failures : 0
Dec 5 04:33:22 jrankin kernel: sectors corrected: 0.
Dec 5 04:33:22 jrankin kernel: [134] ftape-ctl.c
(ftape_disable_R7b52f04b) - Warning: 1 media defects!.
Dec 5 04:33:23 jrankin kernel: [135] ftape-ctl.c
(ftape_disable_R7b52f04b) - tape motion statistics:
Dec 5 04:33:23 jrankin kernel: repositions : 10.
Dec 5 04:33:23 jrankin kernel: [136] zftape-init.c (zft_close) -
_zft_close failed.
Sorry for all the output!
Jim
