Apologies for the rather vague subject but I'm more that a little stumped by
this. I've been running with ftape-3.04c for quite some time now and with no
complaint (trouble free backups and the odd successful restore when
required).
Last night my backup script (I use GNU tar) failed with an "I/O error", I
kicked off the backup a second time and it worked fine so I didn't think too
much of it.
Tonight I can't get a backup to work, I'm constantly getting an I/O error.
After trying various things (tape retentions, un-load and re-load ftape,
cycle the power on the machine, etc..) I used ftmt to up the reporting level
and attempted a backup, the output from that failed session is attached.
If someone can give me an idea as to why backups are suddenly failing I'd
really appreciate the pointer.
Various bits of info that may or may not be of use:
ftape version: 3.04c
Linux version: 2.0.33
Tape drive: HP Colorado T3000
Tape: 3M Travan-3 1.6GB
ftape is installed as:
----------------------------------------------------------------------
root@hagbard:~# lsmod
Module: #pages: Used by:
zftape 15 0
ftape 26 [zftape] 0
----------------------------------------------------------------------
Thanks in advance.
--
Take a look in Hagbard's World: | w3ng - The WWW Norton Guide reader.
http://www.acemake.com/hagbard/ | eg - Norton Guide reader for Linux.
http://www.hagbard.demon.co.uk/ | weg - Norton Guide reader for Windows.
Free software, including........| dgscan - DGROUP scanner for Clipper.
Mar 23 23:29:49 hagbard kernel: [219] fdc-io.c (fdc_reset) - drive polling
completed.
Mar 23 23:29:49 hagbard kernel: [220] fdc-io.c (fdc_fifo_threshold) - original
fifo state: disabled, threshold 1, not locked.
Mar 23 23:29:49 hagbard kernel: [221] fdc-io.c (fdc_fifo_threshold) - original
fifo state: enabled, threshold 8, locked.
Mar 23 23:29:49 hagbard kernel: [222] zftape-buffers.c (zft_vmalloc_once_R0db669bc)
- allocated buffer @ 0484f000, 29696 bytes.
Mar 23 23:29:49 hagbard kernel: [223] zftape-vtbl.c (zft_open_volume) - create new
volume.
Mar 23 23:29:49 hagbard kernel: [224] zftape-vtbl.c (zft_find_volume) - 3 - 55849.
Mar 23 23:29:49 hagbard kernel: [225] zftape-vtbl.c (zft_find_volume) - Volume 0:
Mar 23 23:29:49 hagbard kernel: description :
Mar 23 23:29:49 hagbard kernel: first segment: 3
Mar 23 23:29:49 hagbard kernel: last segment: 55849
Mar 23 23:29:49 hagbard kernel: size : 1616680/0 KB
Mar 23 23:29:49 hagbard kernel: block size : 10240
Mar 23 23:29:49 hagbard kernel: compression : 0
Mar 23 23:29:49 hagbard kernel: zftape volume: 1
Mar 23 23:29:49 hagbard kernel: QIC-113 conf.: 1.
Mar 23 23:29:49 hagbard kernel: [226] zftape-write.c (check_write_access) - Volume 0:
Mar 23 23:29:49 hagbard kernel: description :
Mar 23 23:29:49 hagbard kernel: first segment: 3
Mar 23 23:29:49 hagbard kernel: last segment: 55849
Mar 23 23:29:49 hagbard kernel: size : 1616680/0 KB
Mar 23 23:29:49 hagbard kernel: block size : 10240
Mar 23 23:29:49 hagbard kernel: compression : 0
Mar 23 23:29:49 hagbard kernel: zftape volume: 1
Mar 23 23:29:49 hagbard kernel: QIC-113 conf.: 1.
Mar 23 23:29:49 hagbard kernel: [227] ftape-write.c (write_segment) - segment_id =
3.
Mar 23 23:29:49 hagbard kernel: [228] ftape-write.c (write_segment) - calling
ftape_abort_operation.
Mar 23 23:29:49 hagbard kernel: [229] ftape-write.c (write_segment) - segment_id =
4.
Mar 23 23:29:49 hagbard kernel: [230] ftape-write.c (write_segment) - segment_id =
5.
Mar 23 23:29:49 hagbard kernel: [231] ftape-write.c
(ftape_start_writing_R1bd72980) - starting runner for segment 3.
Mar 23 23:29:49 hagbard kernel: [232] ftape-rw.c (ftape_start_tape) - target
segment: 3/0.
Mar 23 23:29:50 hagbard kernel: [233] ftape-rw.c (ftape_start_tape) - current
segment: -1/-1.
Mar 23 23:29:50 hagbard kernel: [234] ftape-rw.c (seek_forward) - from -1/-1 to
2/0 - 1.
Mar 23 23:29:53 hagbard kernel: [235] ftape-write.c (write_segment) - segment_id =
6.
Mar 23 23:29:53 hagbard kernel: [236] ftape-write.c (write_segment) - segment_id =
7.
Mar 23 23:29:54 hagbard kernel: [237] ftape-write.c (write_segment) - segment_id =
8.
Mar 23 23:29:54 hagbard kernel: [238] ftape-write.c (write_segment) - segment_id =
9.
Mar 23 23:29:54 hagbard kernel: [239] ftape-write.c (write_segment) - segment_id =
10.
Mar 23 23:29:55 hagbard kernel: [240] ftape-write.c (write_segment) - segment_id =
11.
Mar 23 23:29:55 hagbard kernel: [241] ftape-write.c (write_segment) - segment_id =
12.
Mar 23 23:29:55 hagbard kernel: [242] ftape-write.c (write_segment) - segment_id =
13.
Mar 23 23:29:56 hagbard kernel: [243] ftape-write.c (write_segment) - segment_id =
14.
Mar 23 23:29:56 hagbard kernel: [244] ftape-write.c (write_segment) - segment_id =
15.
Mar 23 23:29:56 hagbard kernel: [245] ftape-write.c (write_segment) - segment_id =
16.
Mar 23 23:29:57 hagbard kernel: [246] ftape-write.c (write_segment) - segment_id =
17.
Mar 23 23:29:57 hagbard kernel: [247] ftape-write.c (write_segment) - segment_id =
18.
Mar 23 23:29:58 hagbard kernel: [248] ftape-write.c (write_segment) - segment_id =
19.
Mar 23 23:29:58 hagbard kernel: [249] ftape-write.c (write_segment) - segment_id =
20.
Mar 23 23:29:58 hagbard kernel: [250] ftape-write.c (write_segment) - segment_id =
21.
Mar 23 23:29:59 hagbard kernel: [251] ftape-write.c (write_segment) - segment_id =
22.
Mar 23 23:29:59 hagbard kernel: [252] ftape-write.c (write_segment) - segment_id =
23.
Mar 23 23:29:59 hagbard kernel: [253] ftape-write.c (write_segment) - segment_id =
24.
Mar 23 23:30:00 hagbard kernel: [254] ftape-write.c (write_segment) - segment_id =
25.
Mar 23 23:30:00 hagbard kernel: [255] ftape-write.c (write_segment) - segment_id =
26.
Mar 23 23:30:00 hagbard kernel: [000] ftape-write.c (write_segment) - segment_id =
27.
Mar 23 23:30:01 hagbard kernel: [001] ftape-write.c (write_segment) - segment_id =
28.
Mar 23 23:30:01 hagbard kernel: [002] ftape-write.c (write_segment) - segment_id =
29.
Mar 23 23:30:01 hagbard kernel: [003] ftape-write.c (write_segment) - segment_id =
30.
Mar 23 23:30:51 hagbard kernel: [004] fdc-io.c (fdc_reset) - drive polling
completed.
Mar 23 23:30:51 hagbard kernel: [005] ftape-rw.c (ftape_wait_segment) -
fdc_interrupt_wait failed.
Mar 23 23:30:51 hagbard kernel: [006] ftape-write.c (write_segment) - wait for
empty segment failed, tail status: 2.
Mar 23 23:30:51 hagbard kernel: [007] ftape-write.c (ftape_write_segment_R86fa842e)
- write_segment failed, error: -5.
Mar 23 23:30:51 hagbard kernel: [008] zftape-write.c (_zft_write) -
ftape_write_segment_R86fa842e(zft_pos.seg_pos, zft_deblock_buf, FT_WR_ASYNC) failed:
-5.
Mar 23 23:30:51 hagbard kernel: [009] ftape-ctl.c (ftape_abort_operation_R89802473)
- aborting runner, waiting.
Mar 23 23:30:53 hagbard kernel: [010] zftape-ctl.c (_zft_close) - writing file mark
at current position.
Mar 23 23:30:53 hagbard kernel: [011] zftape-vtbl.c (zft_move_past_eof) - old seg.
pos: 30.
Mar 23 23:30:53 hagbard kernel: [012] zftape-vtbl.c (zft_move_past_eof) - new seg.
pos: 31.
Mar 23 23:30:53 hagbard kernel: [013] zftape-ctl.c (_zft_close) - Error: unable to
update header segments.
Mar 23 23:30:53 hagbard kernel: [014] zftape-ctl.c (_zft_close) - rewinding tape.
Mar 23 23:31:14 hagbard kernel: [015] zftape-rw.c (zft_calc_tape_pos) - new cached
pos: 3.
Mar 23 23:31:14 hagbard kernel: [016] zftape-buffers.c (zft_vfree_R46d0a188) -
released buffer @ 0484f000, 29696 bytes.
Mar 23 23:31:14 hagbard kernel: [017] zftape-ctl.c (_zft_close) - Keeping module
locked in memory because:
Mar 23 23:31:14 hagbard kernel: header segments need updating: yes
Mar 23 23:31:14 hagbard kernel: tape not at BOT : no.
Mar 23 23:31:14 hagbard kernel: [018] zftape-buffers.c (zft_memory_stats) - Memory
usage (vmalloc allocations):
Mar 23 23:31:14 hagbard kernel: total allocated: 29804
Mar 23 23:31:14 hagbard kernel: peak allocation: 59500.
Mar 23 23:31:14 hagbard kernel: [019] fdc-io.c (fdc_disable) - fifo restored:
disabled, thr. 1, not locked.
Mar 23 23:31:14 hagbard kernel: [020] ftape-ctl.c (ftape_disable_Rd8944c5d) - ==
Non-fatal errors this run: ==.
Mar 23 23:31:14 hagbard kernel: [021] ftape-ctl.c (ftape_disable_Rd8944c5d) - fdc
isr statistics:
Mar 23 23:31:14 hagbard kernel: id_am_errors : 0
Mar 23 23:31:14 hagbard kernel: id_crc_errors : 0
Mar 23 23:31:14 hagbard kernel: data_am_errors : 0
Mar 23 23:31:14 hagbard kernel: data_crc_errors : 0
Mar 23 23:31:14 hagbard kernel: overrun_errors : 0
Mar 23 23:31:14 hagbard kernel: no_data_errors : 0
Mar 23 23:31:14 hagbard kernel: retries : 0.
Mar 23 23:31:14 hagbard kernel: [022] zftape-init.c (zft_close) - _zft_close failed.
