Re: Colorado Jumbo 250

At 09:11 AM 7/1/02 -0700, you wrote:

>That would be the most interesting information.  Ftape is highly sensitive
>to the tape format, so to rule out problems with the tape format, you need
>to use a command that doesn't expect the tape already to be formatted.
>You didn't mention whether there is any indication of success or failure on
>erase.

Well, let's try lots of info :-)..

Firstly, erase reports:

[root@rush root]# ftmt -f /dev/ftape erase
ftmt: /dev/ftape: Input/output error
[root@rush root]# 

The syslog for the above:

Jul  1 09:19:12 rush kernel: [155]        zftape-rw.c
(zft_verify_write_segments) - Failed to verify written segment 0.
Jul  1 09:19:22 rush kernel: [156]        zftape-rw.c
(zft_verify_write_segments) - Failed to verify written segment 1.
Jul  1 09:19:22 rush kernel: [157]       zftape-write.c
(zft_write_header_segments) - Warning: update of first header segment failed.
Jul  1 09:19:22 rush kernel: [158]       zftape-write.c
(zft_write_header_segments) - Warning: update of second header segment failed.
Jul  1 09:19:22 rush kernel: [159]       zftape-write.c
(zft_write_header_segments) - Error: update of both header segments failed..
Jul  1 09:19:22 rush kernel: [160]      zftape-write.c
(zft_update_header_segments) - zft_write_header_segments(zft_hseg_buf)
failed: -5.
Jul  1 09:19:30 rush kernel: [161]      zftape-rw.c
(zft_verify_write_segments) - Failed to verify written segment 0.
Jul  1 09:19:40 rush kernel: [162]      zftape-rw.c
(zft_verify_write_segments) - Failed to verify written segment 1.
Jul  1 09:19:40 rush kernel: [163]     zftape-write.c
(zft_write_header_segments) - Warning: update of first header segment failed.
Jul  1 09:19:40 rush kernel: [164]     zftape-write.c
(zft_write_header_segments) - Warning: update of second header segment failed.
Jul  1 09:19:40 rush kernel: [165]     zftape-write.c
(zft_write_header_segments) - Error: update of both header segments failed..
Jul  1 09:19:40 rush kernel: [166]    zftape-write.c
(zft_update_header_segments) - zft_write_header_segments(zft_hseg_buf)
failed: -5.
Jul  1 09:19:40 rush kernel: [167]   zftape-ctl.c (mtioctop) -
zft_update_header_segments() failed: -5.
Jul  1 09:19:48 rush kernel: [168]     zftape-rw.c
(zft_verify_write_segments) - Failed to verify written segment 0.
Jul  1 09:19:57 rush kernel: [169]     zftape-rw.c
(zft_verify_write_segments) - Failed to verify written segment 1.
Jul  1 09:19:57 rush kernel: [170]    zftape-write.c
(zft_write_header_segments) - Warning: update of first header segment failed.
Jul  1 09:19:57 rush kernel: [171]    zftape-write.c
(zft_write_header_segments) - Warning: update of second header segment failed.
Jul  1 09:19:57 rush kernel: [172]    zftape-write.c
(zft_write_header_segments) - Error: update of both header segments failed..
Jul  1 09:19:57 rush kernel: [173]   zftape-write.c
(zft_update_header_segments) - zft_write_header_segments(zft_hseg_buf)
failed: -5.
Jul  1 09:20:00 rush kernel: [174]   ftape-ctl.c (ftape_disable_R7b52f04b)
- == Non-fatal errors this run: ==.
Jul  1 09:20:00 rush kernel: [175]   ftape-ctl.c (ftape_disable_R7b52f04b)
- fdc isr statistics:
Jul  1 09:20:00 rush kernel:  id_am_errors     :   0
Jul  1 09:20:00 rush kernel:  id_crc_errors    :   0
Jul  1 09:20:00 rush kernel:  data_am_errors   :   0
Jul  1 09:20:00 rush kernel:  data_crc_errors  :   0
Jul  1 09:20:00 rush kernel:  overrun_errors   :   0
Jul  1 09:20:00 rush kernel:  no_data_errors   :   0
Jul  1 09:20:00 rush kernel:  retries          :   0.
Jul  1 09:20:00 rush kernel: [176]   ftape-ctl.c (ftape_disable_R7b52f04b)
- ecc statistics:
Jul  1 09:20:00 rush kernel:  crc_errors       :   0
Jul  1 09:20:00 rush kernel:  crc_failures     :   0
Jul  1 09:20:00 rush kernel:  ecc_failures     :   0
Jul  1 09:20:00 rush kernel:  sectors corrected:   0.
Jul  1 09:20:00 rush kernel: [177]   ftape-ctl.c (ftape_disable_R7b52f04b)
- tape motion statistics:
Jul  1 09:20:00 rush kernel: repositions       :  12.
Jul  1 09:20:00 rush kernel: [178] zftape-init.c (zft_close) - _zft_close
failed.

