HI,
I am running Amanda 2.4.2p2 with ftape-3212002 and everything was
working fine until I installed a scsci-2 HP Surestore T4 tape drive.
When I run amcheck on the conf file I get the following error:
Amanda Tape Server Host Check
-----------------------------
Holding disk /amanda: 1342540 KB disk space available, that's plenty
ERROR: /dev/nqft0: not an amanda tape
(expecting tape Daily-003 or a new tape)
NOTE: skipping tape-writable test
Server check took 15.302 seconds
Amanda Backup Client Hosts Check
--------------------------------
Client check: 1 host checked in 0.025 seconds, 0 problems found
(brought to you by Amanda 2.4.2p2)
The tape was a valid tape several days ago and worked fine. So, to just
check things out I also tried to relabel the tape using the command
amlabel -f Daily Daily-003 and the output I get is now:
rewinding, reading label, no tape online
rewinding, writing label Daily-003,
rewinding, updating volume tableamlabel: setting date for entry 1:
Permission denied
Now, when looking into the logs I notice that zftape is acting strange.
I get this as the output:
Jul 23 05:56:12 stud kernel: [157] 0 ftape-ctl.c
(ftape_get_drive_status) - status: new cartridge.
Jul 23 05:56:13 stud kernel: [158] 0 ftape-io.c
(ftape_report_configuration) - TR-3 tape detected.
Jul 23 05:56:13 stud kernel: [159] 0 ftape-ctl.c (ftape_init_drive) -
post QIC-117B drive @ 1000 Kbps.
Jul 23 05:56:13 stud kernel: [160] 0 ftape-ctl.c
(ftape_calibrate_data_rate) - Highest FDC supported data rate: 1000 Kbps.
Jul 23 05:56:15 stud kernel: [161] 0 ftape-io.c
(ftape_report_configuration) - TR-3 tape detected.
Jul 23 05:56:15 stud kernel: [162] 0 ftape-ctl.c (ftape_init_drive) -
unknown length QIC-3020 tape.
Jul 23 05:56:21 stud kernel: [163] 0 ftape-read.c
(ftape_decode_header_segment) - calculated tape length is 766 ft.
Jul 23 05:56:21 stud kernel: [164] 0 ftape-bsm.c
(print_bad_sector_map) - 1580098 Kb usable on this tape.
Jul 23 05:56:21 stud kernel: [165] 0 ftape-bsm.c
(print_bad_sector_map) - 6144 bad sectors.
Jul 23 05:56:21 stud kernel: [166] 0 zftape-read.c
(zft_read_header_segments) - Segments written since first format: 182149.
Jul 23 05:56:21 stud kernel: [167] 0 zftape-read.c
(zft_read_header_segments) - zftape->ftape->first_data_segment: 2,
zftape->ftape->last_data_segment: 54699.
Jul 23 05:56:26 stud kernel: [168] 0 ftape-ctl.c
(ftape_print_history) - == Non-fatal errors this run: ==.
Jul 23 05:56:26 stud kernel: [169] 0 ftape-ctl.c
(ftape_print_history) - fdc isr statistics:
Jul 23 05:56:26 stud kernel: id_am_errors : 0
Jul 23 05:56:26 stud kernel: id_crc_errors : 0
Jul 23 05:56:26 stud kernel: data_am_errors : 0
Jul 23 05:56:26 stud kernel: data_crc_errors : 0
Jul 23 05:56:26 stud kernel: overrun_errors : 0
Jul 23 05:56:26 stud kernel: no_data_errors : 0
Jul 23 05:56:26 stud kernel: retries : 0.
Jul 23 05:56:26 stud kernel: [170] 0 ftape-ctl.c
(ftape_print_history) - ecc statistics:
Jul 23 05:56:26 stud kernel: crc_errors : 0
Jul 23 05:56:26 stud kernel: crc_failures : 0
Jul 23 05:56:26 stud kernel: ecc_failures : 0
Jul 23 05:56:27 stud kernel: sectors corrected: 0.
Jul 23 05:56:27 stud kernel: [171] 0 ftape-ctl.c
(ftape_print_history) - tape motion statistics:
Jul 23 05:56:27 stud kernel: repositions : 1.
Jul 23 06:02:49 stud kernel: [172] 0 zftape-init.c (zft_open) - failed:
already busy.
Jul 23 06:02:51 stud kernel: [173] 0 zftape-init.c (zft_open) - failed:
already busy.
Jul 23 06:02:55 stud kernel: [174] 0 zftape-init.c (zft_open) - failed:
already busy.
Jul 23 06:03:03 stud kernel: [175] 0 zftape-init.c (zft_open) - failed:
already busy.
Jul 23 06:03:19 stud kernel: [176] 0 zftape-init.c (zft_open) - failed:
already busy.
Jul 23 06:03:35 stud kernel: [177] 0 zftape-init.c (zft_open) - failed:
already busy.
Jul 23 06:03:51 stud kernel: [178] 0 zftape-init.c (zft_open) - failed:
already busy.
Jul 23 06:04:07 stud kernel: [179] 0 zftape-init.c (zft_open) - failed:
already busy.
I've yet to find out what it is busy doing. I cannot rmmod the module
because it is auto-unloading.
Now, I completly seperated the new scsi tape drive from the system to
try out that variable, but that made no difference. The funny thing is
that I can backup to that tape drive as user amanda or root using tar
and the files verify fine. Any help is appreciated. Thanks.
--
Trevor Morrison
Hailix, LLC
[EMAIL PROTECTED]