If I try a test write to the tape, I don't see any errors reported on the
command line:

[root@rush root]# tar -cvf /dev/ftape taper_prefs
taper_prefs
[root@rush root]# 

But syslog shows:

Jul  1 09:23:27 rush kernel: [208]     zftape-rw.c
(zft_verify_write_segments) - Failed to verify written segment 0.
Jul  1 09:23:36 rush kernel: [209]     zftape-rw.c
(zft_verify_write_segments) - Failed to verify written segment 1.
Jul  1 09:23:36 rush kernel: [210]    zftape-write.c
(zft_write_header_segments) - Warning: update of first header segment failed.
Jul  1 09:23:36 rush kernel: [211]    zftape-write.c
(zft_write_header_segments) - Warning: update of second header segment failed.
Jul  1 09:23:36 rush kernel: [212]    zftape-write.c
(zft_write_header_segments) - Error: update of both header segments failed..
Jul  1 09:23:36 rush kernel: [213]   zftape-write.c
(zft_update_header_segments) - zft_write_header_segments(zft_hseg_buf)
failed: -5.
Jul  1 09:23:39 rush kernel: [214]   ftape-ctl.c (ftape_disable_R7b52f04b)
- == Non-fatal errors this run: ==.
Jul  1 09:23:39 rush kernel: [215]   ftape-ctl.c (ftape_disable_R7b52f04b)
- fdc isr statistics:
Jul  1 09:23:39 rush kernel:  id_am_errors     :   0
Jul  1 09:23:39 rush kernel:  id_crc_errors    :   0
Jul  1 09:23:39 rush kernel:  data_am_errors   :   0
Jul  1 09:23:39 rush kernel:  data_crc_errors  :   0
Jul  1 09:23:39 rush kernel:  overrun_errors   :   0
Jul  1 09:23:39 rush kernel:  no_data_errors   :   0
Jul  1 09:23:39 rush kernel:  retries          :   0.
Jul  1 09:23:39 rush kernel: [216]   ftape-ctl.c (ftape_disable_R7b52f04b)
- ecc statistics:
Jul  1 09:23:39 rush kernel:  crc_errors       :   0
Jul  1 09:23:39 rush kernel:  crc_failures     :   0
Jul  1 09:23:39 rush kernel:  ecc_failures     :   0
Jul  1 09:23:39 rush kernel:  sectors corrected:   0.
Jul  1 09:23:39 rush kernel: [217]   ftape-ctl.c (ftape_disable_R7b52f04b)
- tape motion statistics:
Jul  1 09:23:39 rush kernel: repositions       :   5.
Jul  1 09:23:39 rush kernel: [218] zftape-init.c (zft_close) - _zft_close
failed.

BTW, I have a dozen different tapes and ftape exhibits the same failures
regardless of which tape I try. 

Does the above help at all?

Ken








------------------------------------------------------------------------------
Amateur Radio Station AH6LE
http://www.ah6le.net
http://www.ah6le.com
AH6LE/R - IRLP Node 300
http://www.irlp.net

RC Websites
http://oregonbarnstormers.rcclubs.com
http://pegasus.rcplanet.com
-
To unsubscribe from this list: send the line "unsubscribe linux-tape" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html